YouTube Thumbnail Download: Why maxresdefault Is Missing

PublishedToolYouTube Thumbnail Downloader: Up to 1280×720

Contents
  1. Why maxresdefault won't open: and why it feels like it's just you
  2. How to check without a tool: swap the filenames one by one
  3. Why Some Videos Have No High-Quality Thumbnail at All
  4. Comparing by Quality and Use Case
  5. Where People Get Stuck
  6. Copyright: How Far Can You Go?
  7. How is this different from similar methods?
  8. The short version
  9. Frequently asked questions

If you've ever added maxresdefault.jpg to a YouTube thumbnail URL and gotten a broken image instead of a picture, it's not your browser or your account. That video simply has no 1280×720 thumbnail file on the server in the first place.

This post covers how YouTube creates and serves thumbnails, why some videos are missing the highest-resolution thumbnail, and how to check which sizes actually exist for a video you're looking at — no tool required. We'll also get into why file sizes differ by resolution and why you can't download the video file itself the same way.

Summary ① YouTube thumbnails come in just five fixed filename tiers: maxresdefault, sddefault, hqdefault, mqdefault, and default. ② For videos uploaded at lower quality, the larger thumbnail files are never generated, so maxresdefault may not exist at all. ③ Manually swapping filenames means you can't know in advance what exists, so filtering to only the sizes that are there is much faster.

Why maxresdefault won't open: and why it feels like it's just you

Maybe you wanted to save a video's thumbnail in high resolution for YouTube channel art or a blog thumbnail. Search around and you'll find plenty of advice telling you to type img.youtube.com/vi/VIDEO_ID/maxresdefault.jpg into your browser's address bar to grab the highest-quality image directly. Try it a few times and it really does work, which makes you think you've found the answer — so you do the same thing on the next video.

But once you use it across a bunch of videos, you find that it works for some and not others. Popular music videos or videos from big channels load a large image just fine, while personal vlogs, older videos, and videos uploaded at low quality often show a blurry or broken image instead. The method that worked on the last video suddenly fails on the next one, so it feels like some rule has broken. And when a forum post or blog says "this always works" and it doesn't, you start wondering whether you did something wrong.

At that point you usually blame one of two things. Either you typed the URL wrong, or YouTube has blocked this method. Neither is true. The answer is much simpler: that video never had a 1280×720 thumbnail file stored on YouTube's servers in the first place. You can't load a file that doesn't exist, no matter how precisely you type the URL. Retype it a hundred times, try another browser, switch computers — the result is the same. It's not your connection or your network; the file simply isn't there, and no workaround changes that.

The trouble is there's no easy way to know in advance. Before you play a video, it's hard to judge how good the original quality was, and a channel's subscriber count or view count doesn't guarantee a high-resolution thumbnail. The playback quality shown on screen (say, 480p or 720p) can feel different from the original quality at upload time, so you might look at the player, assume "this one must have the high-res thumbnail too," and be wrong.

That uncertainty gets worse when you're handling thumbnails in bulk. If you're building a comparison table or catalog of videos, some entries will get a big image and others a small one, and the whole thing stops looking consistent. If you knew ahead of time which videos support the highest resolution, you could design the layout around that. But you can't know until you open each one, and that's the frustrating part.

So you open the URL, see it break, and only then learn "ah, this video doesn't have it." For a single video, that trial and error is no big deal. But when you're collecting and organizing thumbnails for many videos at once, or comparing them, the same process repeats every time and adds up to a lot of wasted time.

This comes up more often when you're managing content. Say you're putting together a playlist cover or a roundup post from videos you like. You look through the thumbnails for ten or twenty videos at once, and a few of them stand out as noticeably worse. At first you think it's an editing mistake, but it turns out those are the videos with no maxresdefault, so a lower-resolution image got used instead. This happens a lot with older videos or content that was shot or recorded at a low resolution from the start — screen recordings saved at low resolution and uploaded as-is, or videos shot on old equipment where the source file itself is small.

How to check without a tool: swap the filenames one by one

