If you have ever embedded a YouTube video on a client site or a landing page, you already know the awkward moment: the video finishes, and the screen fills with a grid of other people’s videos. Sometimes a competitor’s. You did the work of getting someone to watch, and the last thing the player does is offer them somewhere else to go.
So people go looking for the setting that turns it off. This walkthrough covers what you can genuinely control, what changed in 2018 that broke most of the advice still circulating, and what is left once you know the difference.
The short version
There is no combination of URL parameters that gives you a YouTube embed with no branding and no suggested videos. Two of the three parameters everyone recommends no longer do anything at all, and the third does something much smaller than its reputation suggests.
That is not a reason to give up. It is a reason to stop spending an afternoon on query strings and pick one of the three approaches further down.
What actually happens when you paste an embed code
The standard embed loads YouTube’s own player inside an iframe on your page. That player is YouTube’s product, not yours, and it is built to keep people watching YouTube. The end screen is not a bug or an oversight. It is the point.
This matters because it explains why the parameters are so limited. You are not configuring your player. You are politely requesting small adjustments to someone else’s.
The three parameters everyone recommends
Here is the current state of each, according to YouTube’s own player parameter documentation:
| Parameter | Status | What it does today |
|---|---|---|
rel=0 |
Changed in 2018 | Limits end-screen suggestions to videos from the same channel. It does not remove the end screen. |
modestbranding=1 |
Deprecated | No effect. Retired in August 2023; the player now decides its own branding. |
showinfo=0 |
Removed | No effect. The title and channel avatar always appear before playback. |
The rel change is the one that catches people, because it is so easy to believe it worked. Before September 2018, rel=0 genuinely did suppress related videos. Afterwards it only narrowed them to your own channel. Nothing errors, nothing warns, and the URL looks exactly like the one in the tutorial you copied it from, so there is no signal that anything changed.
If you want the full picture, including the parameters that do still work and what each one actually controls, there is a detailed breakdown of every current player parameter here. It is the most complete reference I have found on what survived the deprecations.
What you can still control
Plenty of the player API works fine. It is worth knowing where the real boundary sits:
- Hide the control bar entirely with
controls=0. This works, but you lose the scrubber, volume and captions button too, so you need to build replacements or accept a player nobody can operate. - Stop playback early with
end, measured in seconds. Useful for trimming, though the suggestion grid still arrives if the video reaches its real end. - Turn off annotations with
iv_load_policy=3. - Remove the fullscreen button with
fs=0, and disable keyboard control withdisablekb=1. - Recolor the progress bar with
color, which accepts exactly two values: red or white.
What you cannot do, at any price, through parameters alone: skip the title card before playback, prevent the end screen, or make the player look like it belongs to your brand.
The three approaches that actually work
1. Shape the end screen instead of fighting it
Set rel=0 so suggestions stay on your channel, use end to stop short where it makes sense, and publish enough of your own videos that a same-channel grid is a reasonable next step rather than an exit. This costs nothing and is genuinely the right answer for a lot of channels.
2. Move to paid hosting
Vimeo and Wistia both give you a quiet player with no third-party suggestions, because their revenue is your subscription rather than watch time. You pay for storage and bandwidth you currently get for free, and you take on a migration and an ongoing bill that grows with your library. If you need private video, client review workflows, or per-viewer engagement analytics, that bill buys real things.
3. Keep the video where it is and change the wrapper
The third option is the one most people do not realise exists. Instead of moving the video, you put it inside a player shell of your own: your cover image, your colors, your controls, and your message when playback finishes. The video keeps living on YouTube, so you keep the free hosting, transcoding and CDN, and the presentation stops being YouTube’s decision.
This is the approach purpose-built embed tools take. Vid Sharpei is one of them: you paste a link, pick your accent color and the call to action that appears at the end, and drop one snippet into your site. It works on WordPress, Squarespace, Webflow and anywhere else you can paste HTML, and there is a live comparison on the home page if you want to see the difference side by side before deciding anything.
A note on page speed
Whichever route you take, standard embeds are heavier than they look. A single YouTube iframe pulls a significant amount of JavaScript on page load whether or not anyone presses play, and on a page with three or four videos that adds up fast enough to show in your Core Web Vitals. Any approach that defers loading until someone actually clicks will do more for your page speed than most of the optimisation plugins people install to fix it.
The takeaway
If you take one thing from this: rel=0 narrows suggestions to your channel, and modestbranding and showinfo do nothing whatsoever. Any guide that promises a clean embed from a query string was written before September 2018 and never updated.
Once you accept that, the decision gets simpler. Either the end screen is acceptable and you shape it, or the presentation matters enough to change the wrapper around the video. Both are reasonable. Spending another hour on URL parameters is not.
