YouTube thumbnail sizes, explained

Ask what size a YouTube thumbnail should be and you will get two correct answers about two different things. The first is a set of rules for the file you upload: a shape, a minimum width, resolution guidance, a byte limit, a list of formats. The second is the set of image files YouTube may store for a video — up to 5, not all of them for every upload — and serves back at predictable addresses: the sizes a thumbnail downloader can fetch. The lists are related but not the same, and most confusion about "thumbnail size" comes from reading a number from one list as if it belonged to the other. This guide keeps them apart, says where every figure comes from, and shows what each tool on this site does with them.

Two kinds of number appear below. Official figures are quoted from Google's help article "Add video thumbnails", the same source the size guide cites, re-checked on July 25, 2026. Everything else — the stored sizes, their URLs, the frame ratios, the crop percentages, the parser verdicts — is computed while this page is built by the same tested engines that run in your browser on the downloader, the tester, and the aspect calculator. If an engine changed, this page would change with it or the build would fail.

Meaning one: the rules for the file you upload

These are requirements and guidance for the image you hand to YouTube. They come from Google's documentation, not from measurement:

How to read it. "16:9" is a shape, not a size: it fixes the relationship between width and height without fixing either. "Minimum width" is the only pixel figure that is a hard requirement, and it constrains width alone — the matching height follows from the shape, which at 16:9 is 360 pixels for a 640-pixel-wide image. The 3840×2160 figure is guidance on how large an upload may be, not a demand; it simplifies to 16:9, so it is the same shape scaled up. The byte limits depend on the path the upload takes, which is why three numbers exist. None of these figures says anything about what YouTube stores or serves afterwards — that is meaning two.

The famous rule: 1280×720, under 2 MB

The size repeated everywhere — 1280×720 and under 2 MB — is not in the table as a single rule, but it is not wrong: it is the safe intersection of every device path. The aspect engine confirms 1280 wide at 16:9 is 720 tall with no rounding, 720 tall wants 1280 wide the other way, and the pair simplifies to 16:9. Its width clears the 640-pixel minimum. 2 MB is the strictest of the three byte limits, so a file under it uploads from any device. And 1280×720 happens to be the largest size YouTube serves back (maxresdefault, below), so an upload at that size already matches the largest stored size. Google's current guidance runs up to 3840×2160, so a 4K export uploads fine and YouTube downscales it for display; the classic rule and the current documentation do not conflict.

Why 640 px is the hard floor

Of the numbers in the official table, the minimum width is the one that behaves like a floor: guidance can be exceeded, byte limits vary by path, but a file narrower than 640 pixels does not meet the requirement. It is worth being precise about what the floor measures. It is a width — not a height, not a diagonal — and 640 wide at 16:9 gives 360 tall as a consequence, not as a second rule.

The floor is also where meaning one collides with meaning two. Of the 5 stored sizes, 3 are narrower than the minimum (default at 120, mqdefault at 320, hqdefault at 480), so a thumbnail downloaded at one of those sizes does not meet the upload rule if you send it back. Only sddefault, maxresdefault qualify on width, and sddefault clears the floor by nothing at all: its width, 640, is the minimum exactly. Width is only one of the rules, though: sddefault is a 4:3 frame, not the recommended 16:9, so of the stored sizes only maxresdefault meets both the floor and the recommended shape. Widths that are not multiples of 16 add a wrinkle: 1000 wide at 16:9 wants 562.5 pixels tall, so the aspect ratio calculator reports 563 and flags the rounding instead of hiding it.

Meaning two: the 5 sizes YouTube serves back

Once a video exists, YouTube stores up to 5 thumbnail images for it at addresses that follow one pattern: https://img.youtube.com/vi/{id}/{size}.jpg. The table below is generated by the engine's thumbnailSet function for the illustrative ID jNQXAC9IVRw; the frame column comes from describeRatio on each size's pixel dimensions.