YouTube exposes thumbnails at predictable filenames, so once you know the pattern you can check by hand. No login or API key needed — just your browser's address bar.

  1. Copy the 11-character video ID that comes after v= in the video page URL. If it's a short youtu.be link, the ID is the part right after the domain. For a Shorts video, it's the part after shorts/.
  2. Type img.youtube.com/vi/VIDEO_ID/maxresdefault.jpg into your browser's address bar and open it.
  3. If a normal image appears, the video has a 1280×720 thumbnail. Right-click and save it. Before you save, check the actual pixel dimensions with a menu like "View image info" so you know exactly which file you saved.
  4. If you get a broken image or a blurry gray screen, change only the filename part of the URL to sddefault.jpg and reload. If that fails too, work your way down: hqdefault.jpg, mqdefault.jpg, then default.jpg.

hqdefault.jpg exists for practically every video, so by the time you get there you can usually see an image. On mobile browsers, long-pressing the image to save it does the same thing as right-clicking on a computer, so you can check the same way without a PC. The problem is repeating this for every single video. You have to open all five tiers in order, type the filenames exactly by hand, and it's easy to lose track of the actual pixel dimensions just by looking at the screen.

If you need to process several videos at once — collecting thumbnails for a lecture list or playlist cover, for example — that five-step check multiplies by the number of videos. Ten videos means changing the URL at least ten times, and as many as fifty. If you want to know which sizes exist before clicking through them, that repetition becomes a real burden. And one typo in a filename gives you a misleading result, which is another weakness of doing it by hand.

To cut down on that hassle, we built our free YouTube Thumbnail Downloader: Up to 1280×720. Enter a single video URL and it checks all five tiers for you, showing only the sizes that actually exist. No memorizing filenames or editing URLs by hand — just pick the resolution you want from the list on screen.

The manual process isn't hard in itself. The problem is repeating it for every video: trying five URLs in order and judging the results by eye. The maxresdefault step is especially frustrating, since you can't know whether it exists until you open it and see — so checking turns into trial and error.

YouTube Thumbnail Downloader: Up to 1280×720

Free · no login needed · one video URL shows only the sizes that actually exist

Only sizes that actually exist are listed, so you won't hit a broken image — you can check the resolution you want and save it right away.

Why Some Videos Have No High-Quality Thumbnail at All

A YouTube thumbnail isn't an image that gets generated fresh every time someone requests it. It's a static file that already sits at a fixed filename on the img.youtube.com address, and the server just hands it over. So once you know the filename pattern, anyone can get the same picture from the same address, and that pattern doesn't change randomly from video to video. Think of it this way: the image isn't redrawn on each request, it's just pulled from a warehouse of files that were built ahead of time.

Locking the name itself to a resolution like this also helps developers and service operators. If you know the video ID, you can assemble the image address directly in any programming environment, with no separate lookup step. This tool works on the same principle: it pulls the ID out of the video URL, builds the five addresses in order, and checks whether each one actually opens.

When images are pre-built and pinned to fixed addresses, many services and many people can request the same video's thumbnail at the same time and get the same file back over and over, with nothing built on the fly. That's also why countless screens in and around YouTube — search results, recommended video lists, share previews — reuse the same addresses.

The filenames confirmed so far are five. maxresdefault is 1280×720, sddefault is 640×480, hqdefault is 480×360, mqdefault is 320×180, and default is 120×90. The key point is that there's no separate number tacked onto the name — the name itself is a fixed specification that points to a resolution. The moment you see maxresdefault, you can read it as "the highest resolution this video can have," and default reads the opposite way: "the bare minimum size that's always available."

Open all five steps for one well-known video and the pattern shows up as-is. For the 'Rick Astley - Never Gonna Give You Up' video, all five steps exist: the 1280×720 file is 63.8KB and the smallest 120×90 file is 2.8KB. Lower quality means fewer pixels, so even when the photo shows the same scene, the file size shrinks along with it. The 63.8KB image and the 2.8KB image capture the same moment but are files of completely different sizes. Line the five steps up in order and you can see the flow directly: as resolution drops, file size drops with it.

