How to Compress a YouTube Thumbnail to Under 2 MB

Short answer: export a 16:9 thumbnail as a high-quality JPG, check its actual file size, then reduce quality or dimensions in small steps until it is safely below 2 MB. For a standard video, keep the crop at 16:9. YouTube recommends up to 3840 × 2160 pixels, with a 640-pixel minimum width, and accepts JPG or PNG. Its current mobile limit for video thumbnails is 2 MB; desktop uploads allow up to 50 MB for video, Shorts, and podcast thumbnails. YouTube Help

Know which limit applies

Upload path	Video thumbnail limit	Practical target
YouTube Studio mobile	2 MB	1.8–1.9 MB, leaving a safety margin
YouTube Studio desktop	50 MB	Still optimize for faster uploads and sharing
Shorts	50 MB on desktop; mobile rules can differ by upload flow	Follow the limit shown in your app
Podcast thumbnail	50 MB desktop; YouTube lists a separate 10 MB mobile podcast limit	Check the destination before exporting

The title’s “under 2 MB” target is specifically the mobile video-thumbnail constraint. A file that is 2.00 MB by a rounded display can still be rejected if its exact byte count is over the limit, so aim below it.

Recommended dimensions and format

Aspect ratio: 16:9 for standard videos.
Maximum recommendation: 3840 × 2160 pixels.
Minimum width: 640 pixels.
Practical working canvas: 1280 × 720 pixels, a size documented by Buffer’s YouTube resizer.
Formats: JPG and PNG are named in YouTube’s guidance. WebP can be useful in a compressor that supports it, but it is not listed as YouTube’s official requirement in the cited guidance.

Start with the largest useful source, preserve the intended crop, and resize only when the encoded file remains too large. At 1280 × 720, text and faces are usually still clear in the video preview while the encoder has far fewer pixels to store than a 3840 × 2160 source.

Step-by-step: compress a thumbnail in an image editor

Open the original. Keep an untouched copy so you can return to it if the export becomes too soft.
Crop to 16:9. Use a 16:9 crop for a standard video. Do not stretch the image to force the ratio.
Resize the working canvas. Try 1280 × 720 first. If your design contains very fine text, try 1920 × 1080; if the file is still too large, step down.
Choose JPG for photos and gradients. Export at a high quality setting first. JPG is lossy, so inspect faces, diagonal lines, and small lettering.
Keep PNG for transparency or flat edges. PNG is lossless and can preserve crisp text and transparent backgrounds, but photographic or gradient-heavy thumbnails may produce a much larger file.
Check the exact byte size. Use your operating system’s file information or the YouTube upload dialog. Do not infer file size from pixel dimensions.
Lower quality gradually. If the file is over 2 MB, reduce JPG quality in small steps, export again, and inspect the result at 100% zoom.
Use a safety margin. A target around 1.8–1.9 MB avoids failures caused by rounding or a slightly different upload path.
Upload and verify. In YouTube Studio, confirm that the thumbnail appears correctly. YouTube notes that changes can take time to appear.

How to choose JPG quality

Symptom	Adjustment
File is far above 2 MB	Resize to 1280 × 720, then export JPG at high quality.
File is slightly above 2 MB	Keep dimensions and lower JPG quality by a small amount.
Faces look blocky	Raise quality, reduce dimensions less aggressively, or simplify noisy backgrounds.
Text has halos or ringing	Raise quality, use a sharper resize filter, or export PNG if the design is mostly flat color.
PNG is too large	Convert a non-transparent photographic design to JPG and compare at 100%.

Browser-only compression

A browser compressor is convenient when you do not have an editor installed. The workflow documented by video.yt is:

Upload the PNG, JPG, or WebP file.
Select the output format and quality.
Compare the original and compressed previews.
Download the result.

Use the downloaded file’s actual size as the decision point. Browser-local processing can also avoid sending the source to a remote server, depending on the tool’s implementation; check the tool’s own privacy description before uploading sensitive artwork.

Command-line workflows

ImageMagick

magick original.png -resize 1280x720^ -gravity center -extent 1280x720 -strip -quality 86 thumbnail.jpg
ls -lh thumbnail.jpg

The -strip option removes metadata that is not needed for YouTube. If the output is still above 2 MB, try -quality 80, then -quality 75. If the source is already 16:9, omit the crop and extent options:

magick original.jpg -resize 1280x720 -strip -quality 86 thumbnail.jpg

Python with Pillow

from pathlib import Path
from PIL import Image

