YouTube Embed Code Generator

Paste any YouTube watch URL, youtu.be link, /shorts/ URL, or 11-character video ID and this tool builds a customizable <iframe> embed code. Toggle autoplay, loop, and controls, set start/end times, choose width × height (16:9 lock available), and pick privacy mode (youtube-nocookie.com) or standard. Live preview, copy-ready code, no upload, no signup.

What is a YouTube embed code generator?

A YouTube embed code is a small <iframe> snippet that loads YouTube's player on your own page. The browser fetches the player from YouTube, plays the video inside the frame, and pipes user controls back through YouTube's IFrame Player API. The frame's src URL — https://www.youtube.com/embed/{videoId} — is the only piece YouTube actually reads. Everything else (autoplay, loop, controls, start/end) is appended as query-string parameters that the player checks on load.

This generator builds that snippet for you. Paste a watch URL, youtu.be short link, /shorts/ link, or a bare 11-character ID; flip toggles for the playback options you want; and copy the result. The output is a single iframe — no JavaScript, no third-party loader, nothing to install. Paste it into HTML, Markdown, a CMS rich-text field, a Notion page, a Substack post, or wherever embeds are accepted, and the player loads on first paint.

Why customize an embed?

Defaults work fine when an embed is the focus of the page, but they're rarely right for hero videos, course platforms, kiosks, or marketing sites where the video is supporting content. Autoplay + mute + loop is the standard recipe for a background hero. Start time jumps past intros so a citation lands on the right moment. Hidden controls let the embed feel native rather than like a YouTube widget. Privacy mode defers cookie writes until the user actively plays, which simplifies consent flows under GDPR and ePrivacy rules. Most of these options aren't exposed by YouTube's share-dialog copy, which is why a separate generator is useful.

Embed privacy: what cookies a YouTube iframe drops

A YouTube embed is a network call to Google. Even before the user clicks play, the standard youtube.com/embed/{id} iframe loads JavaScript and image assets from googlevideo.com and sets a few session cookies — VISITOR_INFO1_LIVE, YSC, and a couple of analytics cookies. The privacy-enhanced host (youtube-nocookie.com) defers all of those until the user actually starts playback. For consent banners that block trackers by default, this is the difference between an embed that loads on first paint and an embed that needs a click-through. We default to nocookie because most pages benefit from it; switch to youtube.com only when you specifically need standard YouTube behavior.

Why does autoplay only work when muted?

Browsers block auto-playing audio by default. Chrome, Safari, Firefox, and Edge all enforce a media engagement policy: a video may auto-play only if it's muted, or if the user has previously interacted with the site at a meaningful level. The practical consequence for embeds is that autoplay=1 works reliably only when paired with mute=1. If you uncheck mute while autoplay is on, this tool surfaces a warning and the live preview will autoplay silently in some browsers and not at all in others — which is exactly what real visitors will experience. The fix is one of two things: keep mute on, or drop autoplay and let the user press play themselves. There's no third option.

youtube-nocookie.com vs youtube.com

Both hosts serve the same player and the same video. The difference is in cookie behavior. youtube.com sets a small set of session and analytics cookies on first frame load — even if the user never clicks play. youtube-nocookie.com defers cookie writes until the user explicitly starts playback. For a page that mostly shows the player but where most visitors don't watch, the nocookie host is the right default — fewer cookies dropped per visitor, simpler consent flows under GDPR / ePrivacy, and identical behavior when a user actually plays the video. There's no quality difference, no playback feature you lose, and no SEO penalty for using either host. This tool defaults to nocookie for that reason.

Deprecated parameters and what replaces them

A few embed parameters you'll see in older snippets are dead. showinfo=0 and rel=0 were retired in 2018 — the player ignores both. cc_load_policy=1 still works for forcing captions on, but YouTube also reads the viewer's account preference, so it isn't a guarantee. The enablejsapi=1 flag isn't deprecated, but it's only useful if you're calling the IFrame Player API from JavaScript on the host page; for a static embed it's noise. We omit all of these from the generated snippet by default — fewer bytes, fewer surprises, and nothing the player will ignore.

