Choosing the Right IP Camera Resolution: 2MP vs 4MP vs 8MP

Camera resolution is one of the most consequential decisions in CCTV system design. It drives image quality, storage volume, network bandwidth and, through all three, project cost. Understanding the trade-offs between 2MP (1080p), 4MP (1440p) and 8MP (4K) is what lets you deploy the right camera at each position instead of the same camera everywhere.

The mistake that costs the most is specifying resolution as a headline number. A megapixel count on its own says nothing about whether a camera will produce a usable image of a face at the far end of a car park. What matters is pixel density at the target, meaning pixels per metre of scene, and that depends on resolution, lens focal length and distance together.

Pixel density is the real specification

EN 62676-4 gives the framework the industry uses, and it is worth committing the four levels to memory. Detect requires about 25 px/m, enough to know something is there. Observe requires 63 px/m. Recognize, meaning you can tell whether this is a person you already know, requires 125 px/m. Identify, meaning the image would support identification of a stranger, requires 250 px/m.

Those numbers are what turn an argument about megapixels into an engineering calculation. An 8MP camera on a wide lens covering a 40 m scene delivers roughly 95 px/m, nowhere near identification, despite being 4K. A 2MP camera on a narrow lens covering a 6 m scene delivers over 300 px/m and identifies comfortably. Resolution alone is meaningless without the distance and the lens.

To work out exactly how far a given resolution and lens combination reaches for each DORI level, use our free DORI Distance Calculator

Where 2MP still wins

The 2MP (1080p) camera remains the workhorse of the industry, and the reasons are sound. It delivers sufficient pixel density for general surveillance: entrance monitoring, corridor coverage, parking lot overview. At 15 FPS with H.265 compression a 2MP camera generates approximately 3-5 GB per day, making it the most storage-efficient option available. On projects with hundreds of cameras, 2MP frequently gives the best ratio of cost to coverage.

It also performs better than its megapixel count suggests in low light. For a given sensor size, fewer pixels means larger pixels, and larger pixels gather more photons. A 2MP camera and an 8MP camera on the same sensor format will not perform equally at night, and the 2MP one usually wins. In a poorly lit yard, the lower-resolution camera can produce the more usable image.

The 4MP middle ground

The 4MP camera hits a sweet spot for scenes that need more detail without the bandwidth burden of 4K. It provides approximately four times the pixel density of 1080p at the same field of view, enabling reliable facial identification at distances up to 15-20 metres with an appropriate lens. Retail environments, office lobbies and access points benefit clearly, and storage lands at roughly 1.5-2x that of 2MP.

In practice 4MP is the default for any position where the recorded image may need to answer a question rather than just show that something happened. That is most doors, most tills, most reception desks.

When 8MP earns its cost

The 8MP (4K) camera is at its best in wide-area surveillance, where a single camera replaces several lower-resolution units. City-centre intersections, large warehouse floors and perimeter runs benefit from 4K's ability to digitally zoom into a region of interest without losing usable detail. The economics work when one 8MP camera genuinely removes two or three 2MP cameras, with their mounts, cable runs and switch ports.

The economics stop working when 8MP is applied as a blanket standard. Storage and bandwidth run 3-4x higher than 2MP, which compounds across a large system into recorder capacity, disk count and licence cost. There are secondary costs too: 4K sensors need more light to perform, and 4K streams put real load on the client workstations that decode them.

• Storage and bandwidth roughly 3-4x a 2MP camera at equivalent frame rate
• Lower per-pixel light sensitivity, so night performance needs verifying on site
• Higher decoding load on viewing workstations, especially with multiple 4K tiles
• Larger lens and housing requirements, which affects mounting and discretion
• Genuine value where one camera replaces several, rather than as a default everywhere

Modelling the infrastructure before you commit

Resolution decisions become storage decisions the moment they are multiplied by camera count and retention period. A 90-day retention requirement on 200 cameras behaves very differently at 2MP than at 8MP, and the difference is measured in recorder hardware rather than in percentages.

To model the storage and bandwidth impact of different resolution mixes before finalising your design, use our free CCTV Storage Calculator

• Define the operational task at each position first: detect, observe, recognize or identify
• Measure the actual distance from mounting point to the target area
• Select lens and resolution together to meet the required pixel density at that distance
• Check night-time performance at the specified resolution, not just daytime
• Model total storage against the real retention obligation before selecting recorders

The right answer is almost never a single resolution across a site. It is a mix: 2MP for overview and general coverage, 4MP at the positions that have to answer questions, 8MP where one camera genuinely replaces several. Decide position by position, starting from the operational task and the distance, then verify with pixel density rather than with the number on the datasheet.