The catch is that these five steps aren't prepared identically for every video. maxresdefault is generated by reflecting the original upload quality. If the uploaded video itself is low quality, YouTube never creates a 1280×720 thumbnail file in the first place. You can't pull a large picture out of material that isn't there, so that size is simply never generated on the server. It also means YouTube doesn't stretch pixels from a small original to fake a large file.

So no matter how precisely you type the maxresdefault.jpg address, you can't get a picture from a video that doesn't have that file. It's not a typo in the address and it's not blocked access — you're requesting a file that was never created. Lower steps like sddefault, hqdefault, mqdefault, and default are sizes that can still be produced from a lower-quality original, so they work on most videos. The lower the step, the higher the odds of "this one is almost always there." Put the other way, the higher you go — meaning the larger the resolution — the more it depends on whether the original video actually carried that much quality.

How the screen reacts to a file that doesn't exist can also vary. You may get an error screen with no connection at all, or it may be replaced by a tiny default image or a broken-image icon. Either way, one thing is common: to the human eye it's just a signal that "something went wrong," and on its own it never tells you kindly which size is missing. That's why it's far more intuitive to check whether each one actually exists first and show people only the result.

This tool uses that trait directly. You enter a video URL and it checks all five file addresses up front, then lists only the files that actually exist. Sizes that don't exist are dropped from the list entirely, so you never hit a broken image or have to try missing filenames by hand one at a time. You give it one video URL and it shows only the qualities that video actually has ready. Instead of clicking all five and hitting failures, you download only what's already confirmed to work. This check is the same in principle as a person clicking five times. The only difference is that it handles the repetition in an instant, filters out the failures, and shows you just the successes. It's less a new technology than automated busywork.

That covers the image side. The five filename steps, the upload quality that decides whether each exists, and the file size that shrinks with quality all follow one principle.

Separately from thumbnails, the video file itself (mp4 and so on) can't be downloaded this way. A thumbnail is a static image file you can view with no authentication, but video streaming is protected by a completely different structure. For requests coming from servers (data centers) that run without a login, YouTube requires a step (PoToken) that verifies whether the request is human or a program. That verification is designed around an ordinary browser environment, so a server-based tool that runs automatically with no login has no way around it. Handing over one static image file and serving a live video stream are, from YouTube's side, requests on completely different levels.

Unpack that difference a little more: a request to download one static image file and the series of requests needed to play a video go through different procedures inside YouTube's system. An image file is a simple request that ends with one address, while video playback is streaming: chunks for each quality level are received in sequence, and at the start there's a step that checks whether a human came in through a browser. A server-based tool that runs automatically, without login and without human involvement, has no means to pass that check, so video is blocked at the source. Supporting images (thumbnails) but not downloading the video file itself is the structural limit that services running on servers without login — this tool included — run into in common.

Shorts works exactly the same way. A Shorts URL differs from a regular video only in the shape of its path. Extract the video ID inside it and request img.youtube.com the same way, and the same five-step rule applies as-is. There's no separate rule for Shorts; once you pull the video ID correctly, everything else is identical to a regular video. Being shot vertically doesn't change the filename system either, and the possibility that maxresdefault is missing applies to Shorts just the same.

To sum up: the five filename steps are a fixed specification set by YouTube, and whether a file for that specification was actually created depends on the original upload quality. Accessing addresses you memorized directly never tells you in advance whether the file "was actually created," so you have to check every time — and automating that check is all this tool does.

One thing is worth clearing up here. The fact that maxresdefault is missing only means the video's original upload quality wasn't enough to produce a 1280×720 thumbnail. It doesn't mean the video is damaged or the channel has a problem. It's just the answer to a narrow question: "Is a still image file at this size available on the server?"

Recalculate the five steps as aspect ratios and something interesting shows up. maxresdefault (1280×720) and mqdefault (320×180) are 16:9 widescreen, but sddefault (640×480), hqdefault (480×360), and default (120×90) come out to a 4:3 ratio. Even for the same video's thumbnail, the aspect ratio itself differs depending on which filename you get. If you don't know about that difference when placing the image on another screen, it can be the reason something looks oddly stretched or squished even though you only resized it.

