Audited ·Last updated 28 Jul 2026·5 citations·Tier 2·0 uses

Pixel Aspect Ratio Calculator (Non-Square Pixels)

Convert between pixel, storage and display aspect ratio for anamorphic video, and get the square-pixel resolution to rescale a non-square frame to.

Pixel Aspect Ratio Calculator

What do you know?
The coded width in samples, as the file reports it — 720, 704, 1440, 1920. For 720-wide standard definition, use 704 with the H.264 ratios: only 704 of the 720 samples are meant to be visible.
px
The coded height in samples — 480 for 525-line systems, 576 for 625-line, 1080 for HD.
px
The first number of the pixel ratio: 1 for square pixels, 10 for 10:11 (525-line 4:3), 12 for 12:11 (625-line 4:3), 40 for 40:33, 16 for 16:11, 4 for 4:3 (HDV 1440x1080).
The second number: 1 for square, 11 for the 10:11, 12:11 and 16:11 ratios, 33 for 40:33, 3 for the 4:3 HDV pixel.
Only used in the second mode. 4 for 4:3, 16 for 16:9, 2.35 for a cinemascope master.
Only used in the second mode. 3 for 4:3, 9 for 16:9, 1 for a 2.35:1 shape.
Display aspect ratio
4:3
The shape the frame actually displays at, in lowest terms. This is the answer in the first mode — and it is usually not the shape the pixel dimensions suggest.
Pixel aspect ratio
10:11
Square-pixel width
640 px
Square-pixel height
528 px
Display aspect ratio as a decimal
1.3333
Pixel aspect ratio as a decimal
0.9091
Storage aspect ratio
1.4667
Storage aspect ratio, reduced
22:15
What this means
Each pixel is 10:11, i.e. taller than it is wide, so the 704 x 480 frame is stored wider than it should look and has to be narrowed on display. The stored shape is 1.4667 but the frame displays as 4:3. To work in square pixels, rescale to 640 x 480 (stretching the width) or 704 x 528 (stretching the height). Ignoring the pixel aspect ratio is what makes old standard-definition footage look stretched or squashed when it is imported into a square-pixel editor.

Background.

Most aspect-ratio arithmetic quietly assumes that pixels are square — that a 1920 × 1080 frame is 16:9 because 1920 ÷ 1080 = 1.7778. For every modern format that assumption is correct and guaranteed: Recommendation ITU-R BT.709 specifies a pixel aspect ratio of 1:1 for HD, and BT.2020 carries the same square pixels into 4K and 8K. If your pixels are square, the aspect ratio calculator is the tool you want, and this page has nothing to add.

This page is for the cases where they are not. Standard-definition video, DV and DVD masters, HDV, and anything described as anamorphic store frames whose pixels are taller than they are wide, or wider than they are tall, and the frame only takes its intended shape when the display stretches them back. Get that wrong and faces look thin or fat — the single most common symptom of importing old footage into an editor that assumes square pixels.

Three ratios are involved, and one identity connects them. The storage aspect ratio is the stored pixel dimensions, width over height. The pixel aspect ratio is the shape of one pixel. The display aspect ratio is what you actually see, and it is the product of the other two: DAR = SAR × PAR. Give the calculator any two and it returns the third, plus the square-pixel resolution to rescale to.

The standard pixel ratios are not folklore; they are a numbered table in ITU-T Recommendation H.264. `aspect_ratio_idc` 1 is 1:1 square, 2 is 12:11, 3 is 10:11, 4 is 16:11, 5 is 40:33, and the list continues through 24:11, 20:11, 32:11, 80:33, 18:11, 15:11, 64:33, 160:99, 4:3, 3:2 and 2:1, with 255 reserved for an explicitly signalled pair. The specification also requires that the two numbers be relatively prime, which is why this calculator reduces its labels with a greatest-common-divisor rather than rounding to a decimal.

