YouTube embed parameters are the query-string options that control exactly how an embedded video looks and behaves. This guide walks through twelve of the most useful ones individually, with a working example for each, so you can see precisely what each one changes.
How parameters attach to an embed URL
Every parameter is appended to the embed URL as a key-value pair, joined with an ampersand: https://www.youtube-nocookie.com/embed/VIDEO_ID?param1=value1¶m2=value2. You can combine as many as you like. Boolean-style parameters generally use 1 for “on” and 0 for “off,” and leaving a parameter out entirely falls back to YouTube’s own default behaviour for it.
1. autoplay
Starts the video the moment the player loads, without a visitor pressing play.
https://www.youtube-nocookie.com/embed/VIDEO_ID?autoplay=1Most browsers block autoplaying video with sound unless the visitor has already interacted with your site, so autoplay is almost always paired with mute.
2. mute
Starts the player muted, which is what makes autoplay reliably work across browsers.
https://www.youtube-nocookie.com/embed/VIDEO_ID?autoplay=1&mute=13. start
Begins playback at a specific number of seconds into the video, rather than from the beginning.
https://www.youtube-nocookie.com/embed/VIDEO_ID?start=90Ninety seconds in this example means the player opens straight at the 1:30 mark.
4. end
Stops playback at a specific number of seconds, useful for showing only a relevant clip of a longer video.
https://www.youtube-nocookie.com/embed/VIDEO_ID?start=30&end=90Combined with start, this plays only the 30 to 90 second window and then stops.
5. loop
Replays the video automatically once it finishes. For a single video (not a playlist), you also need to add a playlist parameter set to the same video ID, or looping silently will not work.
https://www.youtube-nocookie.com/embed/VIDEO_ID?loop=1&playlist=VIDEO_ID6. controls
Shows or hides the player’s control bar (play/pause, volume, progress, fullscreen).
https://www.youtube-nocookie.com/embed/VIDEO_ID?controls=0Setting this to 0 is common for background-style video where you do not want visible playback controls.
7. rel
Controls what related videos are suggested once playback ends. Setting this to 0 limits suggestions to videos from the same channel rather than YouTube’s broader recommendation pool.
https://www.youtube-nocookie.com/embed/VIDEO_ID?rel=08. list (and the videoseries path)
Loads an entire playlist instead of a single video. This is combined with the /embed/videoseries path rather than a single video ID.
https://www.youtube-nocookie.com/embed/videoseries?list=PLAYLIST_ID9. index
Used alongside a playlist to choose which item to start on, counting from 0 for the first video.
https://www.youtube-nocookie.com/embed/videoseries?list=PLAYLIST_ID&index=2This example starts on the third video in the playlist.
10. hl
Sets the language of the player’s own interface elements (not the video’s audio or captions), using a standard language code.
https://www.youtube-nocookie.com/embed/VIDEO_ID?hl=de11. cc_load_policy
Forces captions to display by default when set to 1, useful for accessibility-focused embeds or silent-autoplay video where captions carry the meaning.
https://www.youtube-nocookie.com/embed/VIDEO_ID?cc_load_policy=112. color
Sets the colour of the player’s progress bar, accepting either red or white as values.
https://www.youtube-nocookie.com/embed/VIDEO_ID?color=whiteCombining several parameters
Parameters stack freely. A privacy-friendly, responsive, autoplaying background clip that loops silently and hides controls might look like this:
https://www.youtube-nocookie.com/embed/VIDEO_ID?autoplay=1&mute=1&controls=0&loop=1&playlist=VIDEO_ID&rel=0Reference table
| Parameter | Values | What it does |
|---|---|---|
| autoplay | 0 / 1 | Starts playback automatically |
| mute | 0 / 1 | Starts muted, required for reliable autoplay |
| start | seconds | Playback start point |
| end | seconds | Playback stop point |
| loop | 0 / 1 | Replays the video (needs playlist param for a single video) |
| controls | 0 / 1 | Shows or hides the control bar |
| rel | 0 / 1 | Limits end-of-video suggestions to the same channel |
| list | playlist ID | Loads a full playlist via /embed/videoseries |
| index | number | Which playlist item to start on |
| hl | language code | Player interface language |
| cc_load_policy | 0 / 1 | Forces captions on by default |
| color | red / white | Progress bar colour |
Related reading
For the layout side of embedding, see our guide on responsive YouTube embeds. For privacy, see embedding YouTube videos without cookies. For troubleshooting, see YouTube video not embedding: 8 fixes.
Parameters that are frequently confused with each other
A few of these twelve parameters get mixed up often enough to be worth a direct comparison. autoplay and loop sound similar but do different jobs: autoplay controls whether playback starts on load, loop controls whether it restarts after finishing, and they are commonly used together but are independent settings. start and index are also easy to confuse: start is a time offset in seconds within a single video, while index is a position within a playlist, counted in items rather than time. Getting these paired correctly matters, since mismatching them (for example, trying to use index on a single-video embed) simply has no effect rather than producing an error.
Parameters with limited or inconsistent support
Not every parameter behaves identically across every context. modestbranding, which reduces YouTube’s logo presence, has had inconsistent effects across different versions of the player and is generally considered a best-effort setting rather than a guaranteed one. Similarly, some display-related parameters can behave slightly differently depending on whether a visitor is logged into a Google account in their browser, since account-level preferences can interact with player defaults. The playback-control parameters covered above, start, end, autoplay, mute, loop and controls, are the most consistently reliable across browsers and account states, which is why they are the ones worth building your embed strategy around.
A worked example: building a course-page embed step by step
Imagine you are embedding a lesson video on a course page and want it privacy-friendly, responsive, starting at the two-minute mark where the actual lesson content begins (skipping a channel intro), with captions on by default for accessibility, and no autoplay since a visitor should choose to start it themselves. Working through the parameters: privacy-friendly means the youtube-nocookie.com domain; responsive means a percentage-based wrapper rather than fixed dimensions; starting at two minutes means start=120; captions by default means cc_load_policy=1; and no autoplay means simply omitting the autoplay parameter, since that is the default state. The resulting embed URL would be:
https://www.youtube-nocookie.com/embed/VIDEO_ID?start=120&cc_load_policy=1&rel=0This single example shows how the parameters covered in this guide combine naturally to solve a specific, realistic requirement rather than existing as an abstract list.
Testing your parameter combinations
Before publishing an embed with several combined parameters, it is worth testing it directly rather than assuming the combination works as expected. Paste the full embed URL, parameters and all, directly into a browser tab; the player should behave exactly as it would inside your page’s iframe, which lets you catch typos in parameter names (a common mistake, since a misspelled parameter is usually just silently ignored rather than flagged as an error) before they reach your live site.
Parameters and privacy: which ones interact with the nocookie domain
It is worth clarifying that every parameter covered in this guide works identically whether you use the standard youtube.com embed domain or the privacy-enhanced youtube-nocookie.com domain. The domain choice and the playback parameters are entirely independent decisions: switching to the privacy-enhanced domain does not disable or alter any of autoplay, mute, start, end, loop, controls, rel, list, index, hl, cc_load_policy or color. This is a common point of confusion worth addressing directly, since some site owners assume privacy mode is a stripped-down version of the player with fewer options, when in practice it is functionally identical, just with different cookie behaviour on the Google side.
Building your own parameter reference for a specific project
For a larger site with many embedded videos, it is worth documenting internally which combination of these twelve parameters your team defaults to, rather than reinventing the choice for every new embed. A simple internal standard, for example: always use the privacy-enhanced domain, always include rel=0, default to no autoplay unless a specific page type calls for it, and always use a responsive wrapper, keeps embeds consistent across a site and makes it much faster to spot a misconfigured one during review. Treating this list of twelve parameters as a menu to choose defaults from, rather than a one-off decision made fresh each time, pays off as a site’s video content grows.
A final word on keeping this reference handy
Bookmarking this page, or the reference table above specifically, is likely more useful than trying to memorise all twelve parameters outright. In practice, most embeds on a typical site use only three or four of these at once (commonly a privacy-enhanced domain implicitly, rel=0, and occasionally start or autoplay/mute together), so having the full list to check against for the less common cases, like playlists or captions, covers the remaining situations without needing everything memorised up front.
How YouTube’s own documentation compares to this guide
YouTube publishes its own developer documentation covering the IFrame Player API and embed parameters, aimed primarily at developers building custom, JavaScript-controlled players rather than site owners adding a straightforward embed to a page. This guide focuses specifically on the subset of parameters relevant to a standard iframe embed without custom JavaScript, which covers the large majority of real-world use cases on ordinary websites. For anyone building more advanced, programmatically controlled video experiences (custom play buttons, watch-progress tracking, synchronised multi-video players), YouTube’s own IFrame Player API documentation is the next step beyond what a query-string-parameter approach like this one can offer.
A closing summary of the twelve parameters
Across autoplay, mute, start, end, loop, controls, rel, list, index, hl, cc_load_policy and color, the practical takeaway is that a small handful (privacy domain choice, rel, and a responsive wrapper) form a sensible default for nearly every embed, while the rest (start/end, loop, shorts formatting, playlists, captions, language and colour) are situational tools worth reaching for only when a specific page genuinely calls for them, rather than being added indiscriminately to every embed on a site.
Build one now
Free tool
Skip the manual query strings. Paste a link and toggle the options you need.
Keeping this reference within reach means never having to guess at parameter names from memory when a new embedding need comes up.
Frequently asked questions
Do all these parameters work together with no conflicts?
Yes, they can generally be combined freely. The main dependency to remember is that loop requires a matching playlist parameter to work on a single video.
Are there parameters that no longer work?
A few older parameters referenced in older tutorials, such as showinfo, have been deprecated by YouTube over time and no longer have a visible effect.
Do I need to memorise these to use them?
No. Our free embed code generator exposes the most useful ones as simple toggles and fields and builds the URL for you.
What happens if I misspell a parameter name?
YouTube’s player generally ignores parameters it does not recognise rather than throwing a visible error, so a typo silently has no effect, which is why testing your exact embed URL directly is worthwhile.
Can I set a default volume level with a parameter?
No, there is no parameter for a specific default volume level; the player either starts muted (via the mute parameter) or at the viewer’s own last-used volume setting.
Do these parameters work the same way on mobile?
Generally yes, though mobile browsers apply their own additional autoplay restrictions on top of YouTube’s own, so muted autoplay is even more consistently required on mobile than on desktop.
Can I change these parameters after a video is already embedded on my page?
Yes, since the parameters simply live in the iframe’s src URL, editing the HTML on your page and republishing takes effect immediately for anyone loading the page afterward.
Is there a maximum number of parameters I can combine?
No practical limit; URLs can carry many parameters, and all twelve covered here can technically be combined on a single embed at once, though not every combination makes sense together.