Three things to read off that table. First, the ceiling: maxresdefault at 1280×720 is the largest stored size — there is no 4K thumbnail to fetch, whatever a download button elsewhere promises, and the 3840×2160 figure belongs to meaning one. Second, availability is not uniform: default, mqdefault, hqdefault exist for effectively every public video, while sddefault, maxresdefault are generated only for some uploads. Third, the frames: 3 of the 5 stored sizes (default, hqdefault, sddefault) are 4:3 frames, so the pixel dimensions you download from those addresses are the frame's, not the shape of a 16:9 thumbnail; only mqdefault, maxresdefault are 16:9. The downloader names each file after the ID, the size key, and the pixels — youtube-jNQXAC9IVRw-maxresdefault-1280x720.jpg — so a folder of downloads stays readable later.

How the downloader knows a size really exists

When one of the 2 conditional sizes (sddefault, maxresdefault) is missing, YouTube answers with HTTP 404 — but the body of that response is a gray 120×90 placeholder image. A plain <img> tag renders it, and a careless tool offers it as a download. ThumbnailPro checks two signals, the HTTP status of the fetch and the decoded pixel width of the image, and only a size that passes both gets a download button. The classifier is a pure function, so its verdicts can be shown directly:

The default row matters: that size is itself 120×90, so a small decode there is legitimate, and the classifier treats a small decode as a placeholder only when the size requested was larger. The fetch is possible at all because YouTube's image server sends Access-Control-Allow-Origin: * on thumbnail responses (verified empirically), so your browser talks to YouTube directly and this site's servers never see the link; if something in your environment strips those headers, the tool degrades to "Open image" links rather than pretending a download happened. Why maxresdefault in particular is so often absent has its own guide: Why maxresdefault is missing.

Which links produce a video ID

None of the stored sizes can be fetched without the 11-character ID, so the downloader begins by parsing whatever was pasted. It accepts the forms people actually share and rejects the rest with a specific reason rather than a generic error. The verdicts below are the parser's own output at build time:

A third size nobody uploads: display size

There is a third list, easy to mistake for either of the first two: the pixel sizes at which video surfaces display a thumbnail. The tester renders your image at the home grid card (desktop) at 320×180, suggested / sidebar row at 168×94, search result row at 246×138, mobile list row at 160×90, plus a legibility strip at 120, 168, 246 pixels wide. These are honest current typicals of how video platforms size those surfaces — platforms shift them a few pixels with every redesign — so they are labelled typical, not a spec, and none of them is an upload rule or a stored size.

Other shapes, and what a 16:9 cover slot does to them

The tester models each display slot as a 16:9 "cover" slot: the image is scaled until it fills the slot and whatever overflows on one axis is hidden. In that model — and it is the tester's model, not a statement about any platform's player — an image of any other shape is cropped: a wider image loses width, a taller one loses height. The size guide, which cites Google's help page for the 16:9 recommendation, notes that a different shape gets cropped or letterboxed by the player surfaces; the figures below are the tester's cover-crop geometry only. The table takes the maxresdefault width of 1280, asks the aspect engine for each common ratio's height (flagging where no whole pixel exists), then asks the tester's crop function what a 16:9 cover slot would discard:

Common misreadings

• "Google mentions 4K, so I can download a 4K thumbnail." The 3840×2160 figure is upload guidance. The largest stored size is 1280×720.
• "sddefault is the standard-definition 16:9 version." It is 640×480, a 4:3 frame, and it exists only for some uploads.
• "hqdefault is high quality, so it will do for re-upload." The label describes a size key, not a grade; at 480 pixels wide it is below the 640-pixel minimum.
• "The limit is 2 MB." That is the mobile figure; desktop allows 50 MB and podcasts 10 MB. Under 2 MB is simply the number that works everywhere.
• "640 is the minimum size." It is the minimum width. Height follows from the shape (360 at 16:9); the official table lists no separate minimum height.

Frequently asked questions

Every figure in this guide that is not cited to Google's documentation was computed at build time by the same engine that runs locally in your browser on the downloader, the tester, and the aspect calculator, so the tables cannot drift from the tools; nothing you paste or load into those tools is transmitted to this site — the downloader's only network requests are your own browser fetching images directly from YouTube. See the methodology page for how the engines are tested. Official figures verified against Google's help documentation on July 25, 2026; conventions are labeled as conventions. If Google changes the rules, the contact page is the fastest way to tell us. ThumbnailPro is not affiliated with YouTube or Google.