Aspect Ratio Calculator

Quick Tips for Accurate Results

Features

Why Resizing by Hand Goes Wrong

Stretched thumbnails, squashed video previews, and logos that look subtly "off" almost always trace back to the same mistake — changing a width without changing the height by the same proportion, or vice versa. A 1920×1080 image resized to a width of 800px needs a height of exactly 450px to look right; typing in 500px instead doesn't just make it a little different, it visibly distorts every straight line and circle in the image. The math behind avoiding that is simple multiplication, but doing it correctly by hand for every new size, every time, is exactly the kind of small repetitive calculation that's easy to get wrong under time pressure.

That's the entire job this calculator does — take an original width and height, and for any target width, height, or overall scale, work out the other dimension so the proportions stay identical to the source. Nothing here modifies an actual file; it produces the correct numbers to type into whatever tool does the real resizing, whether that's the Image Resizer, a video export panel, or a design tool's own resize field.

Reading a Ratio Like 16:9

The simplified ratio shown here isn't a rounded estimate — it's the exact result of dividing both numbers by their greatest common divisor, the largest number that goes into both evenly. 1920 and 1080 share a GCD of 120; dividing each by 120 gives 16 and 9, which is the entire reason a "1920 by 1080" video frame gets called 16:9 in the first place. The same math applies identically to any pair of numbers, named ratio or not — a photo that comes out as 37:24 isn't broken or unusual, it's just a ratio that doesn't happen to match a widely-used industry standard.

Named-ratio detection exists specifically to flag the cases that do match something recognizable, since knowing a dimension is genuinely 16:9 (rather than merely close to it) matters for things like video export presets, where "close enough" can still trigger unwanted letterboxing or a slightly-off crop during encoding.

Three Ways to Ask the Same Question

Setting a target width, a target height, and a scale percentage are three different entry points into the same underlying calculation, and which one to use depends entirely on what constraint is actually driving the resize. A platform that specifies "banner must be exactly 1200px wide" calls for typing that number directly into New Width and reading off the matching height. A layout with a fixed vertical slot but flexible width works the other way — set New Height and let the width follow. Neither of those situations involves thinking in percentages at all.

Scale percentage earns its place as a third option because plenty of real resizing decisions aren't tied to an exact pixel number in the first place — "make the thumbnail about half size" or "bump this up 20% so it's easier to see" are both percentage decisions dressed up as pixel problems. Typing 50% is faster and less error-prone than working out what half of 1920 actually is by hand, and it keeps the intent of the resize ("smaller," "bigger," "by roughly this much") directly visible in the number itself, rather than buried inside two now-unrelated-looking pixel values.

Where This Actually Gets Used

A video editor exporting the same clip for YouTube (16:9), Instagram Reels (9:16) and a square feed post (1:1) needs three completely different crops of the same footage, and starting from the right target dimensions for each platform avoids discovering a distorted export only after upload. A web developer building a responsive video embed uses the simplified ratio directly in CSS — the modern `aspect-ratio` property takes exactly this kind of value to reserve the correct space for a video or image before it finishes loading, preventing the layout-shifting jump that happens when a page doesn't know an element's proportions in advance.

A designer resizing a hero image for three different breakpoints types in the target width for each and reads off the matching height rather than guessing, and a photographer preparing prints checks whether a shot's native ratio matches a standard print size (like 3:2) or will need a crop first to avoid unwanted white borders or a trimmed edge at the print shop. In every one of these cases, the actual bottleneck isn't technical difficulty — it's making sure the arithmetic is exactly right before spending time on the export, crop or layout itself.

What This Doesn't Do

It calculates proportions — it doesn't touch pixels. No image, video or file is uploaded or modified here, which also means it can't fix a photo that's already the wrong shape for where it needs to go. If a source image is landscape but the destination needs portrait, no amount of proportional math avoids the real choice that has to be made somewhere: crop part of the image away, add padding around it, or accept some distortion. This calculator makes that decision informed rather than automatic — the Image Cropper is the tool for actually making the crop once the target ratio is known.

It also doesn't account for DPI or physical print size on its own — the ratio between 6 inches and 4 inches is mathematically identical to the ratio between 1500 and 1000 pixels, but converting between "inches at a given print quality" and "pixels" needs a separate DPI calculation layered on top of the proportional math handled here.

And it deliberately stays a calculator rather than trying to guess intent — it won't silently decide that a slightly-off ratio "should" be treated as 16:9 and round it for you, since that kind of quiet correction is exactly how a genuinely custom ratio gets misidentified as a mistake. The named-ratio match only appears when the numbers actually support it, leaving every other judgment call — crop, pad, or accept the distortion — where it belongs, with the person doing the resizing.