Guides

The tools on ThumbnailPro act: paste a link and get every stored thumbnail size, load an image and see it at display size, type a width and get a height. A tool page explains its controls; it has no room for the mechanism behind a result — why a size comes back "not available for this video", why a web page can download an image from another domain at all, why a preview size is called typical rather than exact, and how a background can be removed without the photo leaving your device. These guides are that explanation, one mechanism per page.

They follow the rule of the methodology page: every figure is either computed at build time by the engine that powers the tool, or attributed to the document it came from. The figures here are all the first kind — 5 stored sizes, a 120×90 placeholder, a height of 562.5 that has to be rounded — each produced by the engine while the site was built, apart from the HTTP status code in the maxresdefault section, which is YouTube's behavior as documented on the methodology page. The official upload rules are the second kind: they are cited to Google's help documentation on the size guide, with the date they were last verified, and the guides restate them only that way.

YouTube thumbnail sizes, explained

YouTube stores up to 5 images per video under one predictable path, from default at 120×90 to maxresdefault at 1280×720. 3 of them exist for effectively every public video; sddefault and maxresdefault are generated only for some uploads. This guide walks the full table — key, label, pixels, guaranteed or not — and keeps it apart from the upload rules, which have a different source. It also separates the largest size served back from the largest size you may upload.

Why maxresdefault is missing for some videos

When a size was never generated, YouTube's image server answers with HTTP 404 — but the body of that response is a gray 120×90 image, and a plain <img> tag renders it as if it were the thumbnail, which is how a careless tool ends up offering it as a download. The downloader checks two signals, HTTP status and decoded pixel width, and this guide traces both through the classifier: a failed status is classified missing; a successful status that decodes to 120 px when maxresdefault should be 1280 px wide is also missing; a full-width decode is available. It also explains where the check stops — a verdict says what the image server served when asked, never why — and what the undecodable verdict means: a success status arrived, but the bytes did not decode, which the classifier keeps distinct from a size that was never generated.

Safe areas, explained

Player surfaces draw interface chrome over thumbnails: a duration badge bottom-right, hover controls top-right, a watched-progress bar along the bottom edge. YouTube publishes no specification for any of it, so the safe-area checker's zones model the convention at typical proportions and say so on their labels. This guide shows how a proportion becomes a rectangle: for a 1280×720 image the duration-badge zone is 282×101 px at (998, 619) from the top-left corner, and the progress-bar zone spans the full width at 36 px tall — typical zones, not a spec. It then explains what "keep important content out of here" does and does not mean.

Aspect-ratio math for thumbnails

Height equals width times ratio-height divided by ratio-width, and the honest answer is sometimes fractional. At 16:9, a width of 1000 wants 562.5 px; pixels are whole, so the calculator reports 563 and flags the rounding. This guide covers the forward and reverse calculations, the 6 ratios the calculator offers, and how the ratio of an existing image is simplified — which is why a 1000×563 image describes as 1000:563 rather than 16:9, and why the tester's crop report treats it as a non-fit that loses 0.1% of its height.

How the one-click download works

A web page can only read image bytes from another domain when that domain's server explicitly allows it, through CORS. YouTube's image server sends Access-Control-Allow-Origin: * on thumbnail responses — verified empirically — which lets your browser fetch the image, confirm it is not a placeholder, and offer a real download. This guide follows one link through the pipeline: the share link https://youtu.be/jNQXAC9IVRw?si=share-tracking parses to the ID jNQXAC9IVRw, and the ID derives https://img.youtube.com/vi/jNQXAC9IVRw/maxresdefault.jpg for the largest size. It lays out the parser's accept and reject matrix with each rejection's reason — for a playlist link the engine says "That is a playlist link, not a single video. Open a video in the playlist and paste its URL." — and explains the honest fallback when an extension or proxy strips the header: "Open image" links to the original YouTube URLs.

On-device background removal, verifiably local

The background remover runs its segmentation models in your browser: Google's open-source MediaPipe models for the fast and click-the-subject tiers, and a BiRefNet_lite export for the best-quality tier, each executed by a self-hosted runtime under /vendor/ with a provenance note alongside. This guide makes "on device" concrete — the only network requests are your browser fetching model and runtime files from this site, visible in the DevTools network panel — and explains why the best-quality tier runs at a fixed input size (a measured memory constraint), why the WebGPU path is deliberately unused on the pinned runtime, and what the input rules are: image/png, image/jpeg, image/webp, up to 20 MB, with empty files reported distinctly.

How to read the thumbnail tester

The tester draws your image at 4 true display sizes, from a 320×180 home grid card (desktop) down to a 160×90 mobile list row, labeled as honest current typicals because platforms shift them a few pixels with every redesign. This guide explains what each slot represents, what the legibility strip at 120, 168, 246 px is for, and how the crop report works: an exact 16:9 image fits every slot untouched, while a 1080×1080 square loses 43.8% of its height in a 16:9 cover crop. It is equally clear about what the tester does not tell you: it reports geometry, not how anyone will respond.

Where to go next

The guides explain; the tools act: the downloader, the tester, the size guide and safe-area checker, the aspect ratio calculator, the maker and the background remover. The methodology page is the canonical account of how everything works and is tested; the about page explains who publishes the site and why the tools are narrow.

Every figure on this page was computed at build time by the engines behind the tools, and the tools themselves run locally in your browser — nothing you paste or load is transmitted to this site; the downloader's only network requests are your own browser fetching images from YouTube. See the methodology page for how the engines are tested.