There is one trap that defeats most published pixel-ratio arithmetic, and it is worth stating plainly. Applying the standard 10:11 ratio to a full 720 × 480 frame gives (3/2) × (10/11) = 15/11 = 1.3636, which is not 4:3. That is not a mistake in the ratio: Table E-1's own note explains that the 4:3 shape belongs to the 704 samples that are actually visible, and the extra 8 samples at each edge are horizontal overscan. Do the same arithmetic on 704 × 480 and it lands on exactly 4:3 — and the square-pixel form comes out at exactly 640 × 480. Whenever a pixel-ratio calculation refuses to close on a round number, the 720-versus-704 distinction is the first thing to check.

A second, subtler point: two different conventions are in circulation and both are correct. ITU-T H.264 gives the 704-based ratios (10:11 and 12:11). Recommendation ITU-R BT.500 Table 1-1 lists the same formats measured across the full 720 samples and gives 0.89 for 720 × 483 and 1.07 for 720 × 576. They differ by exactly the overscan, and neither is wrong — they answer slightly different questions about the same signal. This page lets you enter whichever pair your file or your workflow uses, and shows the consequences of the choice rather than picking one for you.

The second mode runs the identity backwards. If you know a frame is 704 × 576 and is meant to be seen as 16:9, the pixel ratio it needs is (16 × 576) ÷ (9 × 704) = 9216 ÷ 6336, which reduces to 16:11 — H.264's `aspect_ratio_idc` 4, recovered from the geometry alone. That is the mode to use when a file has lost its metadata and you have to reconstruct what it should be.

What is pixel aspect ratio calculator?

Pixel aspect ratio (PAR), called sample aspect ratio in the video-coding standards, is the shape of an individual pixel: its width divided by its height. A PAR of 1:1 means square pixels, which every modern display format specifies. A PAR of 10:11 means each pixel is slightly taller than it is wide, so the stored frame has to be stretched horizontally to display correctly.

It matters because it breaks the usual assumption that a frame's shape can be read off its pixel dimensions. The stored dimensions give the storage aspect ratio (SAR); the shape you see is the display aspect ratio (DAR); and DAR = SAR × PAR. ITU-T Recommendation H.264 enumerates the standard values in Table E-1 — 1:1, 12:11, 10:11, 16:11, 40:33 and a dozen more — and requires that the two numbers be relatively prime. Correcting a non-square frame means rescaling it so that the pixels become square while the display shape is preserved, which can be done by widening the width or by shortening the height.

How to use this calculator.

  1. Enter the stored frame dimensions exactly as the file reports them — the coded width and height in samples, not the shape you expect to see.
  2. In the first mode, enter the pixel aspect ratio as two numbers: 10 and 11 for 525-line 4:3, 12 and 11 for 625-line 4:3, 40 and 33 for 525-line 16:9, 16 and 11 for 625-line 16:9, 1 and 1 for square.
  3. Read the display aspect ratio: this is the shape the frame is meant to be seen at, and the number to set in your editor's sequence settings.
  4. Use the square-pixel width to rescale for a square-pixel workflow — the stored height stays as it is. The square-pixel height output is the equivalent correction applied the other way.
  5. If the answer does not land on a familiar ratio, check whether you should be using 704 rather than 720 for the width; the extra 16 samples are horizontal overscan and are not part of the 4:3 or 16:9 picture.
  6. Switch to the second mode when you know how footage is supposed to look but not what pixel ratio it carries — enter the intended display ratio and the calculator returns the pixel ratio in lowest terms.

The formula.

DAR = SAR × PAR; SAR = Ws ÷ Hs; PAR = DAR ÷ SAR; Wsq = Ws·PAR; Hsq = Hs ÷ PAR

Think of the frame as a grid of Ws by Hs cells, each cell a rectangle PAR times as wide as it is tall. The grid's own shape is SAR = Ws ÷ Hs. Multiplying every cell's width by PAR multiplies the whole picture's width by PAR too, so the shape you see is DAR = SAR × PAR. That is the entire theory; everything else is rearrangement.

Solving for the pixel shape gives PAR = DAR ÷ SAR, which written out on the raw inputs is (darWidth × Hs) ÷ (darHeight × Ws). Because those four numbers are normally integers, the result is an exact fraction, and reducing it by the greatest common divisor produces a ratio in lowest terms — which is exactly what ITU-T H.264 requires when it says that sar_width and sar_height 'shall be relatively prime'. That is why this calculator can print 16:11 rather than 1.4545:1.