Comparing by Quality and Use Case

Here's what each of the five filename sizes is good for, and how the video file itself differs from them.

FilenameResolutionWhat it's likeDoes it always exist?
maxresdefault1280×720The highest resolution, matching the quality of the original uploadNo — missing if the upload quality was low
sddefault640×480SD quality, a solid size for a representative imageExists for most videos
hqdefault480×360The default most widely used in search results and previewsExists for virtually every video
mqdefault320×180A small thumbnail suited to list-style layoutsExists for virtually every video
default120×90The smallest size, icon-level previewAlways exists
Original video file (mp4, etc.)Not applicableUnlike the images in this table, it isn't published as a static fileDownloading isn't possible at all (bot verification required)

As the table shows, the lower you go, the less likely a size is to be missing. Below hqdefault, you can safely assume just about everything exists — but if the highest quality is your only goal, you really do need to check availability first. That's also why people who think "just grab the biggest one" and try only maxresdefault for a representative image keep hitting a wall.

Which size fits which job also varies. In a spot that takes up a lot of screen space, like the top of a blog post, you want sddefault or better or it'll look blurry. If you're lining several images up in a list, mqdefault or even default is plenty recognizable. On the other hand, if you need to blow it up to original size for print or a large banner, a video without maxresdefault simply isn't usable for that purpose — you're better off preparing a different representative image.

The original video file in the last row of the table isn't something whose existence you can know in advance the way you can with those five sizes. It isn't published statically like the images are; it's streamed with authentication on every request. It sits in the same table, but keeping in mind that it's a fundamentally different kind of item will save you some confusion.

As covered earlier, maxresdefault and mqdefault are calculated at 16:9, while the other three sizes are 4:3 — so if you want to compare images at exactly the same aspect ratio, keep that distinction in mind. For example, if you want to preserve the original framing as closely as possible, instead of dropping straight to sddefault when maxresdefault is missing, you might try mqdefault first, since it shares the aspect ratio.

Where People Get Stuck

Here are the problems people who work with these URLs directly actually run into, along with their causes.

SymptomCauseFix
You entered the URL correctly, but only a broken image shows upThat size file doesn't exist for the video (low upload quality)Try the next size down, or use our tool to check which sizes exist first
You thought you got the highest quality, but it looks blurrymaxresdefault was missing, so you saved a lower-tier image thinking it was the highest qualityCheck the actual pixel width × height before saving
You assumed this method doesn't work for ShortsThe same method applies to Shorts — the URL format is just different and confusingPasting a Shorts URL works exactly the same way
You want the video file too, but it won't workYouTube requires bot verification (PoToken) for server-side requestsThis method only works for images (thumbnails), not video
People say the same video looks different in quality for each of themThey downloaded different filenames (hqdefault, mqdefault, and so on)Compare using matching filenames
You pasted a URL, but the wrong video shows up, or no quality appears at allExtra data from a playlist link got mixed in, so the video ID was cut incorrectlyUse exactly the 11 characters after v= (or after shorts/)

The first row of the table is the most common case. Most confusion starts with requesting a file that doesn't exist as if it does. The filename isn't wrong — that size just isn't available for that video.

The second most common mistake is confusing a lower-tier image for the highest quality. Browsers scale any size to fit the screen, so an hqdefault image (480×360) stretched to fill a large view can feel high-quality at a glance. Unless you check the pixel dimensions of the file you actually saved, that illusion is hard to catch.

Third is losing track of where you are when processing several videos at once. Since each video has a different maximum available size, changing filenames by hand while scanning down a list makes it easy to lose track of which videos you've checked and which sizes you saved. In that case, a method that lists all the results on screen at once helps cut down on mistakes.

Fourth happens when you open a video from inside a playlist. The URL often has playlist information (like list=) appended to it. If you mistake all that extra data for the video ID, you build the wrong URL and get no image at all. The key is to use exactly the 11 characters right after v= and nothing more.