source = Path("original.png")
output = Path("thumbnail.jpg")

with Image.open(source) as image:
    image = image.convert("RGB")
    image.thumbnail((1280, 720), Image.Resampling.LANCZOS)
    image.save(output, format="JPEG", quality=86, optimize=True, progressive=True)

size_mb = output.stat().st_size / (1024 * 1024)
print(f"{output}: {size_mb:.2f} MB")

For a strict 16:9 crop, crop before calling thumbnail. For PNG output, use image.save("thumbnail.png", optimize=True), then check whether the resulting file clears the target.

Node.js with Sharp

import sharp from "sharp";
import { stat } from "node:fs/promises";

await sharp("original.png")
  .resize(1280, 720, { fit: "cover" })
  .jpeg({ quality: 86, progressive: true, mozjpeg: true })
  .toFile("thumbnail.jpg");

const bytes = (await stat("thumbnail.jpg")).size;
console.log(`${(bytes / (1024 * 1024)).toFixed(2)} MB`);

Preserve quality while reducing bytes

Remove unnecessary metadata. Camera and editing metadata adds bytes without improving the thumbnail.
Reduce background noise. Grain, confetti, foliage, and detailed textures compress poorly.
Keep important text large. Compression cannot rescue lettering that is already tiny at thumbnail size.
Inspect at 100% and at preview size. A file can look acceptable zoomed in but lose legibility in YouTube’s small preview.
Do not repeatedly recompress JPG. Return to the original and export again; repeated lossy saves compound artifacts.
Use PNG selectively. Flat-color designs, transparency, and sharp line art may benefit from PNG, while photos usually favor JPG.

Troubleshooting

Error or symptom	Likely cause	Fix
“File is too large” on mobile	The exact file exceeds 2 MB.	Export below 1.9 MB; reduce JPG quality or resize to 1280 × 720.
Thumbnail looks stretched	The image was resized without preserving its aspect ratio.	Crop to 16:9, then resize proportionally.
PNG export is unexpectedly huge	Photos and gradients contain many colors that PNG stores inefficiently.	Use JPG unless transparency or lossless edges are essential.
Text looks fuzzy	Quality was reduced too far, or the source was resized repeatedly.	Start from the original, raise quality, and keep a larger canvas.
File appears under 2 MB but is rejected	The file manager rounded the displayed size, or the upload path has a stricter threshold.	Check exact bytes and export with a margin, such as 1.8 MB.
Thumbnail change is not visible immediately	YouTube says changes may take time to appear.	Wait, refresh Studio, and verify on the video page after processing.
Colors shift after JPG export	Color profiles or aggressive compression changed the appearance.	Convert to standard RGB before export and compare the downloaded file.

Performance, reliability, and cost notes

Resizing before compression usually saves more bytes than repeatedly lowering quality on a very large canvas. A 1280 × 720 export is also faster to upload than a multi-megapixel original. Keep the original layered project for future edits, and keep the final compressed file as a separate upload asset.

For one-off thumbnails, an editor or browser compressor is enough. For automated screenshot or image pipelines, measure the output byte size in code and reject or retry files above your chosen threshold. Compression itself has no YouTube fee; the relevant cost is the software or service you choose and the time spent reviewing quality.

Or skip the browser setup

If your thumbnail starts as a webpage or design preview, ScreenshotNeo can capture the page first; you can then run the same resize and compression step above. It is a website screenshot API, so it does not replace the final image compressor.

One GET request returns a PNG, JPEG, WebP, or PDF. See the ScreenshotNeo API documentation for all options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' }); const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and each response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server lets Claude, Cursor, and other MCP clients take screenshots. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.

FAQ

Can I upload a 2 MB file exactly?

Do not target the exact boundary. Export below it, preferably around 1.8–1.9 MB, because displayed sizes may be rounded.

Is 1280 × 720 required?

No. It is a practical working canvas. YouTube recommends up to 3840 × 2160 and requires at least 640 pixels of width for video thumbnails.

Should every thumbnail be JPG?

No. JPG is usually smaller for photographs and gradients. PNG can be better for transparency and crisp flat-color artwork; compare the actual byte size.

Does WebP satisfy YouTube’s official format guidance?

The cited YouTube guidance names JPG and PNG. WebP may be accepted by a third-party compressor, but treat it as an optional intermediate and verify the upload flow you use.

Why does my desktop upload work when mobile fails?

YouTube lists a 2 MB mobile video-thumbnail limit and a 50 MB desktop limit. The same file can therefore pass on desktop while failing in the mobile app.