maxresdefault Is Not the Only 1280 × 720 File: maxres1, maxres2, maxres3
Everyone learns one file name and stops: maxresdefault.jpg. But the image host answers to four names at that size — maxresdefault, maxres1, maxres2, maxres3 — and they are four different files, not four aliases. We fetched all of them, decoded every one, and hashed the bytes, on 24 October 2026. Two findings change what a thumbnail tool should do. First, which of the four is the largest is not fixed: across 12 videos the winner was maxresdefault six times and one of the other three (or hq720) the other six, with the largest file up to 3.83× the smallest. Second, and more useful: on the videos where maxresdefault returns 404, the numbered names were still there on 5 of 6 — so a tool that stops at "no maxresdefault" is leaving a 1280 × 720 picture on the table. Every number below is a response we read, and the pixel counts come from decoding the file, not from what any table says.
Which name is biggest? It changes video by video
These are raw byte counts from twelve videos — five names each, all requested in one pass. The winner is marked in bold.
| Video | maxresdefault | maxres1 | maxres2 | maxres3 | hq720 | Biggest |
|---|---|---|---|---|---|---|
| 1 | 65,324 | 40,095 | 38,549 | 41,883 | 65,324 | maxresdefault |
| 2 | 108,323 | 46,862 | 101,833 | 55,989 | 179,638 | hq720 |
| 3 | 184,051 | 51,873 | 63,737 | 78,231 | 184,051 | maxresdefault |
| 4 | 82,327 | 42,813 | 71,978 | 54,971 | 82,327 | maxresdefault |
| 5 | 404 | 36,873 | 36,344 | 31,194 | 404 | maxres1 |
| 6 | 404 | 49,944 | 30,241 | 33,481 | 404 | maxres1 |
| 7 | 80,870 | 78,641 | 72,759 | 72,447 | 80,870 | maxresdefault |
| 8 | 81,713 | 52,577 | 72,950 | 85,377 | 81,713 | maxres3 |
| 9 | 94,891 | 72,203 | 85,948 | 75,874 | 94,891 | maxresdefault |
| 10 | 86,484 | 77,851 | 77,968 | 69,256 | 86,484 | maxresdefault |
| 11 | 404 | 72,452 | 127,897 | 48,654 | 404 | maxres2 |
| 12 | 404 | 119,875 | 79,188 | 104,075 | 404 | maxres1 |
Six wins for maxresdefault, six for something else. The spread inside a single video reached 3.83× between its largest and smallest of the five names (row 2), and the smallest spread was 1.12×. So "the biggest file" is a question you answer per video by comparing byte counts — not a fact you memorise.
Row 2 hides a second surprise worth its own sentence: that video's maxresdefault decodes to 1278 × 720, not 1280 × 720, while its hq720 is a full 1280 × 720 and 179,638 bytes. The name says "max res"; the pixels say otherwise, and a different name gave the wider file.
Four names, four different files
These are not the same bytes served under several names. On one video the four 1280 × 720 names produced four distinct SHA-1 fingerprints — and the two that looked interchangeable by name are the ones that differ most in content:
| Pair compared (same 1280 × 720 canvas) | Mean pixel difference, 0–255 | How to read it |
|---|---|---|
maxres2 vs maxresdefault | 0.45 | the same picture, re-encoded — indistinguishable |
maxres1 vs maxres3 | 12.56 | close, but visibly not the same file |
maxres1 vs maxresdefault | 42.86 | a different picture |
maxres3 vs maxresdefault | 41.92 | a different picture |
maxres1 vs maxres2 | 42.85 | a different picture |
On a second, older video the same comparison gave 76.56, 87.76, 72.72 and 57.40 for the pairs involving the default — even further apart. (Reading this honestly: the numbered names sometimes hold the same artwork at a different compression and sometimes hold different artwork entirely. We can measure the difference; we cannot measure which one the creator considers current, so we do not claim these are "earlier versions".)
hq720 is sometimes the same file and sometimes a bigger one
hq720 looks like a separate rung and behaves like an alias of the maxres family — but the aliasing is not guaranteed. On one video all four hq720 variants matched their maxres counterparts byte for byte (hq720 = maxresdefault 65,324 B, hq720_1 = maxres1 40,095 B, hq720_2 = maxres2 38,549 B, hq720_3 = maxres3 41,883 B, identical SHA-1 in every pair). On row 2's video it is a different and much larger file: 179,638 B against the default's 108,323 B. So the rule "hq720 is just another name for maxresdefault" is true often enough to be useful and false often enough to cost you the biggest file.
When maxresdefault is gone, the numbered names are still there
This is the part with practical value. Across 32 videos (thirty from one channel plus two long-standing public uploads), maxresdefault returned 404 on 6 of them. On 5 of those 6, maxres1, maxres2 and maxres3 all returned 200 at a genuine 1280 × 720:
| Video without maxresdefault | maxres1 | maxres2 | maxres3 | Pixels (decoded) |
|---|---|---|---|---|
| 1 | 72,452 B | 127,897 B | 48,654 B | 1280 × 720 each |
| 2 | 119,875 B | 79,188 B | 104,075 B | 1280 × 720 each |
| 3 | 72,707 B | 70,060 B | 66,674 B | 1280 × 720 each |
| 4 | 70,365 B | 94,626 B | 79,717 B | 1280 × 720 each |
| 5 | 36,873 B | 36,344 B | 31,194 B | 1280 × 720 each |
| 6 — the one exception | 404 | 404 | 404 | nothing at this size at all |
The sixth is an upload from 2005 that has no 1280-wide file under any of the names. And note what does not rescue you: on all four of these videos, hq720 returned 404 alongside the missing maxresdefault, so the alias cannot stand in. Only the numbered names can. That is the correction to the usual fallback ladder — before dropping to 640 × 480, ask for maxres1, maxres2, maxres3.
The numbering is on every rung, not just the top
One more measurement, because it changes how you probe a single video. The suffix 1, 2, 3 works on each of the four standard rungs, and each numbered file is a distinct file at the same canvas size:
| Rung | base name | …1 | …2 | …3 | Canvas |
|---|---|---|---|---|---|
| 1280 × 720 | 65,324 | 40,095 | 38,549 | 41,883 | 1280 × 720 |
| 640 × 480 | 31,029 | 18,854 | 18,930 | 21,734 | 640 × 480 |
| 480 × 360 | 21,011 | 6,753 | 6,778 | 7,698 | 480 × 360 |
| 320 × 180 | 10,303 | 4,388 | 4,370 | 5,184 | 320 × 180 |
So the real name space is four rungs × four variants = sixteen files for one video, plus the hq720 aliases and the WebP twins. Every figure above came from a 200 response with the bytes counted — the placeholders (1,097 B / 120 × 90) are what a name that does not exist returns, and the verification page shows how to tell that apart from a real file.
What the documented API says, and does not say
None of these numbered names appears in the official documentation. The snippet.thumbnails object is documented with exactly these keys — default, medium, high, standard, maxres, fhd, qhd, uhd — and the page we read on 24 October 2026 describes maxres as "1280px wide and 720px tall" and fhd as "1920px wide and 1080px tall", added "for some videos". There is no maxres1 in that list, no numbered variant of anything, and no note that the file behind the maxres key can come back 1278 pixels wide.
Two honest limits on that paragraph: it is a quotation of a documentation page, not a measurement of an API response — we did not call the API with a key, so we do not claim what it returns. What we did measure is the image host, and the image host is what your download URL talks to. If you are choosing between the API and the URL, the cache page covers the lifetimes and the CORS page covers which files a browser can read.
What to actually do
- Do not stop at one name. Request
maxresdefault,maxres1,maxres2,maxres3andhq720; keep the largest 200. On our sample that decision changed the winner on half the videos. - When
maxresdefaultis 404, keep going. The numbered names were present on 5 of 6 such videos at a real 1280 × 720.hq720will not help — it 404s with it. - Check the file's pixels, not just the name. One video's
maxresdefaultwas 1278 × 720 while itshq720was 1280 × 720. Two numbers, two different stories. - Decide whether you want "biggest" or "current". A numbered file can be 42–88 units away (on a 0–255 scale) from the default — a different picture, not a sharper copy of it. If you need the thumbnail as the creator set it, take
maxresdefault; if you need the most pixels and can live with a different frame, compare all five. - Do not assume the numbering stops at 3. We tested
1–4; four returned 404 on every video we tried, so we report three as the last one that exists in this sample and make no claim beyond it.
Questions people actually ask
"Is maxresdefault.jpg the largest thumbnail available?"
Not always. On 6 of 12 videos measured, one of maxres1, maxres2, maxres3 or hq720 was larger — up to 3.83× the smallest of the five, and on one video hq720 came in at 179,638 bytes against the default's 108,323.
"My video returns 404 for maxresdefault. Is there nothing bigger than 480 × 360?"
Usually there is. On 5 of the 6 videos in our sample that had no maxresdefault, maxres1, maxres2 and maxres3 all returned real 1280 × 720 files. Only an upload from 2005 had nothing at that size.
"Why do maxres1 and maxresdefault look like different pictures?"
Because they are. On one video the mean pixel difference between them was 42.86 out of 255 — the same scale where 0.45 meant "the same picture, re-encoded". The numbered names are not guaranteed to hold the artwork you saw on the watch page.
"Do these names come from the YouTube Data API?"
No. The documented thumbnails object lists default, medium, high, standard, maxres, fhd, qhd, uhd — no numbered names at all. They are an image-host behaviour, and we are reporting what the host returned, not what a spec promises.
"Is hq720 just another name for maxresdefault?
Sometimes, exactly: four pairs came back with identical SHA-1. Sometimes not: on another video it was 71,315 bytes heavier and 1280 pixels wide where the default was 1278. Treat it as a fifth candidate to compare, not as a duplicate.
Every figure on this page was produced by us on 24 October 2026: 50-name probe on one video, five names × twelve videos with bytes and decoded pixels, four names × thirty-two videos for availability, pairwise pixel differences computed from the decoded files, and four hq720/maxres pairs hashed and compared. Video IDs are given only as row numbers; no title, channel name or image is reproduced. Two things we did not do and therefore do not claim: we did not call the Data API with a key, so the documentation paragraph is a quotation and not a measurement; and we could not establish what the numbered files are — only that they exist, differ, and are sometimes the only 1280-wide copy. Nothing on this page is an estimate.