Fifth is when you check the same video again at a different time and the result looks different. In most of these cases the file itself hasn't changed — you just didn't record which size you tried the first time. Writing down the filename or a note about which size you saved will make it much less confusing the next time you check.

The thumbnails you can pull with this tool are limited to images from videos that are public on YouTube. Thumbnails for private or deleted videos, or for content you can only see after logging in, can't be accessed this way at all. Put the other way around, the fact that anyone can open a video without logging in also means the channel chose to publish that content publicly.

That said, a public video doesn't mean you're free to use its thumbnail however you like. Copyright in the thumbnail image belongs to the channel that made the video — the original creator. Downloading it doesn't transfer ownership; it just makes one copy on your computer. It's the same principle as saving a photo from the internet: the owner of that photo doesn't change.

If it's your own video thumbnail that you uploaded yourself, or you have the original creator's permission, and the use is personal and lawful, you're fine. On the other hand, taking another channel's thumbnail and re-uploading or redistributing it as your blog's representative image or as the thumbnail for a different video can amount to copyright infringement. It's worth keeping in mind that briefly checking something for reference or analysis and copying it to redistribute elsewhere are completely different matters.

If a case feels unclear, one approach is to ask whether what you're trying to do would work without that thumbnail at all. For example, if you're writing a post that introduces or links to a video, you often don't need to save and move the thumbnail file anywhere — a YouTube link or the official embed feature is enough.

Some thumbnails also contain on-screen captions, subtitles, or footage from other copyrighted works. Those images can involve rights in the elements inside them on top of the original video's copyright, so think more carefully before using them for anything beyond simple reference.

Embedding a video on your page and downloading the thumbnail image file to use elsewhere are also different kinds of acts. An embed shows the original through the YouTube player, while a downloaded image becomes a copy that gets moved onto your post or server — the latter is the one that demands more copyright care. In the end, the principle comes down to one thing: you can bring over a public image, but that doesn't mean you're bringing the rights to it along with it.

How is this different from similar methods?

There are already plenty of known ways to get a YouTube thumbnail. Installing a browser extension is one, and memorizing the img.youtube.com URL pattern and typing it yourself is another. The underlying principle is the same either way: you load an address that follows a fixed filename rule.

The difference is whether something filters out the sizes that don't exist before you click. Many sites and extensions just list all five URLs and leave you to click through them one by one to find out whether the file is actually there. Do that often enough and you keep hitting broken images from sizes that were never created. The end results point to the same server and the same files, so this isn't about "secretly holding back better quality." The accurate way to put it is that it's about how conveniently the same information gets confirmed.

Our tool checks whether all five files actually exist the moment you enter a video URL, and only lists the ones that do. Sizes that don't exist never show up, so you spend less time clicking through them one by one. That said, this only applies to images (thumbnails). Downloading the video file itself isn't supported, for the same structural reason it isn't supported by other similar services: this is a server-based tool that runs without a login.

One more difference is the shape of the result. If you only need the thumbnail for one video, pick a single resolution and download it. If you want to compare several resolutions at once, you can grab every size that exists. Compared with installing an extension or opening your browser's developer tools to dig out the URL, pasting an address into a web page with nothing to install is a real, practical difference.

Where that wall sits varies a bit by platform. Some sites advertise that they'll pull the video itself using workaround techniques, but in practice it often fails outright or only yields low quality. If the setup processes things automatically on a server without a login, then images and video alike end up facing the same kind of authentication requirement. Being usable right on the web with no signup or payment is another point of contrast with services that ask you to register every time or push you toward a paid plan.

To sum up: getting a thumbnail image isn't some special secret. It's closer to checking a URL rule that's already public. What this tool adds is the convenience of doing that check for you in advance and showing you only the results. It isn't magic that makes a missing file appear.

The short version

  • YouTube thumbnails come in five fixed filenames: maxresdefault, sddefault, hqdefault, mqdefault, and default. This rule doesn't change from video to video.
  • For videos uploaded at low quality, the 1280×720 maxresdefault file was never created on the server, and no method can conjure up something that isn't there.
  • Lower quality means a smaller file size (1280×720 is the largest, 120×90 the smallest).
  • The video file itself can't be downloaded by a server-based method without a login because of YouTube's bot verification (PoToken). That's not a limitation unique to this tool; it's a structural one.
  • Shorts follow the exact same rules, so pasting a Shorts URL checks it just like a regular video.