Correcting to square pixels can be done in two directions and both are used in practice. Stretching the width gives Ws × PAR by Hs; shortening the height gives Ws by Hs ÷ PAR. Both produce the same display shape, and the choice is about resampling: widening interpolates new columns, shortening discards rows. Pixel counts must be whole numbers, so both are rounded here.

Working the default through: a 704 × 480 frame has SAR = 704 ÷ 480 = 1.4667, which reduces to 22:15 — not a shape anyone would recognise. Its pixels are 10:11, or 0.9091, slightly taller than wide. The display shape is therefore (22/15) × (10/11) = 220/165 = 4/3, exactly 4:3. Correcting by width gives 704 × 10/11 = 640 exactly, so 640 × 480; correcting by height gives 480 × 11/10 = 528, so 704 × 528. Both are exactly 4:3, and both are whole numbers, which is not a coincidence — the standard ratios were chosen so the arithmetic closes on the resolutions people actually use.

The same procedure reproduces every 'without horizontal overscan' example in H.264's Table E-1: 352 × 288 at 12:11, 352 × 240 at 10:11, 528 × 576 at 16:11 and 528 × 480 at 40:33 all land on exactly 4:3, while 352 × 576 at 32:11, 352 × 480 at 80:33, 528 × 576 at 64:33, 528 × 480 at 160:99, 1440 × 1080 at 4:3, 1280 × 1080 at 3:2 and 960 × 1080 at 2:1 all land on exactly 16:9. Thirteen independent checks on one multiplication.

A worked example.

Example

A standard-definition 525-line master arrives as a 704 × 480 file whose metadata reports a sample aspect ratio of 10:11 — that is ITU-T H.264's aspect_ratio_idc 3, applied to the 704 samples of a 720 × 480 frame that are actually meant to be visible. Start with the grid: 704 ÷ 480 = 1.4667, which reduces by gcd(704, 480) = 32 to 22:15. Nothing about 22:15 suggests a television picture, and that is the point — it is the shape of the pixel grid, not of the image. The pixels themselves are 10 ÷ 11 = 0.9091 wide for every unit of height, slightly taller than they are wide. Multiplying gives the display shape: (22/15) × (10/11) = 220/165, which reduces to exactly 4:3, or 1.3333. To take this into a square-pixel editor, rescale the width by the pixel ratio: 704 × 10/11 = 640, giving 640 × 480 — a whole number, and exactly 4:3. Correcting the other way instead, 480 ÷ (10/11) = 480 × 11/10 = 528, giving 704 × 528, which is also exactly 4:3. Try the same arithmetic on the full 720 × 480 frame and it gives (3/2) × (10/11) = 15/11 = 1.3636, which is not 4:3 — the 16 extra samples are horizontal overscan, exactly as the note under Table E-1 explains, and leaving them in is the usual reason this calculation appears not to work.

modedisplay-from-par
dar Width4
par Width10
stored Height480
stored Width704
dar Height3
par Height11

Frequently asked questions.

