YouTube Thumbnail Size Guide 2026: Dimensions and Best Practices
YouTube expects a wide 16:9 hero image even when the final player is smaller. If you upload something too small, YouTube upscales it and the result looks soft. If you upload the wrong aspect ratio, you risk letterboxing or awkward crops in search and browse surfaces. Whether you are designing a custom thumbnail to upload or downloading an existing one for reference, knowing the exact dimensions in play helps you avoid quality loss at every step.
What YouTube recommends for custom uploads
- Resolution: 1280 by 720 pixels (16:9). This matches the HD tier most viewers expect across desktop, mobile, and TV surfaces.
- Minimum width: 640 pixels. Below that, quality drops quickly on larger displays and YouTube may reject the upload.
- Formats accepted: JPG, PNG, or GIF under roughly 2 MB for custom thumbnail uploads.
- Safe text zone: keep critical text inside the center 90 percent of the frame so it survives different crops on TV, mobile, and embedded players.
- Aspect ratio: 16:9 is enforced. Uploading a 4:3 or 1:1 image will result in black bars or cropping depending on where the thumbnail appears.
What the 16:9 ratio means in practice
A 16:9 image is 1.78 times wider than it is tall. At 1280×720, the width is almost exactly twice the height. This ratio was chosen because it matches the aspect ratio of modern HD and 4K displays, meaning a full-width thumbnail on a desktop browser fills the screen edge to edge without letterboxing. When YouTube renders your thumbnail in a smaller surface — the sidebar, mobile search, or the home feed — it scales the image down while preserving the ratio, which is why text placed near the edges often gets cut off on smaller viewports. Always design with the center safe zone in mind.
Still images the CDN exposes (download names)
When you fetch stills programmatically, YouTube uses predictable filenames. The table below maps the technical key to typical pixel dimensions and estimated JPEG file sizes. Actual values vary depending on the source upload and compression, but these are the numbers you will encounter most often.
| Key | Typical size | Est. file size | Best for |
|---|---|---|---|
| maxresdefault | 1280 × 720 | 80–200 KB | Presentations, design comps, hero marketing |
| sddefault | 640 × 480 | 30–80 KB | Medium weight files when HQ is too soft |
| hqdefault | 480 × 360 | 20–50 KB | Blog embeds, quick reviews, mobile previews |
| mqdefault | 320 × 180 | 10–25 KB | Lists, related video rail, lightweight UI |
| default | 120 × 90 | 3–8 KB | Tiny icons, debugging, legacy players |
Which size to choose by platform
Different use cases call for different quality tiers. Here is a quick reference for the most common scenarios:
- Blog posts and articles: hqdefault (480×360) loads quickly and is sharp enough for inline images at typical column widths up to around 700 pixels.
- Twitter / X cards and Open Graph previews: start from maxresdefault and re-export as a WebP or compressed JPEG. Social platforms re-compress images, so beginning from the highest resolution preserves detail through that second compression pass.
- PowerPoint or Keynote presentations: maxresdefault is the right choice. Anything smaller will appear pixelated on a projector or large external display.
- App UI mockups and wireframes: mqdefault (320×180) keeps file sizes small in design tools like Figma and prevents slow-loading prototype previews.
- Documentation and README files: hqdefault or mqdefault depending on how large the image will render. Smaller is usually better in developer docs where quick page load matters.
Choosing a size for real projects
For social cards that will be recompressed by a third-party platform, start from maxres or SD and export your own optimised WebP or AVIF. For quick internal references, HQ is often enough and loads faster on slow connections. For documentation screenshots, MQ keeps repository sizes small while staying readable at standard zoom levels. Never upscale a smaller tier hoping to recover detail — JPEG upscaling introduces blurring and compression artefacts that cannot be reversed.
JPEG versus PNG: which format to use
YouTube serves all CDN stills as JPEG, which is fine for photographic content with smooth gradients. If you need to composite the thumbnail onto a transparent background in a design tool, convert to PNG after downloading — just be aware that the conversion will not recover detail the JPEG compression already discarded. For final deliverables, stick with JPEG at 85–90% quality to keep file sizes manageable while preserving visible sharpness.
CTR and clarity
Thumbnail size is only half the story. Contrast, readable text at small widths, and a single strong focal point usually move click-through rate more than an extra hundred pixels of resolution. Studies of high-performing YouTube channels consistently show that thumbnails with a clear subject, bold sans-serif text under 20 characters, and high contrast between foreground and background outperform cluttered designs even at lower resolutions. Still, beginning from a sharp 1280×720 master gives you the room to crop for Shorts, Stories, and landscape placements without introducing artefacts during scaling. Always design at the largest size you need, then export smaller versions.
Put it into practice
Use the downloader to inspect what YouTube generated for any public upload, then mirror those proportions in your own custom artwork. If you want to understand how Shorts thumbnails differ from standard videos — including why maxresdefault is sometimes absent — the Shorts thumbnail guide covers that in detail.