CCTV Lens Calculator

Pick your security camera's sensor, resolution and focal length and get the scene width, the angle of view, the pixels per metre at any distance, and how far it can detect, recognise or identify under EN 62676-4.

Free Instant No sign-up

Your camera & lens

Sensor
Recording resolution
Lens
Units
EN 62676-4 standard
Pixel density at that distance
0px/m
—
0scene width
0scene height
0horizontal angle
0vertical angle
0diagonal angle
0sensor area used
Maximum distance for each level
LevelMinimum densityUp to

Quick presets

What focal length do I need?

To cover a given scene width at a given distance, with the sensor and resolution above.

Focal length needed: — mm

How the CCTV lens calculation works

Everything comes from the sensor width s, the focal length f, the horizontal pixels P and the distance D (in mm inside the formulas):

Angle=2 × arctan( s ÷ (2 × f) )
Width=s × (D − f) ÷ f
px/m=P ÷ scene width

The angle is at infinity focus, the way manufacturers publish it, and the width uses the thin lens, as in our field-of-view calculator; at surveillance distances it is practically s × D ÷ f. The maximum distance for each level is the one that gives exactly that density: D = f + P × f ÷ (s × px/m). The reverse, "what focal length do I need?", solves for the focal length: f = D × s ÷ (width + s).

If the resolution does not match the sensor's shape (a 16:9 stream on a 4:3 sensor), the largest centred rectangle with the stream's shape is used: full width and cropped height, or the other way round. That way the vertical angle does not come from sensor height that is not being recorded.

DORI distances under EN 62676-4

The standard measures detail as horizontal pixels per metre on the person, based on a 16 cm face. The calculator flags the level you reach at your distance and the maximum distance for each one:

  • 2014 (DORI): detection 25, observation 62.5, recognition 125, identification 250 px/m.
  • 2025: Overview 20, Outline 40, Discern 80, Perceive 125, Characterize 250, Validate 500, Scrutinize 1500 px/m.

Switch the units to feet and every length and density converts exactly (1 ft = 0.3048 m): 250 px/m is 76.2 px/ft; Axis prints 76.

CCTV sensor formats: why 1/2.8″ is not 1/2.8 of an inch

The fractional-inch name comes from old camera tubes and is not a measurement: two "1/2.8″" sensors can have different areas. So the named sensors use the real recording area = pixels × unit cell from the maker's datasheet:

  • Sony IMX327 (1/2.8″, 2 MP): 1920 × 2.9 µm = 5.57 × 3.13 mm.
  • Sony IMX415 (1/2.8″, 8 MP): 3840 × 1.45 µm = 5.57 × 3.13 mm, the same width with four times the pixels.
  • Sony IMX335 (1/2.8″, 5 MP 4:3): 2592 × 2.0 µm = 5.18 × 3.89 mm.
  • OmniVision OS04C10 (1/2.9″, 4 MP): 2688 × 1.998 µm = 5.37 × 3.04 mm.
  • Sony IMX334 (1/1.8″, 8 MP): 3840 × 2.0 µm = 7.68 × 4.32 mm.

The "classic" 1/3″, 1/2″ and 2/3″ (4:3) are the traditional tube table, handy for unnamed sensors. If you know your sensor's pixel size, use "Custom" with pixels × pixel size.

Example: 2 MP camera with a 2.8 mm vs a 12 mm lens

1/2.8″ sensor (IMX327, 5.57 mm), 1920 × 1080, person at 10 m:

  • 2.8 mm: 89.7° × 58.4°; at 10 m the scene is 19.9 m wide → 96.6 px/m, observation. It identifies up to 3.86 m and detects up to 38.6 m.
  • 12 mm: 26.1° × 14.9°; at 10 m it is 4.63 m wide → 414.3 px/m, identification. It identifies up to 16.6 m and detects up to 166 m.

The datasheet of a 2 MP 1/2.8″ Dahua with a 2.8 mm lens gives DORI 38.6 / 15.4 / 7.7 / 3.9 m, the same as here (38.6 / 15.5 / 7.73 / 3.86 m) apart from rounding; we do not know which sensor it uses, so the maths uses the IMX327 area. Its angle, though, is 102°: with "By datasheet angle" at 102° the scene at 10 m is 24.7 m wide and the average density drops to 77.7 px/m. The difference is wide-angle distortion: the centre keeps the detail and the edges lose it.

Methodology & sources

Every result is computed in your browser with the formula shown above — nothing is sent to a server. The numeric model is based on this data and these references:

Formula reviewed and verified against real-world cases.

CCTV lens & DORI FAQ

What focal length do I need to identify a person at 10 m (33 ft)?
With a 2 MP camera (1920 pixels across) and a 1/2.8″ sensor (5.57 mm active width): to get 250 px/m the scene can be no wider than 1920 ÷ 250 = 7.68 m at 10 m, which takes a 7.2 mm focal length. An 8 mm lens meets it (276 px/m); a 6 mm stays at recognition (207 px/m). In the calculator, enter 7.68 m at 10 m under "What focal length do I need?".
Where do the 25, 62.5, 125 and 250 px/m DORI figures come from?
IEC/EN 62676-4:2014 starts from how many pixels fit across a face (16 cm on average): 4 to detect, 10 to observe, 20 to recognise and 40 to identify. Divided by 0.16 m they give 25, 62.5, 125 and 250 pixels per metre, measured horizontally at the person's distance. Axis rounds 62.5 to 63. In feet that is exactly 7.62, 19.05, 38.1 and 76.2 px/ft (Axis datasheets use 8, 19, 38 and 76; in practice 8, 20, 40 and 80). They are guidelines for a human operator in good conditions: light, compression or motion can call for more.
Why does my 2.8 mm camera cover more than the calculator says?
Because CCTV wide-angles have barrel distortion: they squeeze the edges to fit more scene in. The ideal-lens formula gives 89.7° for 2.8 mm on 1/2.8″; the datasheet of a 2 MP 1/2.8″ Dahua with a 2.8 mm lens says 102°. For the real coverage, pick "By datasheet angle" and type the maker's angle. That same datasheet's DORI distances (38.6 / 15.4 / 7.7 / 3.9 m) do match the ideal lens: they are worked out at the image centre.
More megapixels or a longer lens?
Density is proportional to pixels × focal length ÷ sensor width. Going from 2 MP to 8 MP on the same 1/2.8″ sensor doubles the horizontal pixels (1920 → 3840) and doubles every DORI distance without changing the angle: at 2.8 mm, identification goes from 3.86 m to 7.73 m. Doubling the focal length doubles the distance too, but halves the scene width.
What changes with EN 62676-4:2025?
The 2025 edition replaces the 4 DORI levels with 7: Overview 20, Outline 40, Discern 80, Perceive 125, Characterize 250, Validate 500 and Scrutinize 1500 px/m, still based on a 16 cm face. The 250 px/m that used to mean "identify" is now "characterize"; validating a known person takes 500. The calculator has both editions; it defaults to 2014, which is what the datasheets we checked still publish.