Hyperfocal distance calculator
Find the hyperfocal distance for sharp landscape photos from focal length, aperture and circle of confusion.
Related tools
All Data & computing tools →Need Hyperfocal distance (m)? The Hyperfocal distance calculator derives it from Focal length (mm), Aperture (f-number), Circle of confusion (mm) in one step. For instance, with Focal length (mm) = 50, Aperture (f-number) = 8 and Circle of confusion (mm) = 0.03 it returns Hyperfocal distance (m) = 10.467.
How to use it
- Enter your values: Focal length (mm), Aperture (f-number), Circle of confusion (mm).
- Read the result instantly: Hyperfocal distance (m).
Frequently asked questions
How does the Hyperfocal distance calculator work?
It takes Focal length (mm), Aperture (f-number) and Circle of confusion (mm) and derives Hyperfocal distance (m) from them. The calculation is live as you type, so the result updates on every change.
Which values does the calculator ask for?
3 values: Focal length (mm), Aperture (f-number) and Circle of confusion (mm). Nothing else is required — no account, no file upload.
What does a typical calculation look like?
With Focal length (mm) = 50, Aperture (f-number) = 8 and Circle of confusion (mm) = 0.03, the calculator returns Hyperfocal distance (m) = 10.467. Those figures come from running this exact tool, so you can reproduce them by entering the same values.
How much does the result change with different inputs?
It moves a lot. Using Focal length (mm) = 100, Aperture (f-number) = 16 and Circle of confusion (mm) = 0.06 instead, Hyperfocal distance (m) goes from 10.467 to 10.517 — 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 Focal length (mm) = 25, Aperture (f-number) = 4 and Circle of confusion (mm) = 0.015, Hyperfocal distance (m) comes out at 10.442. 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?
Reading a figure in one unit next to a figure in another. Megabits are not megabytes and the eight-fold gap sinks most transfer estimates; a kilobyte is 1 000 bytes to a drive maker and 1 024 to the operating system; pixels are not dots per inch. None of it is hard arithmetic — the unit on each side is what decides whether the answer means anything.
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.