Skip to content
OneKitly

Crop factor calculator

Find the equivalent full-frame focal length of a lens on a crop sensor.

Enter Lens focal length (mm), Crop factor and the Crop factor calculator works out Equivalent focal length (mm) straight away. For instance, with Lens focal length (mm) = 50 and Crop factor = 1.5 it returns Equivalent focal length (mm) = 75.

How to use it

  1. Enter your values: Lens focal length (mm), Crop factor.
  2. Read the result instantly: Equivalent focal length (mm).

Frequently asked questions

What does the Crop factor calculator actually compute?

It takes Lens focal length (mm) and Crop factor and derives Equivalent focal length (mm) from them. The calculation is live as you type, so the result updates on every change.

What information do I need to provide?

2 values: Lens focal length (mm) and Crop factor. Nothing else is required — no account, no file upload.

Can you show a worked example?

With Lens focal length (mm) = 50 and Crop factor = 1.5, the calculator returns Equivalent focal length (mm) = 75. Those figures come from running this exact tool, so you can reproduce them by entering the same values.

What happens if I enter larger values?

It moves a lot. Using Lens focal length (mm) = 55 and Crop factor = 3 instead, Equivalent focal length (mm) goes from 75 to 165 — which is why it is worth testing a few scenarios rather than trusting a single figure.

What does it give for smaller values?

Scaled down to Lens focal length (mm) = 45 and Crop factor = 0.75, Equivalent focal length (mm) comes out at 33.75. The relationship is worth checking at both ends before you rely on a single result.

When would I actually use this?

Finding out how big a thing will be before you make it: how many gigabytes an hour of footage takes, how long a file needs on the connection you have, how large a photo prints before it goes soft, what bitrate fits the budget you were given.

What is the most common mistake?

Taking the advertised connection speed as the transfer speed. A 100 Mb/s line is megabits, the file is in megabytes, and the eight-fold difference between them is where most download estimates go wrong — before overhead and contention take their own share.

Where do the figures come from, and how current are they?

Byte prefixes follow the IEC convention where a kibibyte is 1 024 bytes and a kilobyte is 1 000 — drive makers use the second, operating systems often report the first, and a disk that shrinks on arrival is that gap and nothing else. Print sizing assumes 300 dpi unless you change it.

Further reading

All guides