Aspect-ratio math for thumbnails

An aspect ratio is a shape, not a size. 16:9 says nothing about how many pixels an image has — only that for every 16 units of width there are 9 of height. Most thumbnail sizing questions come down to that one relationship: what height goes with this width, does this file already have the right shape, and why does the calculator sometimes answer with a fraction.

This guide works through the arithmetic the aspect ratio calculator performs, using the calculator's own engine. Every number below is computed at build time by the same tested functions the tool runs in your browser, so the guide cannot disagree with the tool. For the official size rules the ratio sits inside, see the size guide; for what YouTube stores per video, see YouTube thumbnail sizes, explained.

A ratio is a pair, not a decimal

Written as a decimal, 16:9 is 1.7778 — and that is already a rounding. The engine never stores a ratio as a decimal. Each entry in its list is a pair of whole numbers, a width term and a height term, and every calculation multiplies and divides by those integers directly. The decimal appears only when the engine describes an image that already exists, and then it is reported beside the simplified pair rather than instead of it.

Pairs also carry a wrinkle the decimal hides: two different pairs can name the same shape. The table lists each ratio the calculator offers, the note the engine attaches to it, and the pair in lowest terms as the engine's own describeRatio reduces it. Most are already in lowest terms; 21:9 reduces to 7:3, which matters for the rounding rule below.

Height from width, and the honest fraction

The formula is one line: height = width × height term ÷ width term. At 16:9 that is width × 9 ÷ 16. The difficulty is that pixels are whole and the formula does not care. Run a handful of widths through heightForWidth and the answer is sometimes a whole pixel and sometimes not:

The flag is the honest part. The engine returns three things for every calculation — the exact value, the nearest whole pixel, and whether they differ — and the calculator shows all three instead of quietly picking one. When the exact value is already whole, the two columns agree and the flag reads exact. When it is not, no whole-pixel height exists for that width at that ratio: 1000 wide at 16:9 wants 562.5, and the nearest whole pixel is 563. The rounding sends a half upward, which is why 562.5 becomes 563. A width of 1366 wants 768.375 and lands on 768 — a different fraction, the same flag.

There is a rule behind which widths pass. A whole-pixel height exists exactly when the width is a multiple of the ratio's width term in lowest terms. For 16:9 that means multiples of 16: every width in the table that divides evenly — 640, 1280, 1920, 3840 — passes, and every width that does not is flagged. For 21:9 the rule uses the reduced pair 7:3, not the label: 1400 is not a multiple of 21, yet its height at 21:9 is 600, whole and exact, because 1400 is a multiple of 7.

Width from height

The reverse direction is the same formula turned around — width = height × width term ÷ height term — and it rounds for the same reason. At 16:9 a whole width exists when the height is a multiple of 9. widthForHeight on a few common heights:

The calculator uses this direction when you fill the height field and leave the width empty; if both fields are filled, width wins.

One width, every ratio

The calculator answers every ratio from one width at once, which is how a matched set of exports is produced. Taking 1280 as the input — the width of maxresdefault, the largest thumbnail YouTube serves back — the engine gives:

2 of these round — 9:16 and 21:9 — because each fails the divisibility test at 1280, so their rows carry the flag. That is not a fault in the input. It is a statement that no whole-pixel height exists for that width at that ratio, and the calculator says so rather than silently rounding.

Reading an image that already exists

The other half of the engine, describeRatio, works backwards from a width and height to a shape. It reduces the pair by their greatest common divisor, reports the decimal, and answers one exact question: is this 16:9? That check cross-multiplies whole numbers — width × 9 against height × 16 — rather than comparing decimals, so it never suffers a floating-point near-miss. It also means a fractional pair can still be exactly 16:9: 1000 by 562.5 has no simplified integer form (the engine reports none), yet it passes the 16:9 test, because 1000 × 9 equals 562.5 × 16.

Here are common upload and screen sizes described by the same function. The last column comes from the tester's coverCropReport, which states what a 16:9 "cover" slot does to an image of that shape: a wider image loses width, a taller one loses height, and the percentage is rounded to one decimal.

The screen-shaped sizes are the instructive ones. 1536×864 reduces to 16:9 and passes. 1366×768 reduces to 683:384, a decimal of 1.7786, and fails — close to 16:9, but not 16:9, and the engine does not grade on closeness. The crop report is honest on both counts at once: it says the fit is not exact, and it says the loss rounds to 0% of the width. A square 1080×1080 loses 43.8% of its height in the same slot. The thumbnail tester runs this report on any image you load.

The stored sizes are not all 16:9

Running describeRatio over the 5 sizes YouTube stores per video gives a result worth knowing before you compare a download against your export:

3 of the 5 frames are 4:3; the rest are 16:9. This guide makes no claim about how a 16:9 picture sits inside a 4:3 frame — only that the frame has that shape, which follows from the pixel dimensions alone. Which sizes exist for a given upload, and why the two largest are sometimes missing, is covered in YouTube thumbnail sizes, explained and on the downloader.

Why 16:9, and where the number comes from

Nothing in the arithmetic above makes 16:9 special; the engine treats every pair the same way. The reason it is the thumbnail ratio is external to the math. Google's help article "Add video thumbnails", re-checked on July 25, 2026, recommends 16:9 as the most used in YouTube players and previews, with 1:1 for podcasts. The same article sets a minimum width of 640 pixels and gives resolution guidance of 3840×2160.

Put through the engine, those official figures line up with the standard sizes exactly: 640 wide at 16:9 is 360 tall with no rounding, and 3840 wide is 2160 tall with no rounding, so the pair 3840×2160 reduces to 16:9. The size guide's two footnotes apply here as well: 1280×720 under 2 MB is the safe intersection of every upload path, not a ceiling, and maxresdefault at that size is the largest size YouTube serves back. Every official figure on this site is cited to that article with the date it was last verified; the ratio math is ours, and it is tested.

Limits, and what the calculator refuses

The engine accepts dimensions up to 100,000 pixels per side. Past that it returns an error instead of a number. Ask for a height one pixel beyond the limit and the message is "The width is limited to 100,000 pixels." A zero or negative dimension gets "The width must be greater than 0." Anything that is not a finite number gets "Enter a valid height in pixels." Every function returns either a value or a coded error — it never throws and never emits a not-a-number — which is why the calculator can always show a specific message rather than a blank field. The limit is a sanity bound for a pixel calculator, not a platform rule.

Common misreadings

• A decimal is not a ratio. 1.7778 is a rounded shadow of 16:9. The engine tests pairs by cross-multiplication, so an image is either exactly 16:9 or it is not.
• Rounded does not mean wrong. The flag says no whole-pixel answer exists for that input. If you need an exact pair, choose a width that is a multiple of 16.
• Same ratio, different size. Several rows of the upload table reduce to the same 16:9. A ratio says nothing about pixel count or file size; the size guide covers those figures with their citations.
• Close is not equal. 1366×768 is 683:384. The cover-crop loss rounds to 0%, and the 16:9 verdict is still no.
• Frame shape is not picture shape. 3 stored sizes have 4:3 frames. The guide states the frame ratio and nothing more.
• The limit belongs to the calculator. 100,000 pixels is where the engine stops accepting input; it is not a YouTube figure.

Frequently asked questions

Every figure on this page is computed at build time by the engine that runs locally in your browser on the aspect ratio calculator, and nothing you type there is transmitted. See the methodology page for how the engines are tested.