IP Camera Resolution Guide: 2MP to 8MP and Beyond
Choosing the right resolution for your IP cameras is one of the most important decisions in any surveillance project. Higher resolution captures more detail, but it also demands more bandwidth, storage, and processing power. This guide walks you through the most common IP camera resolutions, explains pixel density and identification distance, and helps you match the right resolution to each area of your site.
What Resolution Actually Means for IP Cameras
Resolution describes the number of pixels a camera sensor captures in each frame. It is typically expressed as megapixels (MP) or as a horizontal-by-vertical pixel count such as 1920×1080. More pixels means more detail in every image, which translates to better facial recognition, licence-plate reading, and forensic evidence. However, more pixels also means larger file sizes and heavier network traffic, so the goal is to choose the right resolution for each camera location rather than simply selecting the highest available.
A concept closely tied to resolution is pixel density, measured in pixels per metre (px/m) at the subject. Industry standards define several benchmarks: roughly 25 px/m for detection (is something there?), 62 px/m for recognition (what type of object?), and 125 px/m or more for identification (whose face is that?). The wider the field of view at a given resolution, the lower the pixel density becomes, so a 2MP camera aimed at a narrow doorway may outperform an 8MP camera covering an entire car park when it comes to identifying individuals.
Common IP Camera Resolutions
2MP / 1080p (1920×1080) — The long-standing workhorse of IP surveillance. A 2MP camera produces clear images suitable for most indoor applications, corridor monitoring, and entrance coverage where the subject is within roughly 10–15 metres. Storage and bandwidth requirements are modest, making 2MP a cost-effective choice for large deployments where hundreds of cameras are needed.
4MP (2560×1440 or 2688×1520) — Doubles the pixel count of 1080p, offering noticeably sharper images. 4MP cameras are popular in retail environments, office lobbies, and warehouse aisles. They strike a solid balance between image quality and resource consumption and have become the new default recommendation for many integrators.
5MP (2592×1944) — Offers a modest bump over 4MP with a 4:3 aspect ratio rather than the widescreen 16:9 format. The taller frame can be useful for areas where vertical coverage matters, such as stairwells or loading docks. Bandwidth is only marginally higher than 4MP.
4K / 8MP (3840×2160) — Four times the pixel count of 1080p. 4K cameras excel in wide-area coverage such as car parks, perimeter fencing, and public spaces where you need to digitally zoom into footage after the fact without losing useful detail. The trade-off is significantly higher bandwidth and storage requirements.
12MP and beyond — Multi-sensor and panoramic cameras now reach 12MP, 16MP, or even 32MP by stitching feeds from multiple imagers. These are specialist devices for overview coverage of stadiums, intersections, or large open-plan warehouses. They require substantial network and storage infrastructure.
Bandwidth and Storage Impact by Resolution
Every step up in resolution increases the data each camera generates. The table below provides typical estimates using H.265 compression at 15 frames per second with medium scene complexity. Actual figures vary with compression settings, scene motion, and quality targets.
Resolution Comparison: Bandwidth and Storage
| Feature | 2MP / 1080p | 4MP | 5MP | 8MP / 4K |
|---|---|---|---|---|
| Pixel Count | ~2.1 million | ~4 million | ~5 million | ~8.3 million |
| Aspect Ratio | 16:9 | 16:9 | 4:3 | 16:9 |
| Typical Bitrate (H.265, 15 fps) | 2–3 Mbps | 4–6 Mbps | 5–7 Mbps | 8–12 Mbps |
| Storage per Camera per Day | 15–25 GB | 30–50 GB | 35–55 GB | 60–100 GB |
| Identification Distance (approx.) | Up to 10 m | Up to 15 m | Up to 17 m | Up to 25 m |
| Best Use Cases | Indoor corridors, POS | Retail, offices, lobbies | Stairwells, loading docks | Car parks, perimeters, wide areas |
Compression: H.264 vs H.265
The codec your cameras and recorder use has a dramatic effect on bandwidth and storage. H.265 (HEVC) typically achieves 30–50% better compression than H.264 at similar image quality. For a 4K camera, this can mean the difference between 16 Mbps (H.264) and 10 Mbps (H.265) — a saving that compounds quickly across dozens of cameras and weeks of retention. Most modern NVRs and VMS platforms support H.265, and many cameras now also offer H.265+ or Smart Codec modes that further reduce bitrate by analysing scene activity in real time.
When planning storage, always confirm that your recording platform supports the codec your cameras will use. Mixing codecs across a site is perfectly fine — just ensure your storage calculations reflect each camera's actual settings rather than a blanket estimate.
Choosing the Right Resolution for Each Scenario
The best approach is to match resolution to the operational requirement of each camera position:
- Point-of-sale and cash registers: 2MP is usually sufficient because the camera is close to the subject (1–3 m) and the field of view is narrow.
- Retail aisles and office floors: 4MP provides excellent detail at medium distances and is the most popular choice for general-purpose indoor coverage.
- Licence-plate recognition (LPR): Dedicated LPR cameras are often 2MP but use narrow lenses and infrared illuminators. If using a general-purpose camera for LPR, 4MP or higher with a varifocal lens is recommended.
- Warehouse and car-park overview: 4K / 8MP cameras shine here because the wide field of view still retains enough pixel density for identification across large distances.
- Perimeter and critical infrastructure: 4K or multi-sensor cameras paired with analytics provide both overview and detail.
A common design technique is to mix resolutions on the same site: use 2MP cameras for interior corridors, 4MP for main areas, and 4K for wide-angle exterior coverage. This approach optimises both image quality and infrastructure cost.
Frequently Asked Questions
Not necessarily. 4K captures more detail, but if the camera is positioned close to the subject (e.g., a doorway or till), 2MP provides plenty of pixel density for identification. 4K is most beneficial for wide-area coverage where you need to digitally zoom into recorded footage.
A single 4K camera recording at 15 fps with H.265 compression generates roughly 60–100 GB per day. Over 30 days that is 1.8–3 TB per camera. For a 16-camera system, plan for approximately 30–48 TB of usable storage, plus RAID overhead.
Yes. Each camera's bitrate directly impacts your switch uplinks and backbone. A 2MP camera at 3 Mbps is manageable, but a 4K camera at 10–12 Mbps requires careful bandwidth planning, especially when aggregating traffic from many cameras onto a single trunk port.
6MP (3072×2048) cameras exist in some product lines and sit between 5MP and 8MP. They offer a good balance for scenarios where 4K is overkill but 4MP does not quite reach the required identification distance. Availability varies by manufacturer.