YouTube Thumbnail Downloader: Up to 1280×720

Free · no login needed · one video URL shows only the sizes that actually exist

Frequently asked questions

Why do some videos not have a maxresdefault?

Because the video was uploaded at low quality, so YouTube never created the large 1280×720 thumbnail file in the first place. You didn't mistype the URL and access isn't blocked — the file simply doesn't exist on the server. For videos like this, check the lower tiers instead, like sddefault or hqdefault. Lower tiers such as hqdefault tend to get created even when the source quality is modest, so they're much more likely to be there.

Do I have to click through every size to see which ones exist?

If you're checking by hand, you have no choice but to open all five URLs in order. But if you use a tool that takes a video URL and automatically filters down to the sizes that actually exist, you can check everything at once without running into broken images or renaming filenames by hand. If you have a batch of videos to handle, that difference feels a lot bigger.

Can I get Shorts thumbnails the same way?

Yes. Shorts only differ in the URL format. Once you pull out the video ID inside, the same img.youtube.com rules apply. There's no separate method — you check the same five filenames as a regular video. A vertically shot video doesn't get its own filename scheme either.

Can I download the video file itself this way?

No. YouTube requires bot verification (PoToken) for requests coming from servers (data centers) that operate without a login, and there's no way around it. Images (thumbnails) are static files, so they work, but video streaming has an entirely different protection setup. This constraint isn't a problem with any one tool — it's something every server-based service that runs automatically without a login runs into.

Why are the file sizes so different between quality levels?

Because the pixel count itself is different. In practice, the 1280×720 size comes in at 63.8KB while the smallest 120×90 size is 2.8KB. Even when it's the same scene, lower resolution means less information to store, so the file gets smaller too. This relationship holds across all five tiers, and the gap widens as you drop two or three steps.

Do older videos always lack the highest quality?

When a video was uploaded isn't the criterion. The criterion is the original upload quality. A video uploaded at low quality long ago may still have no maxresdefault today, and a recent video uploaded at low quality can also lack one. In other words, it's not when you uploaded it but what quality you uploaded it at — that's the only factor.

Can I use a downloaded thumbnail on my blog or channel?

Be careful here. The copyright to a thumbnail belongs to the channel that made the video, and downloading it doesn't transfer ownership to you. Personal, lawful uses — your own video, or one where the original creator gave permission — are fine, but reuploading or redistributing it without permission can infringe copyright. Keep in mind that briefly looking at something for reference or analysis is a different matter from copying it and redistributing it as-is.

This article was adapted from our Korean original. Read the Korean original

Related articles

  1. ASCII Art Line Breaks in Chat Apps: Monospace Font GuideWhy image ASCII art collapses in chat apps, how monospace fonts keep the grid aligned, and how pixel brightness turns into characters.
  2. AVIF to JPG Conversion: Fix Photos That Won't OpenWhy AVIF files won't open in Office apps or upload forms, why renaming the extension breaks them, and how to convert them to JPG or PNG in your browser.
  3. AVIF vs WebP: Compression Rates and a 3-Step Browser FallbackCompare AVIF and WebP compression, see where browser and email support still breaks, and set up a picture-tag fallback that always loads.
  4. Image to Base64 Data URI: Why Size Grows 33% and How to Use ItSee how Base64 Data URIs work, why the file grows exactly 33.3%, when a 10KB icon is worth inlining, and how to generate img and CSS snippets.
  5. Base64 to Image: Restore a Base64 String into a Real Image FileLearn how Base64 strings from APIs and code turn back into image files, how to read the format from the first letters, and preview or download them.
  6. BMP File Size Explained: Why It's So Big and How to Shrink ItBMP files skip compression, so they run 10x larger than JPG. See the size formula and how to convert BMP to JPG, PNG, or WebP with no quality loss.

Related tools