A YouTube thumbnail should be 1280 × 720 pixels, 16:9 aspect ratio, under 2MB. YouTube's stated minimum is 640 pixels wide, but 1280 × 720 is the size worth using because it stays sharp on TV apps and large monitors while still compressing comfortably under the file limit.
| Specification | Requirement |
|---|---|
| Recommended dimensions | 1280 × 720 px |
| Minimum width | 640 px |
| Aspect ratio | 16:9 |
| Maximum file size | 2MB |
| Accepted formats | JPG, PNG, GIF, BMP |
| Requirement to upload | Verified channel |
Specifications current as of August 2026 — confirm against YouTube's official thumbnail documentation.
You are designing for 168 pixels, not 1280
This is the part that decides whether a thumbnail works, and almost nobody accounts for it while designing.
You build your thumbnail on a desktop, at full size, on a large monitor. The text looks crisp. The composition is balanced. Then it ships, and most viewers see it at roughly 350–400 pixels wide in a mobile home feed, or as narrow as 168 pixels in mobile search results. Your carefully kerned six-word headline becomes an unreadable grey smear.
The practical rule: design at 1280 × 720, then zoom your preview down to about 15% and look again. If you can't tell what the video is about at that size, neither can the person scrolling their feed at speed.
What survives at 168 pixels wide:
- Three or four words maximum, set very large. Not a sentence.
- One clear focal point — a face, an object, a single strong shape. Multiple competing elements turn to mush.
- High contrast between subject and background. Subtle tonal relationships that look sophisticated on a monitor disappear entirely at thumbnail scale.
Why your thumbnail keeps getting rejected
The 2MB ceiling is the usual culprit. A 1280 × 720 PNG with a photographic background and text overlay frequently lands between 2MB and 4MB, because PNG stores every pixel losslessly and photographic data doesn't compress well that way.
Two ways out. Export as JPG, which handles the photographic portion far more efficiently and will typically produce a 300–600KB file at the same visual quality. Or keep PNG if the text sharpness genuinely matters and compress it under the 2MB limit instead.
The other rejection causes are simpler: an image narrower than 640 pixels, an unsupported file type, or a channel that hasn't been verified. Custom thumbnails require account verification — without it, you're limited to the auto-generated frames YouTube picks from your video.
JPG or PNG for a thumbnail?
It depends on how much text you're overlaying.
JPEG compression works in 8×8 pixel blocks and approximates colour across each block. Smooth photographic gradients compress cleanly. Sharp high-contrast edges — exactly what large bold text is — do not, which is why JPEG text picks up a faint halo. At full size you won't notice. Scaled down to 168 pixels, that softening compounds with the downscaling and can push borderline-readable text into unreadable.
For a thumbnail that is mostly photograph with a small text element, JPG is the better trade: much smaller file, no meaningful quality difference. For a thumbnail dominated by large text or flat graphic shapes, PNG holds the edges cleanly and is worth the file size. More on this in our format comparison guide.
YouTube re-encodes your thumbnail anyway
YouTube generates its own set of resized versions for every placement: the mobile search result, the home feed card, the desktop sidebar, the full-size version on TV apps. Whatever you upload is re-encoded for each one.
So uploading a file that scrapes the 2MB ceiling buys nothing over a clean 600KB file. Both get re-encoded to the same set of outputs. The smaller file uploads faster and is far less likely to fail the size check when you're publishing on a deadline.