YouTube Thumbnail Not Loading: Six Causes, and How to Tell Them Apart
When a thumbnail is not loading, the instinct is to blame the image. The measurements say otherwise. In every pass we have run (2, 5, 11 and 12 October 2026, 24 public videos), a missing name did not return an error — it returned a valid 1,097-byte JPEG at 120 × 90, which browsers and viewers display without complaint. So "not loading" (the same symptom people also describe as "not showing", "blank", "grey square" or "blurry") is usually one of six specific things, and each one has a different check. The two that account for most cases are worth stating up front: the 1280 × 720 file existed on only 10 of 12 videos, and the file a watch page normally displays is 480 × 360, not the big one.
Start with these three checks — they settle most cases
- Byte count. 1,097 bytes is the placeholder. It is identical on every miss in every pass. A real file in the same runs started at 2,888 bytes — at the very same 120 × 90 size.
- Pixel size from the file's own header, not the name.
maxresdefault.jpgcame back 1278 × 720 on one video, so the name does not pin the dimensions. - Whether that name exists at all for that video.
hqdefault.jpganswered on 12 of 12 videos;sddefault.jpgon 11 of 12;maxresdefault.jpgandhq720.jpgon 10 of 12.
The symptom table
| What you see | What it usually is | The check |
|---|---|---|
| Nothing at all, or a broken-image icon | A wrong shape of token: a playlist ID, a channel ID or handle, an ID one character off, or the right ID in the wrong case | Is the token exactly 11 characters of A-Z a-z 0-9 _ -? Case matters |
| A small grey square | The placeholder — that name does not exist for this video | 1,097 bytes = placeholder |
| An image that looks soft or blurry | A 480 × 360 file being displayed larger than it is | Read the width and height out of the file |
| Blurred bars on the left and right | A Short, shown through a landscape file | Ask for oar2.jpg instead |
| The old picture, after the creator changed it | A cache, not a bug | Wait — real files carry max-age=7200 |
| A big file when you expected a small one, or the reverse | Two names, two different files — or the same file under both | Compare bytes, not names |
"Not loading", "not showing", "blank" — one symptom, several names
People describe this differently depending on where they are looking, and the wording sends them to different advice for what is the same fault. A thumbnail that will not load in the YouTube app, one that is not showing in search results, one that is blank on the watch page and one that is a grey square are, in the measurements below, the same short list of causes. The check is identical in every case: fetch the file and read its byte count and its pixel size. 1,097 bytes is the placeholder; anything else is a real picture, and if it looks wrong the problem is which file was fetched, not whether one was.
Two wordings are worth separating out, and both have their own section below. A picture that is soft or blurry is not a loading failure at all — it is a 480 × 360 file being shown too large (Cause 4). And a Short with blurred bars down the sides is loading fine; it is simply the wrong shape (Cause 5).
Cause 1 and 2: the token was the wrong shape, or the wrong case
These are the only cases that can genuinely produce "nothing". We fed 10 different pasted strings to the image host on 8 October 2026 exactly as a downloader would, and only 3 returned a picture. A playlist ID (34 characters), a channel ID (24), a channel handle (17), a whole playlist URL, a whole channel URL, an ID one character short and an ID one character long all failed. Case matters too: on 2 October 2026, DQW4W9WGXCQ returned the placeholder while dQw4w9WgXcQ returned 65,324 bytes at 1280 × 720. The "get a thumbnail" page lists the eleven link shapes that all resolve correctly.
Cause 3: the name does not exist for that video
The commonest cause by far, and the one that looks like a bug because the server does not say so. The response is a valid image — 1,097 bytes at 120 × 90, a plain grey square, cached for 30 seconds instead of the 7,200 a real file gets. Two videos in twelve had no 1280 × 720 file under any name. Fall back in this order and keep the first address that is not 1,097 bytes:
maxresdefault.jpg → hq720.jpg → oar2.jpg → sddefault.jpg → hqdefault.jpg → mqdefault.jpg → default.jpg
And do not assume "one size down" is the fix: one video in our 5 October sample had neither 1280 × 720 nor 640 × 480 and topped out at 480 × 360 at 23,549 bytes, while another had no 1280 × 720 but still served 640 × 480 at 62,587 bytes. The availability page has the full breakdown.
Cause 4: "blurry" is a size problem, not a quality problem
This is the most misdiagnosed one. On the 3 regular watch pages we read on 12 October 2026, the thumbnail address hqdefault.jpg appeared in all 3, and maxresdefault.jpg in just 1. hqdefault.jpg is 480 × 360 — perfectly sharp at the size a page displays it, soft the moment anything shows it bigger. If you took that file and enlarged it, you made the softness worse and permanent: 480 × 360 to 1280 × 720 is 5.33× the pixels and zero new information. The fix is never to sharpen; it is to fetch the bigger file that was there all along. The resize page covers the arithmetic.
Cause 5: blurred bars down the sides of a Short's thumbnail
If the picture is sharp in the middle and smeared at the edges, you are looking at a landscape file being used for an upright video. On 12 Shorts measured on 12 October 2026, maxresdefault.jpg and hq720.jpg were 1280 × 720 landscape on 12 of 12 — the upright frame placed in the middle with blurred filler either side. We compared the middle 405-pixel band against the two side bands on 6 of them: the sides carried only 7% to 30% of the middle's edge detail and were measurably darker (mean brightness 8.9–53.3 against 34.7–139.2). The genuinely upright file is oar1.jpg, oar2.jpg or oar3.jpg — 1080 × 1920 on 12 of 12. The Shorts page has the details.
Cause 6: it is showing you the old picture
Not a failure at all — a cache doing its job. Every real file we captured carried Cache-Control: public, max-age=7200, so a thumbnail the creator replaced can keep appearing as the previous version for up to two hours. The asymmetry is worth remembering: a wrong ID clears in 30 seconds (that is the placeholder's max-age), while a changed thumbnail can linger for 7,200. Past that window the file is settled — 114 of 114 addresses we re-requested a day later came back byte-identical.
The 404 that is not a 404
Worth stating plainly because it breaks naive error handling. Ask for a name that does not exist and you do get an HTTP 404 — but the body is not an error page. It is a 1,097-byte JPEG, image/jpeg, 120 × 90, with Cache-Control: public, max-age=30 and no Accept-Ranges. Anything that trusts the status code will handle it correctly; anything that trusts "did an image load?" will not, because one did. Two more 404 traps from the same runs: a HEAD request on a missing name answers 404 with Content-Length: 1097, and asking for .webp on the image host returns 404 whose body is a JPEG — so a file ending in .webp can be a JPEG of nothing at all.
Two things that look like a quality setting but are not
There is no quality knob in the address; there is only which file you asked for. Within one name the bytes vary enormously between videos — hqdefault.jpg ranged from 15,921 to 53,433 bytes in our sample, always at 480 × 360. And two names can hold the same picture at very different sizes: on one video maxresdefault.jpg was 108,323 bytes at 1278 × 720 while hq720.jpg was 179,638 bytes at 1280 × 720, a 71,315-byte gap behind the same 720p label. Across a 10-video check the two names were byte-identical on 9 and different on 1. So if two tools show you visibly different "same" thumbnails, that is not a quality setting disagreeing — they fetched different files.
Questions people actually ask
"Why is the thumbnail not loading even though the video plays fine?"
Because the video and the thumbnail are separate files, and the one you asked for may not exist. Two videos in twelve had no 1280 × 720 file at all. Ask for hqdefault.jpg — it answered on 12 of 12 videos in our sample. If you came here because a thumbnail is not showing in search results or in the app rather than on the watch page, the same six causes apply.
"Is there a thumbnail quality setting I am missing?"
No. There is no quality knob anywhere in the address — only which file you asked for. Two tools can show you visibly different "same" thumbnails because they fetched two different files, not because one of them used a better setting.
"Is a grey square a broken download?"
No, it is a complete download of a placeholder. 1,097 bytes at 120 × 90, valid JPEG, opens anywhere. Compare the byte count rather than trusting that the image loaded.
"Why is my thumbnail blurry when the video is sharp?"
You almost certainly have the 480 × 360 file. That is the file watch pages themselves load most of the time, and it looks fine at page size. Fetch maxresdefault.jpg or hq720.jpg instead of enlarging it.
"Why is only the middle of my Short's thumbnail sharp?"
Because a 1280 × 720 landscape file was used for an upright video, with blurred filler at the sides. The side bands carried 7% to 30% of the middle's edge detail in our measurement. Use oar2.jpg.
"I replaced the thumbnail and it still shows the old one. How long?"
Up to about two hours, per the max-age=7200 on real files. A wrong ID is the opposite case — the placeholder is cached for only 30 seconds, so a typo fixes itself almost immediately once you correct it.
Every number on this page was measured by requesting img.youtube.com/vi/<id>/<name> directly and reading each response's status, headers and body. Sources: 2 October 2026 — 4 public videos × 26 names plus ID and case variants (124 requests); 5 October 2026 — 12 public videos, all names (hit counts and the 480 × 360 top-out cases); 11 October 2026 — 8 videos × 5 names plus 11 follow-up requests covering HEAD, ranges, the placeholder and the two WebP addresses; 12 October 2026 — 12 Shorts × 12 names plus 118 follow-up requests, and the HTML of 7 Shorts and 3 regular watch pages. The 1,097-byte placeholder figure is exact and identical in every pass. Videos and pages are identified by ID only — no titles, channel names or watch links appear on this page, and no thumbnail is hosted here. A different sample of videos would move these counts, which is why every count is given with its sample size attached.