SD vs HD vs 4K for surveillance: what the resolutions actually mean, pixels per meter forensic standards (IEC 62676-4), storage and bandwidth math, AI analytics impact, and how to design a mixed-resolution fleet.
The video resolution conversation for surveillance is consistently the wrong conversation. Buyers fixate on whether 4K cameras are better than 1080p cameras, vendors compete on the highest pixel count they can ship, and procurement teams approve specifications that the storage budget cannot sustain six months into production. The right question is not which resolution is best. It is which resolution is operationally correct for each camera in the fleet, given the scene, the use case, the storage budget, and the bandwidth profile of the site.
This guide explains the difference between SD, HD, Full HD, and 4K resolutions, what those numbers actually mean for surveillance, how resolution affects forensic usability for face recognition, license plate recognition, and incident review, the storage and bandwidth math that resolution decisions drive, and the patterns that consistently work for designing a mixed-resolution camera fleet.
Video resolution is the number of pixels in the image, measured as horizontal pixels by vertical pixels. The major resolution tiers shipped in surveillance cameras in 2026 are the following.
SD (Standard Definition) typically refers to 720x480 pixels in the NTSC standard or 720x576 pixels in the PAL standard. SD was the dominant resolution for analog CCTV cameras shipped before the IP camera transition. In 2026, SD is essentially obsolete for new surveillance deployments and only appears in legacy analog installations that have not been upgraded.
HD (High Definition), also called 720p, refers to 1280x720 pixels. HD was the first widely-shipped IP camera resolution and is still common in cost-constrained deployments where the per-camera budget rules out higher-resolution alternatives.
Full HD, also called 1080p or 2K, refers to 1920x1080 pixels. Full HD is the most widely deployed resolution in 2026 surveillance and is generally the right default for indoor cameras, midrange outdoor cameras, and most general-purpose surveillance workloads.
4K, technically Ultra HD (UHD) at 3840x2160 pixels, delivers approximately four times the pixel count of Full HD. 4K is increasingly the default for outdoor wide-area cameras, license plate capture cameras, perimeter cameras, and any scene where the camera needs to cover a large area while preserving the ability to digitally zoom into specific details.
8K cameras (7680x4320 pixels) exist in 2026 but remain an edge category for surveillance because the storage, bandwidth, and processing costs rarely justify the pixel count over a well-placed 4K camera.
The pixel count is not the operational metric that matters. The metric that matters is pixels per meter at the distance the camera is mounted from the scene. A 4K camera that covers a 100-meter parking lot delivers fewer usable pixels per meter than a 1080p camera covering a 10-meter doorway. The 1080p camera will produce dramatically better forensic detail on the doorway even though its specification sheet shows four times fewer pixels.
The forensic usability standard for surveillance was formalized in the IEC 62676-4 standard and is operationally summarized as follows.
Detection of a person (deciding whether a moving object is a human) requires approximately 25 pixels per meter of subject height.
Observation of an event (general situational awareness, no identification) requires approximately 62 pixels per meter.
Recognition of a known individual (matching the person to someone the operator has seen before) requires approximately 125 pixels per meter.
Identification of an unknown individual (forensic identification suitable for evidence) requires approximately 250 pixels per meter.
License plate capture for ANPR requires 80 to 150 pixels across the plate width, depending on the plate format and the ANPR engine.
These pixel-per-meter requirements are what determine whether a camera resolution is operationally correct. A 1080p camera at the right distance and lens choice can deliver identification-grade pixels on a face. A 4K camera at the wrong distance and lens choice can deliver only observation-grade pixels on the same face. Resolution is necessary but not sufficient.
The comparison that matters maps each resolution tier to the surveillance workflows it can actually serve.
SD is operationally obsolete for new surveillance deployments. The pixel count is too low for reliable face recognition at any reasonable distance, the format is analog in most legacy installations and requires conversion to IP for modern VMS integration, and the storage savings versus HD are no longer meaningful given the cost trajectory of modern surveillance storage. The only place SD still belongs is in legacy deployments where the existing camera fleet has not been replaced and the budget for an upgrade has not landed. Plan to replace SD cameras in any deployment that processes identifiable footage for security, compliance, or evidence purposes.
HD is the cost-constrained default. The pixel count is sufficient for general situational awareness, motion detection, and observation-grade workflows at reasonable distances. HD struggles for face recognition beyond a few meters, struggles for license plate capture, and is no longer the optimal price-performance choice in 2026 because Full HD camera pricing has fallen to the point where the cost difference rarely justifies specifying HD. HD is operationally correct for low-priority indoor cameras (hallways, storage rooms, internal monitoring) where the budget per camera is genuinely tight and the workflow is observation rather than identification.
Full HD is the right default for most surveillance cameras in 2026. The pixel count is sufficient for face recognition at typical doorway distances, license plate capture at typical entry-point distances with the right lens, and operator-grade situational awareness across general-purpose scenes. Full HD's storage and bandwidth profile is well-understood, mature, and supported by every modern VMS and recording infrastructure. Buyers designing a new fleet should specify Full HD as the baseline and step up to 4K only for cameras where the scene size, the identification requirement, or the digital zoom workflow specifically justifies the additional cost.
4K is the right resolution for cameras where the scene is large, the identification requirement is high, or the operational workflow depends on digital zoom into a wide-area view. The typical use cases are perimeter cameras covering long fence lines, parking lot cameras covering large open areas, license plate capture cameras at vehicle entry points, and any camera where the VMS or AI model will need to extract identification-grade detail from a portion of the scene without re-aiming the optics. 4K is operationally heavy in storage and bandwidth, and the additional cost compounds across a large fleet. Specifying 4K for every camera is the most common cost mistake in 2026 surveillance procurement.
The storage requirement for a camera fleet scales with resolution, frame rate, codec efficiency, recording mode, and retention duration. Most procurement teams underestimate at least two of these variables, which means the storage budget surfaces as a problem six to twelve months after the fleet is live.
A representative storage profile for a single camera, recording continuously at 25 frames per second with H.265 encoding, runs approximately as follows in 2026 codec efficiency.
HD (720p) at moderate motion: 8 to 12 GB per camera per day. Full HD (1080p) at moderate motion: 16 to 24 GB per camera per day. 4K (UHD) at moderate motion: 60 to 120 GB per camera per day.
A 100-camera fleet running 4K at 30-day retention requires approximately 180 to 360 TB of storage capacity. The same fleet at Full HD requires approximately 48 to 72 TB. The storage cost difference at 100 cameras is meaningful. At 1,000 cameras, the storage cost difference is the entire budget conversation.
Three architectural choices materially change the storage math. Event-triggered recording, which records continuously at lower resolution and switches to high resolution only when motion or an event is detected, can reduce storage requirements by 40 to 70 percent depending on the scene. Variable bitrate H.265 encoding (and increasingly AV1 in 2026 deployments) reduces storage versus H.264 by 30 to 50 percent at equivalent visual quality. Tiered retention, where the most recent 7 days are stored at full quality and the next 23 days are downsampled or transcoded, reduces long-tail storage cost significantly.
The most common cost mistake is specifying continuous 4K recording across an entire fleet without modeling the storage trajectory at fleet maturity. The vendors that consistently deliver value design the fleet with mixed-resolution cameras matched to scene requirements, then apply event-triggered recording, H.265 or AV1 encoding, and tiered retention to control the total storage footprint.
Resolution drives bandwidth for live viewing and for site-to-site replication, not just for recording.
A Full HD camera streaming live at 25 fps with H.265 typically requires 1.5 to 4 Mbps. A 4K camera streaming live at 25 fps with H.265 typically requires 8 to 25 Mbps. Multiplied across a fleet of dozens or hundreds of cameras, the live viewing bandwidth load is real and frequently exceeds the design capacity of the network the cameras are running on.
The architectural pattern that works is to record full quality locally on the VMS and to deliver a lower-resolution proxy stream for live viewing, with the VMS transcoding on demand when an operator wants the full-quality view of a specific camera. This pattern decouples the recording resolution from the viewing bandwidth load, which means the fleet can record at 4K without consuming 4K bandwidth across every concurrent viewer.
For deployments with remote sites, the bandwidth math gets harder. A site with 50 4K cameras producing 12.5 Mbps each generates 625 Mbps of aggregate recording load, which exceeds the symmetric bandwidth of nearly every commodity site uplink. Recording locally and replicating selectively (only the cameras and time ranges that matter) is the architectural pattern that survives site-level bandwidth reality.
Resolution is a per-camera decision, not a fleet-wide decision. The strongest fleet designs match each camera's resolution to its scene and its workflow.
Step 1: Identify the operational task each camera serves. Detection only, observation, recognition, identification, or license plate capture. The IEC 62676-4 framework above maps each task to a pixels-per-meter requirement.
Step 2: Measure the scene. The distance from the camera to the subject, the subject height (typically 1.7 meters for adults), and the horizontal field of view the camera needs to cover.
Step 3: Compute the pixels per meter required at the working distance. Pixels per meter = (horizontal resolution / horizontal field of view in meters at the working distance).
Step 4: Match the resolution to the requirement. If a 1080p camera with the right lens delivers identification-grade pixels at the working distance, specifying 4K adds cost without operational value. If the scene requires identification-grade pixels at a distance where 1080p produces only observation-grade pixels, 4K is operationally required.
Step 5: Verify with a pilot. Pixel calculations work in theory. Production scenes have lighting, weather, and operational variations that calculators do not capture. A 30-day pilot on the actual scene with the actual lens validates the calculation in production conditions.
Most enterprise surveillance fleets in 2026 are mixed-resolution by design. A representative pattern in a large commercial facility looks approximately like this.
Entry doors, lobby cameras, and any scene where face identification is operationally required: Full HD with the right lens, or 4K if the scene is wide and the identification distance is meaningful.
Hallways, internal monitoring, and observation-grade workflows: HD or Full HD, with HD acceptable only if the cost difference per camera is material at scale.
Parking lots, perimeter cameras, and wide-area exterior coverage: 4K, often with multi-sensor 4K cameras for very wide scenes.
License plate capture at vehicle entry points: 4K (or specialized ANPR cameras with higher effective resolution on the plate region).
PTZ cameras: 4K is increasingly the standard, particularly for surveillance PTZ where the digital zoom workflow benefits from the additional pixel headroom.
This mixed pattern delivers identification-grade detail where the workflow needs it, controls storage and bandwidth where the workflow does not, and avoids the procurement mistake of either undersizing the resolution at critical cameras or oversizing the resolution across an entire fleet.
AI analytics performance is meaningfully sensitive to camera resolution. The relationship is not linear. Doubling the resolution does not double accuracy. Resolution affects different AI workloads differently.
Face recognition accuracy improves materially with resolution up to the point where the face occupies approximately 125 pixels per meter, beyond which additional resolution returns diminishing accuracy gains.
License plate recognition (ANPR/ALPR) is the most resolution-sensitive AI workload. Accuracy degrades sharply below 80 pixels across the plate width, which is why 4K cameras and specialized ANPR cameras are routinely specified for plate capture at vehicle entry points.
Object detection (person, vehicle, package) is relatively resolution-tolerant. A Full HD camera typically delivers strong object detection accuracy across a wide range of scene sizes. 4K does not materially improve object detection accuracy in most cases.
Pose estimation and unsafe behavior detection benefit from higher resolution because the model needs to resolve the relative position of body joints. Full HD is typically sufficient at typical working distances. 4K helps for wide scenes where the worker is far from the camera.
Crowd density and counting are relatively resolution-tolerant for density estimation but resolution-sensitive for individual-person tracking through the crowd.
The implication is that AI analytics performance should inform the resolution choice for cameras serving specific AI workloads, not the reverse. A camera specified for face recognition at the door benefits from Full HD or 4K with the right lens. A camera specified only for crowd density estimation in a lobby does not.
The pattern of mistakes is consistent enough across deployments to be worth naming.
Specifying 4K for every camera. The most common procurement mistake in 2026. The storage and bandwidth cost compounds across the fleet, the workflow on most cameras does not require the additional pixels, and the budget for the cameras themselves crowds out the budget for the surrounding infrastructure (storage, network, VMS licensing) that actually determines whether the fleet operates well.
Specifying HD or SD to save money. The other side of the same mistake. Cost-constrained deployments that under-specify resolution at critical cameras (entry doors, identification points, plate capture cameras) save money in procurement and lose it in operational value when the footage cannot deliver the identification the workflow was designed around.
Ignoring lens choice. Resolution and lens choice together determine pixels per meter at the working distance. A 4K camera with the wrong lens delivers worse forensic detail than a Full HD camera with the right lens. The lens specification is at least as important as the resolution specification.
Ignoring frame rate. Resolution and frame rate together drive storage and bandwidth. A 4K camera at 60 fps consumes nearly twice the storage of the same camera at 25 fps. Most surveillance workflows do not require frame rates above 25 fps, and many can run at 12 to 15 fps for observation-grade workflows. Specifying high frame rates uniformly is a routine source of unnecessary storage cost.
Ignoring codec efficiency. H.264 is still the most widely deployed codec in surveillance, but H.265 delivers 30 to 50 percent storage savings at equivalent quality, and AV1 is emerging in 2026 deployments for the additional efficiency gain. VMS platforms that support H.265 and AV1 transcoding give buyers a meaningful storage cost lever.
Ignoring retention requirements. Storage cost is roughly linear in retention duration. A fleet specified for 90-day retention requires three times the storage of the same fleet at 30-day retention. Procurement teams routinely default to long retention windows without modeling the storage cost trajectory.
Visylix is built to operate mixed-resolution camera fleets natively. The platform supports SD, HD, Full HD, 4K, and 8K cameras on the same deployment, with the recording engine handling each camera at its native resolution and the VMS applying analytics uniformly across the fleet regardless of source resolution.
Visylix supports H.264, H.265, and increasingly AV1 codecs natively, with server-side transcoding that allows the same camera stream to be recorded in one codec, viewed live in another, and replicated to a remote site in a third. The transcoding architecture decouples recording resolution from viewing bandwidth, which means a fleet recording at 4K does not have to consume 4K bandwidth across every concurrent viewer.
Event-triggered recording is supported across the entire fleet, with motion detection, AI-detection events, and operator-defined triggers driving recording behavior. Tiered retention policies allow the deployment to retain high-quality footage for the most recent days and transition older footage to lower-resolution or compressed storage automatically. The platform's 12 self-learning AI models, including face recognition, ANPR, object detection, pose estimation, and 8 others, are applied at the resolution each camera natively produces, with the analytics tuned to the resolution profile rather than forcing the camera to match a fixed analytics resolution.
The deployment model matches the storage and bandwidth reality of real fleets. Visylix runs as a Docker image on customer infrastructure, supports on-premise, edge, and air-gapped deployments, and integrates with S3-compatible archive tiering for long-tail storage cost control. Unlimited cameras at flat-rate pricing means the resolution decision is purely an operational and infrastructure decision, not a per-camera licensing decision.
If you are designing a surveillance fleet, modernizing an existing fleet, or running into the storage cost wall that a 4K deployment frequently hits, the Visylix team would welcome a conversation about how to design the fleet for operational fit rather than for marketing-grade resolution claims. Reach us at https://visylix.com/contact.
Video resolution for surveillance is not a one-resolution-fits-all decision. SD is operationally obsolete. HD is the cost-constrained default for low-priority cameras. Full HD is the right baseline for most cameras in a 2026 fleet. 4K is operationally correct for wide-area cameras, license plate capture, and any workflow where digital zoom into a portion of the scene is operationally required. The metric that determines whether a resolution is correct is pixels per meter at the working distance, not the raw pixel count on the specification sheet. The IEC 62676-4 framework maps detection, observation, recognition, and identification workflows to specific pixels-per-meter requirements that should drive the resolution decision per camera. Storage and bandwidth math scales with resolution, and the most common procurement mistake is specifying 4K across an entire fleet without modeling the storage trajectory at fleet maturity. Mixed-resolution fleets, paired with event-triggered recording, modern codec efficiency (H.265 and AV1), and tiered retention, deliver identification-grade detail where the workflow requires it while controlling cost where the workflow does not.
SD (Standard Definition) is typically 720x480 or 720x576 pixels, mostly seen in legacy analog cameras and operationally obsolete for new surveillance deployments. HD (High Definition) is 1280x720 pixels and serves observation-grade workflows but struggles with face recognition and license plate capture at distance. Full HD (1080p) is 1920x1080 pixels and is the right default for most modern surveillance cameras. 4K (Ultra HD) is 3840x2160 pixels and delivers approximately four times the pixel count of Full HD, suitable for wide-area cameras, license plate capture, and digital zoom workflows where the additional pixels are operationally required.
Not universally. 4K is better for wide-area scenes where the camera needs to cover a large area while preserving the ability to digitally zoom into specific details, for license plate capture at vehicle entry points, and for perimeter cameras where the scene is large. 1080p is better (or operationally equivalent) for indoor cameras, doorway cameras, and any scene where the camera is close enough to the subject that 1080p already delivers identification-grade pixels per meter. Specifying 4K uniformly across an entire fleet is the most common cost mistake in 2026 surveillance procurement.
The right answer depends on the scene, the workflow, and the camera placement. Full HD is the right baseline for most cameras in a 2026 fleet. 4K is the right answer for wide-area cameras, license plate capture, and digital zoom workflows. The correct framing is not which resolution is best universally, but which resolution delivers the pixels per meter the operational workflow requires at the working distance. The IEC 62676-4 framework maps detection, observation, recognition, and identification workflows to specific pixels-per-meter requirements.
A 4K security camera recording continuously at 25 fps with H.265 encoding typically consumes 60 to 120 GB per day, depending on scene complexity, motion patterns, and codec efficiency. The same camera at Full HD consumes 16 to 24 GB per day, and at HD consumes 8 to 12 GB per day. A 100-camera 4K fleet at 30-day retention requires approximately 180 to 360 TB of storage. Event-triggered recording, H.265 or AV1 encoding, and tiered retention can collectively reduce storage requirements by 50 to 80 percent versus continuous 4K recording.
1080p (Full HD) is 1920x1080 pixels and is the most widely deployed surveillance resolution in 2026. 4K (Ultra HD) is 3840x2160 pixels, approximately four times the pixel count of 1080p. 4K delivers better detail at distance and supports digital zoom workflows that 1080p cannot. The tradeoff is meaningfully higher storage and bandwidth requirements. For most general-purpose surveillance cameras, 1080p is the right baseline. For wide-area cameras, license plate capture, and digital zoom workflows, 4K is operationally required.
HD (720p) is operationally acceptable for observation-grade workflows on low-priority cameras, including internal hallways, storage rooms, and general monitoring where face recognition or license plate capture is not the operational requirement. HD struggles for face recognition beyond a few meters and for license plate capture at typical vehicle entry distances. For cameras serving identification-grade workflows or AI analytics requiring high pixels per meter on the subject, Full HD or 4K is operationally required.
Resolution is the total pixel count of the image. Pixels per meter is the pixel density at the working distance, which is what determines whether the camera can deliver the forensic detail the workflow requires. A 4K camera covering a 100-meter parking lot delivers fewer usable pixels per meter on a face at the far end of the lot than a 1080p camera covering a 10-meter doorway. The 1080p camera will produce better forensic detail on the doorway. Resolution is necessary but not sufficient. Pixels per meter at the working distance is the operational metric.
Resolution affects different AI workloads differently. License plate recognition (ANPR/ALPR) is highly resolution-sensitive and benefits materially from 4K cameras or specialized ANPR cameras. Face recognition is resolution-sensitive up to approximately 125 pixels per meter on the face, beyond which additional resolution returns diminishing accuracy gains. Object detection, pose estimation, and crowd density estimation are relatively resolution-tolerant, with Full HD typically sufficient at typical working distances. AI analytics performance should inform the resolution choice for cameras serving specific AI workloads, not the reverse.
Not necessarily directly to 4K. Replace SD cameras with the resolution that matches each camera's operational task. Cameras serving identification or AI analytics workflows benefit from Full HD or 4K, depending on scene size. Cameras serving observation-grade workflows can move to HD or Full HD without justifying the additional storage cost of 4K. The right framing is to design the replacement fleet around per-camera workflow requirements rather than upgrading uniformly to the highest available resolution.
H.265 (HEVC) is the most widely deployed codec for 4K surveillance in 2026 and delivers 30 to 50 percent storage savings versus H.264 at equivalent visual quality. AV1 is emerging in 2026 deployments and delivers additional efficiency gains, particularly for the AV1 hardware-decoder generation of modern processors. VMS platforms that support H.265 and AV1 transcoding give buyers a meaningful storage cost lever. H.264 remains the most universally compatible codec but is no longer the right choice for new 4K deployments where storage cost matters.