What this generator does not include

We deliberately omit a handful of options that shipped on older embed generators. The deprecated showinfo, rel, and stand-alone color tweaks (color=red/white) are out — the player no longer reads them. The fs=0 flag for hiding the fullscreen button is rarely useful on real sites, so it's not exposed; you can edit it into the generated code by hand if you need it. enablejsapi=1 only matters when you're scripting the player from your own page, which is a separate workflow from a static embed and out of scope here. Captions are available through cc_load_policy, but they default to the viewer's account preference — adding a checkbox here would mislead users into thinking it's a guaranteed switch, so we leave it off.

Embed parameters at a glance

These are the parameters the IFrame Player API actually reads. Anything not listed here is ignored or deprecated.

Each row maps to one URL parameter on the iframe <code>src</code>. Parameters set to their default value are omitted from the generated code so the snippet stays small.

Common Uses

• Blog posts and articles: embed a video at a specific timestamp using the start parameter to skip intros and land readers on the cited moment.
• Marketing pages and landing sites: use a muted, autoplaying, looping background hero video to set tone without the audio competing with copy.
• Documentation and tutorials: embed a clipped segment with start and end times set, so each step links to its own video region.
• Privacy-first websites: use the youtube-nocookie host so embeds load without setting tracking cookies until the user actively presses play.
• Kiosks and digital signage: turn off controls and loop a single video for a clean, minimal display surface.
• Course platforms and LMS embeds: drop a sized iframe into a lesson page where you can't run third-party scripts but plain HTML is allowed.

How this compares to YouTube's official embed code

YouTube's own share dialog gives you an embed code, but it's a one-shot copy: you get a fixed snippet with a hard-to-customize default size (560×315), a checkbox for start time, and a privacy-mode toggle. Anything else — toggling controls, looping a single video, setting an end time, picking a non-default size — has to be edited by hand or wired up through the IFrame Player API. The official code is also chattier (extra attributes, a slightly older allow list) than what the player actually requires.

This generator gives you all the parameters the player honors in one form, with a live preview that updates as you toggle. The output is the minimum surface that reflects your choices: defaults are omitted, deprecated parameters are skipped, and the iframe attributes match the modern allow spec. Single-line output goes straight to the clipboard so it pastes cleanly into JSX, Markdown, and CMSes that gag on multi-line attributes; the multi-line view is purely for human reading.

Related YouTube tools

• Download YouTube thumbnails — Grab a single video's thumbnails at every resolution from default to Max HD.
• Download YouTube Shorts thumbnails — Same as the thumbnail downloader, but tuned for /shorts/ URLs with the SHORTS badge.
• Compare YouTube thumbnails — Lay two videos' thumbnails side-by-side at every resolution. Useful for A/B research and competitor study.

By the Numbers

• 200×113 minimum: below this size, YouTube's player hides its own controls and shows a smaller fallback. Above that, every dimension up to 4096px on a side renders cleanly. The default 560×315 is YouTube's own historic embed size; 16:9 holds at any pair that satisfies height = width × 9 ÷ 16.
• ~310 bytes per snippet: the generated single-line iframe is between roughly 280 and 360 bytes depending on options. By comparison, a standard YouTube share-dialog embed is closer to 420 bytes because it includes attributes (referrerpolicy, full title) that aren't strictly required.
• 2 hosts, 7 parameters: two iframe hosts (youtube.com, youtube-nocookie.com) and seven parameters that the player actually reads (autoplay, mute, loop, playlist, controls, start, end). Anything beyond that is either deprecated or only useful from the IFrame JavaScript API.

Sources & Further Reading

• YouTube IFrame Player API — parameter reference
• Chrome — Autoplay policy explained
• MDN — <iframe> element reference
• W3C WAI — Accessibility for media
• YouTube Help — Embedded videos