![Featured](data:image/svg+xml,%3Csvg xmlns="http://www.w3.org/2000/svg" width="300" height="169" fill="%23333"%3E%3Crect width="300" height="169"/%3E%3Ctext x="50%25" y="50%25" dominant-baseline="middle" text-anchor="middle" fill="%23666" font-size="14"%3EFeatured Post%3C/text%3E%3C/svg%3E)
Resolve any YouTube link into embeds & assets.
Paste a URL and the video materialises: a live embed, every thumbnail, timestamp handling, a click‑to‑load facade for page speed, and downloadable embed cards. All in your browser.
signal
stage
downloadable assets · built locally
embed & share code
paste a link to generate code…
Browsers are not permitted to read YouTube's video streams from another domain (cross‑origin lock + copyright), so no honest page can hand you the MP4 directly. The embeds, thumbnails and code above are fully yours to keep. If you run your own yt-dlp or cobalt endpoint, paste it below and we'll hand the URL to it.
What "resolving" a link actually gives you
The moment you paste, the studio pulls the video id out of whatever shape of URL you threw at it and rebuilds every useful form of that video from scratch. The thumbnail you see is the real poster, the iframe beside it is a real, working embed, and the timestamp you type flows straight into the embed's start parameter and the watch link's t. Nothing about the video is fetched from a server of ours — there is no server.
The facade embed is the one you should ship
A normal embed drops a heavy YouTube iframe onto your page the instant it loads, whether the visitor ever presses play or not. That single iframe is one of the biggest things dragging down Core Web Vitals. The facade code the studio generates shows the thumbnail and a play button instead, and only swaps in the real iframe on click. For a content site that embeds video, that one swap is often the difference between a red and a green Lighthouse score.
Thumbnails you can actually keep
Every resolution YouTube publishes — from the tiny 120×90 frame up to the 1280×720 max‑res still, plus the WebP variants — is offered as a one‑click grab. Where the browser allows the cross‑origin read, the studio paints the frame to a canvas and drops a real PNG into your Downloads; where YouTube blocks that read, it opens the full‑res frame in a new tab so you can save it with a right‑click. Either way you walk away with the image.
Frequently asked
Can this download a YouTube video as an MP4 in the browser?
Not directly, and any tool that claims to do so from pure browser code is misleading you. YouTube serves its video streams from a different domain behind signed, cross‑origin‑locked URLs, so a web page is not permitted to read those bytes. This studio gives you everything that is legitimately yours to keep — the embed, every thumbnail, the embed code, a privacy‑friendly facade embed, and downloadable embed‑card and manifest files — and offers an optional field where you can point it at your own yt‑dlp or cobalt endpoint if you run one.
Which YouTube URL formats does it understand?
All of the common ones: youtube.com/watch?v=, the youtu.be short link, /shorts/, /embed/, /live/, the legacy /v/ path, m.youtube.com, music.youtube.com, playlist URLs, and timestamps written as ?t=90, ?t=1:30 or ?t=1:02:03.
Is anything I paste sent to a server?
No. Parsing, the live embed, the thumbnail preview and every generated file all happen inside your browser. The only outbound request is the embed iframe and thumbnail image, which load straight from YouTube exactly as they would on any page that embeds a video.