Planning guide

Security Camera Resolution and Megapixel Reference

A mechanism-level reference on security camera resolution: exact pixel counts per megapixel tier, the pixels-per-foot and IEC 62676-4 DORI density targets, the field-of-view-versus-detail tradeoff, sensor size and low-light behavior, and worked resolution recipes for a doorway, a driveway, and a parking lot.

5.0· 14 Google reviews

Updated 2026-07-24

EVOTECH technicians installing indoor and outdoor security cameras, with a monitoring wall and branded service van.
Illustrative brand image — security-camera and surveillance work.

The short answer

Resolution is not the single number that decides whether footage is usable; the number that matters is pixel density on the subject, measured as pixels per foot (PPF) or, in the IEC 62676-4 standard, pixels per meter (px/m). A camera's megapixel count sets how many pixels are available to spread across the scene, but the lens field of view decides how wide that scene is, and the two together set density. The industry rules of thumb are roughly 20 PPF to detect that a person or vehicle is present, about 40 PPF to recognize a known person or read large features, and 80 PPF or more to identify a stranger or capture court-usable facial detail. In metric terms IEC 62676-4 (the DORI framework) anchors Detection at 25 px/m, Observation at 62.5 px/m, Recognition at 125 px/m, and Identification at 250 px/m.

The exact pixel counts are: 2MP = 1920x1080 (2,073,600 px, 1080p), 4MP = 2560x1440 (3,686,400 px), 5MP commonly 2592x1944 (about 5.0 million px), 8MP = 3840x2160 (8,294,400 px, 4K UHD), and 12MP commonly 4000x3000 (12,000,000 px). To size a camera, divide horizontal pixels by the scene width in feet. A 4K camera's 3840 horizontal pixels give 96 PPF across a 40-foot-wide scene (identify-grade) but only 38 PPF across 100 feet (recognize-grade). So a doorway with a 6-to-10-foot view reaches identification even at 2MP, a driveway usually wants 4MP to 8MP, and a wide parking lot needs 8MP-plus, multiple cameras, or a PTZ because one fixed lens cannot both cover the area and identify faces at range.

Quick Decision: What Resolution for Which Scene