What is a pixel aspect ratio?
It is the shape of a single pixel — its width divided by its height. Square pixels have a ratio of 1:1, and every modern format specifies them: Recommendation ITU-R BT.709 gives 1:1 for HD and BT.2020 gives 1:1 for 4K and 8K. Standard-definition and anamorphic formats do not. There, pixels are stored slightly taller or wider than square, and the display has to stretch them back, which is why the shape of the frame cannot be read off its pixel dimensions alone.
What is the difference between PAR, SAR and DAR?
The storage aspect ratio (SAR) is the stored pixel dimensions, width over height — the shape of the grid. The pixel aspect ratio (PAR, called sample aspect ratio in the coding standards) is the shape of one cell in that grid. The display aspect ratio (DAR) is what you see, and it is the product: DAR = SAR × PAR. A 704 × 480 frame has a storage ratio of 22:15, a pixel ratio of 10:11, and a display ratio of exactly 4:3. Confusingly, some tools use 'SAR' for the sample aspect ratio rather than the storage one, so check which quantity a piece of software means.
Why does 720x480 with a 10:11 pixel ratio not come out at 4:3?
Because only 704 of those 720 samples are part of the picture. ITU-T H.264's Table E-1 lists 10:11 for a '720x480 4:3 frame with horizontal overscan', and its note spells out what that means: the entry refers to 'having an area of 704x576 luma samples (which has an aspect ratio of 4:3) of the cropped decoded frame (720x576 luma samples) that is visible in the display area' — the same logic applies to the 480-line case. Run the arithmetic on 704 × 480 and it gives exactly 4:3. Run it on 720 × 480 and it gives 15:11, which is the shape including the overscan you are not meant to see.
What are the standard pixel aspect ratios?
ITU-T Recommendation H.264 numbers them in Table E-1. The ones you will meet in practice are 1:1 (square, all HD and UHD), 10:11 (525-line 4:3), 12:11 (625-line 4:3), 40:33 (525-line 16:9), 16:11 (625-line 16:9) and 4:3 (HDV, where a 1440 × 1080 frame displays as 16:9). The full list also includes 24:11, 20:11, 32:11, 80:33, 18:11, 15:11, 64:33, 160:99, 3:2 and 2:1, with an escape code for signalling any other pair explicitly.
Why do I see 0.9 and 1.09 quoted instead of 10:11 and 12:11?
Because two conventions are in circulation and both are legitimate. The H.264 values are measured on the 704 visible samples: 10 ÷ 11 = 0.909 and 12 ÷ 11 = 1.091. Recommendation ITU-R BT.500's Table 1-1 measures the same formats across all 720 samples and lists 0.89 for 720 × 483 and 1.07 for 720 × 576. The difference is exactly the overscan at each edge. Neither is wrong; they answer slightly different questions about the same signal. Use whichever matches the way your file describes itself, and enter it here as two numbers so nothing is lost to rounding.
How do I convert anamorphic footage to square pixels?
Multiply the stored width by the pixel aspect ratio and keep the height, or divide the stored height by the pixel aspect ratio and keep the width. Both are given as outputs here. For a 704 × 480 frame at 10:11, the first gives 640 × 480 and the second gives 704 × 528; both are exactly 4:3. Which you choose is a resampling decision — widening interpolates new columns and preserves all the original detail, while shortening discards rows. For upscaling to an HD or UHD timeline the difference is usually immaterial, since the frame is being resampled anyway.
My old footage looks stretched or squashed — is this why?
Almost always. If a 720 × 480 file is treated as square-pixel by an editor, it is displayed at 1.5:1 instead of 4:3 or 16:9, so faces look wide and circles look like ellipses. If a 16:9 anamorphic file is interpreted as 4:3, everything looks tall and thin. The fix is to tell the software the correct pixel aspect ratio, or to rescale the footage to the square-pixel resolution this calculator gives you before importing it. Checking the numbers here first tells you which of the two problems you have.
Do modern cameras and codecs still use non-square pixels?
Rarely, and it is disappearing. Recommendation ITU-R BT.709 fixed 1:1 pixels for HD and BT.2020 does the same for 4K and 8K, so anything shot on a current camera in a current format has square pixels and this calculator returns the identity. The exceptions are legacy material — DV, DVD, broadcast archives — plus HDV, whose 1440 × 1080 frames carry a 4:3 pixel ratio to display as 16:9, and anamorphic cinematography, where the squeeze is optical rather than digital but the arithmetic is identical.
Can I use this for a 2.35:1 anamorphic film?
Yes, in the second mode: enter the stored dimensions and 2.35 and 1 as the display ratio, and the calculator returns the pixel ratio that produces it. Because 2.35 is not an integer the label falls back to the reduced form of the scaled fraction rather than a tidy pair — that is deliberate, since inventing a small integer ratio the input never contained would be wrong. The decimal pixel aspect ratio output is the number to use in software either way.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 590 calculators remain free
  • No billing is enabled
Coming soon