Start from the task, not the megapixel number. Decide whether you need to detect (something is there), recognize (a person you already know, or a large object), or identify (a stranger's face, a small logo, a license plate). Then measure how wide the area is that the camera must cover. Pixel density falls as scene width grows, so the same camera swings between identify-grade and detect-grade depending only on how wide you aim it. This is why a spec sheet alone cannot tell you if a camera is enough.

The horizontal math is simple and is the working heuristic installers use: PPF equals horizontal pixels divided by scene width in feet. For a 4K sensor (3840 px wide), a 20-foot-wide view yields 192 PPF, 40 feet yields 96 PPF, and 100 feet yields 38 PPF. A 4MP sensor (2560 px wide) yields 128, 64, and 26 PPF over the same widths. A 2MP sensor (1920 px wide) yields 96, 48, and 32 PPF over 20, 40, and 60 feet. Cross those figures against the 20/40/80 PPF targets to see which task each covers.

Vertical and target-plane density (how DORI measures) differ slightly from this horizontal shortcut, but for rectangular scenes the horizontal-PPF estimate is close enough to specify a system. When identification at range is the goal over a wide area, no single fixed lens satisfies both coverage and density; that is a multi-camera or PTZ problem, covered below.

  • Detect (is something there): about 20 PPF / 25 px-per-meter (DORI Detection) — general awareness, motion triggers.
  • Recognize (known person / large feature): about 40 PPF / 125 px-per-meter (DORI Recognition).
  • Identify (stranger's face, small text): 80+ PPF / 250 px-per-meter (DORI Identification).
  • Working formula: PPF = horizontal pixels / scene width in feet (e.g., 3840 px / 40 ft = 96 PPF).
  • 4K (3840 px) hits identify-grade to about 48 ft wide; 4MP (2560 px) to about 32 ft; 2MP (1920 px) to about 24 ft.
  • Beyond those widths the same camera drops to recognize- or detect-grade — add cameras, tighten the lens, or use a PTZ.

Real Pixel Counts by Megapixel Tier

Megapixels are literally the pixel count divided by one million, rounded to the sensor's marketing name. The common surveillance tiers and their exact active pixel arrays are fixed values, though a few tiers ship in more than one aspect ratio. 16:9 is standard for widescreen scenes; 4:3 sensors (common at 5MP and 12MP) trade width for height, which suits tall or narrow views like a corridor or a single doorway.

2MP is 1920x1080 for 2,073,600 pixels and is marketed as 1080p or Full HD. 4MP is 2560x1440 for 3,686,400 pixels (1440p, sometimes called 2K or QHD). 5MP is commonly 2592x1944 (about 5.0 million pixels, 4:3) though 16:9 5MP variants near 3072x1728 exist. 8MP is 3840x2160 for 8,294,400 pixels and is 4K UHD. 12MP is commonly 4000x3000 (12,000,000 pixels, 4:3), often used on multi-sensor and panoramic (fisheye) units.

Note that '4K' in consumer video sometimes means the DCI cinema width of 4096 pixels, but security 4K is the UHD figure of 3840x2160. More pixels also mean more data: higher tiers raise both storage and network bandwidth, which is a separate sizing exercise from optics. Compression codec (H.264 versus H.265/HEVC) roughly halves the bitrate for the same tier, and bitrate depends heavily on scene motion and configured quality.

  • 2MP = 1920x1080 = 2,073,600 px (1080p / Full HD, 16:9).
  • 4MP = 2560x1440 = 3,686,400 px (1440p / QHD, 16:9).
  • 5MP = commonly 2592x1944 ≈ 5,038,848 px (4:3); 16:9 variants near 3072x1728 exist.
  • 8MP = 3840x2160 = 8,294,400 px (4K UHD, 16:9) — security 4K is 3840 wide, not the 4096 DCI cinema width.
  • 12MP = commonly 4000x3000 = 12,000,000 px (4:3), frequent on multi-sensor and fisheye panoramic units.
  • Doubling megapixels roughly doubles pixel data; H.265/HEVC cuts bitrate about in half versus H.264 for the same tier.

Pixels Per Foot, DORI, and the IEC 62676-4 Standard

Two frameworks describe the same idea. In North America installers speak in pixels per foot (PPF) with a three-tier rule of thumb: about 20 PPF to detect, about 40 PPF to recognize, and 80+ PPF to identify. Europe and the international standard IEC 62676-4 use pixels per meter (px/m) and a four-tier scheme named DORI: Detection, Observation, Recognition, Identification. Because one meter equals 3.281 feet, the metric thresholds convert cleanly and let you check any spec against a published standard rather than a vendor claim.

IEC 62676-4 (2014/2015) sets Detection at 25 px/m, Observation at 62.5 px/m, Recognition at 125 px/m, and Identification at 250 px/m. Converting: 25 px/m is about 7.6 px/ft, 62.5 px/m is about 19 px/ft, 125 px/m is about 38 px/ft, and 250 px/m is about 76 px/ft. So the US '40 PPF recognize' aligns with DORI Recognition (125 px/m ≈ 38 px/ft), and '80 PPF identify' aligns with DORI Identification (250 px/m ≈ 76 px/ft). The US '20 PPF' label sits between DORI Detection and Observation.

Be aware the standard has been revised; later guidance has proposed raising the Identification target (some 2025 material cites 500 px/m) for higher-confidence facial evidence. For evidentiary face or plate capture, aim for the higher density and treat the 80 PPF / 250 px/m figure as a floor, not a target.

  • DORI (IEC 62676-4:2014/2015): Detection 25 px/m, Observation 62.5 px/m, Recognition 125 px/m, Identification 250 px/m.
  • Conversion factor: 1 m = 3.281 ft, so 25/62.5/125/250 px/m ≈ 7.6 / 19 / 38 / 76 px/ft.
  • US rule of thumb: ~20 PPF detect, ~40 PPF recognize, 80+ PPF identify — 40 and 80 PPF map to DORI Recognition and Identification.
  • DORI Detection assumes the subject occupies at least about 10% of image height; density is measured on the target plane, not the sensor.
  • Later revisions have proposed raising Identification toward 500 px/m for stronger facial evidence — treat 80 PPF as a floor for court use.
  • License-plate reading is a stricter sub-task: dedicated LPR cameras use narrow fields of view, fast shutters, and high on-plate density well above general identification.

Field of View vs Detail: Lens and Focal Length

Resolution is fixed by the sensor; how it is spent is decided by the lens. Focal length sets the horizontal field of view (HFOV), and HFOV sets scene width at any distance, which sets PPF. A short focal length (wide angle) covers a broad scene but spreads pixels thin; a long focal length (narrow) concentrates pixels for detail at range but sees a slice. You cannot get both wide coverage and high identification density from one fixed lens — that is the core tradeoff.

Typical HFOV values for a common 1/2.8-inch sensor: a 2.8mm lens gives roughly 100-110 degrees, 4mm about 80-90 degrees, 6mm about 50-55 degrees, 8mm about 40 degrees, and 12mm about 25-28 degrees. These figures shift with sensor size, because HFOV depends on both focal length and the sensor's physical width — a larger sensor behind the same focal length sees a wider angle. Always read HFOV from the camera's own datasheet rather than assuming from focal length alone.

Varifocal and motorized-zoom lenses let you tune HFOV on site to hit a density target at the actual scene distance, which is often more valuable than buying a higher megapixel tier. A 4MP varifocal set to a 40-degree view can out-resolve an 8MP fixed 2.8mm lens on a distant subject, because the pixels are concentrated where they are needed.

  • HFOV, not megapixels, sets scene width; PPF = horizontal pixels / scene width, so a narrower lens raises density at range.
  • Typical 1/2.8-inch sensor HFOV: 2.8mm ≈ 100-110°, 4mm ≈ 80-90°, 6mm ≈ 50-55°, 8mm ≈ 40°, 12mm ≈ 25-28°.
  • HFOV depends on sensor size too — the same focal length is wider on a larger sensor; confirm from the datasheet.
  • Wide (2.8-4mm) = broad coverage, low density; narrow (8-12mm+) = high density, narrow slice — no fixed lens does both.
  • Varifocal / motorized-zoom lenses let you dial HFOV to hit a PPF target at the real distance, often beating a higher MP fixed wide lens.
  • Concentrating pixels with a longer lens is frequently cheaper and sharper than raising the megapixel tier for range detail.

Sensor Size, Pixel Pitch, and Low-Light Behavior

More megapixels on the same physical sensor means smaller individual pixels (smaller pixel pitch), and smaller pixels gather less light. This is why megapixels and night performance can work against each other. A 4MP camera on a larger 1/1.8-inch sensor commonly outperforms an 8MP camera on a smaller 1/2.8-inch sensor after dark, because each of its pixels is physically larger and collects more photons. For scenes that are dark for much of the day, sensor size and pixel pitch matter as much as the resolution number.

Low-light capability also depends on the lens aperture and the sensor technology. A lower f-number passes more light: an f/1.0 or f/1.6 lens gathers substantially more than f/2.0. Modern low-light lines (marketed as Starlight, ColorVu, and similar) pair large-aperture lenses with sensitive back-illuminated sensors to hold color at very low illumination. Published minimum-illumination specs are given in lux, for example around 0.005-0.05 lux in color and 0 lux with infrared active — but read the test conditions, since manufacturers measure differently.

Infrared night vision extends range in total darkness but is monochrome and depends on IR LED reach. Typical built-in IR ranges run about 30 meters (roughly 100 feet), with long-range units reaching 60 meters or more. IR also does not increase pixel density, so identification at night still requires enough PPF on the subject within the IR throw.

  • Higher MP on the same sensor = smaller pixel pitch = less light per pixel; sensor size can matter more than the MP number at night.
  • A 4MP on a 1/1.8-inch sensor typically beats an 8MP on a 1/2.8-inch sensor in low light due to larger pixels.
  • Lens aperture: lower f-number passes more light — f/1.0 or f/1.6 gathers far more than f/2.0.
  • Low-light sensor lines (Starlight, ColorVu, etc.) hold color near 0.005-0.05 lux; verify each spec's stated test conditions.
  • Built-in IR typically reaches about 30 m (~100 ft); long-range models 60 m+ — but IR is monochrome and adds no pixel density.
  • Wide dynamic range (WDR), stated in dB (e.g., 120 dB), handles backlit scenes like a bright doorway or headlit driveway.

Worked Recipes: Doorway, Driveway, Parking Lot

A doorway is a narrow, close scene — the visible area at the door is often only 6 to 10 feet wide. At 8 feet wide, even a 2MP camera (1920 px) delivers 240 PPF, far above the 80 PPF identification floor, so any modern tier identifies faces here; the real work is mounting height and angle (about 5-7 feet, angled to catch faces rather than the top of heads) and WDR for backlight. A 4:3 tier such as 5MP suits a tall, narrow door view because it adds vertical coverage for packages on the ground and faces at standing height.

A driveway must both detect vehicles and, ideally, identify people and plates across roughly 15 to 40 feet of width. Over a 30-foot-wide view, 4K (3840 px) gives 128 PPF and 4MP (2560 px) gives 85 PPF — both identify-grade for faces. Reading a moving license plate is a stricter task: it needs a dedicated LPR camera with a narrow field of view, a fast shutter to freeze motion, and high on-plate density, not a general overview camera. Plan one camera for the plate and another for the wide scene.

A parking lot exposes the tradeoff plainly. Across 100 feet, 4K yields only 38 PPF (recognize, not identify) and 4MP yields 26 PPF (detect only). To identify people across a large lot you need multiple cameras, a tighter lens on key lanes, a multi-sensor unit, or a PTZ to zoom on demand — one fixed wide camera cannot both blanket the area and identify at range.

  • Doorway (6-10 ft wide): any tier identifies — 2MP over 8 ft = 240 PPF; prioritize 5-7 ft mount height, face angle, and WDR. Consider a 4:3 5MP for tall views.
  • Driveway faces (30 ft wide): 4K = 128 PPF, 4MP = 85 PPF — both identify-grade; 8MP adds margin and future crop room.
  • License plates: use a dedicated LPR camera (narrow FOV, fast shutter, high on-plate density) — a general overview camera will not reliably read moving plates.
  • Parking lot (100 ft wide): 4K = 38 PPF (recognize), 4MP = 26 PPF (detect only) — insufficient to identify strangers.
  • Wide-area identification needs multiple fixed cameras, a tighter lens on key lanes, a multi-sensor panoramic unit, or a PTZ for on-demand zoom.
  • Always size to the widest point the camera must cover, then verify PPF at that width before choosing a tier.

Frequently asked questions

Is a 4K camera always better than a 4MP camera for security?

Not always. 4K (8MP, 3840x2160) has more than double the pixels of 4MP (2560x1440), which helps identification across wider scenes and leaves more room to digitally crop. But on the same physical sensor, 4K's pixels are smaller and gather less light, so a 4MP camera on a larger sensor (for example 1/1.8-inch) often produces cleaner night images than a 4K camera on a smaller 1/2.8-inch sensor. 4K also roughly doubles storage and bandwidth versus 4MP. Choose by scene width and lighting: for a moderate area that is dark part of the day, a well-chosen 4MP can outperform 4K.

How many pixels per foot do I need to identify a face in court?

Plan for at least 80 pixels per foot (PPF) on the subject, which corresponds to the IEC 62676-4 DORI Identification threshold of 250 pixels per meter (about 76 px/ft). Because standards guidance has moved toward higher confidence for facial evidence (some 2025 material cites 500 px/m), treat 80 PPF as a floor rather than a target and aim higher when the footage may need to identify a stranger. Verify density at the actual subject distance using PPF = horizontal pixels divided by scene width in feet, and confirm the subject is well lit and not motion-blurred, since density alone does not guarantee a usable image.

What resolution do I need to read a license plate?

License-plate reading is a specialized task that a general overview camera rarely handles well, regardless of megapixel tier. It requires a dedicated LPR/ANPR camera with a narrow field of view aimed at the plate lane, a fast shutter to freeze vehicle motion, high pixel density on the plate itself, and often infrared plus the ability to handle headlight glare. A wide 4K camera covering an entire driveway spreads its pixels too thin and blurs moving plates. The practical approach is two cameras: one dedicated plate camera on the entry lane and a separate camera for the wide scene and faces.

Does a higher megapixel camera use more storage and internet bandwidth?

Yes. Data scales roughly with pixel count, so moving from 2MP to 4MP to 8MP increases both recording storage and network bandwidth. The exact rate depends on the compression codec, frame rate, and how much motion is in the scene: H.265/HEVC roughly halves the bitrate of H.264 for the same resolution and quality. As a rough planning range, a 4K stream may run several times the bitrate of a 2MP stream at matched settings. Because figures vary widely with configuration, size storage with a calculator using your actual tiers, frame rates, retention days, and codec rather than a single rule of thumb.

Our work

Clean installs across the Houston area

See all our work
Network cable testing and certification by Evotech IT LLC, Houston areaConference room TV mount and network install by Evotech IT LLC, Houston TXUniFi network rack with UPS and switches installed by Evotech IT, HoustonStructured cabling room with patch panels and network rack — Evotech IT LLC, Houston TX
Call WhatsApp