Which NVR for an ANPR Camera in the UK (2026 Guide)

Most ANPR cameras read the plate on the camera itself, so a standard PoE NVR can usually record the footage. You only need an ANPR-capable NVR or a dedicated server if you want to search by plate, run allow/block lists or trigger alerts from the recorder. Whichever you choose, check that it accepts the camera's stream and plate events, has enough bitrate and PoE capacity, and has enough storage to cover your retention period under UK GDPR.

Does an ANPR camera need a special NVR?

Usually not for recording, but you may need a specific recorder model if you want to search footage by plate. An ANPR camera is still CCTV: an IP camera with extra analytics, so it records like any other.

An NVR (network video recorder) is the unit that stores streams from IP cameras sent over your network. You do need one for a multi-camera site, because the camera's microSD slot is a fallback for network outages, not a retention plan.

One installer on a forum thread said they believed the plate reading happens on the camera itself, leaving the recorder to store and index the results. They were unsure what the NVR adds beyond that, and ended up building their own database for plate data because the built-in whitelist and blacklist tools were basic. Treat that as one person's experience, not a rule for every make.

The failure to avoid is a system that records clean footage that nobody can search by plate. Before ordering, check the recorder's datasheet or the manufacturer's compatibility list for plate search, not just "supports 4K" or the right channel count.

Standard NVR, ANPR-capable NVR or dedicated ANPR server?

A standard or ANPR-capable NVR suits a single lane. Move to third-party software once you need barriers, integrations or reporting.

The table below is general guidance, not a statement about any particular model. Recorder behaviour varies, so check the manufacturer's compatibility listing before you buy.

	Standard NVR	ANPR-capable NVR	Dedicated server or third-party software
Who does the recognition	The camera, if it has ANPR at all	Usually the camera; the recorder stores and lists the reads	The camera, or the software's own engine
Plate search on the recorder	Time and event search only	Search by plate text	Search within the software, usually with more filters
Whitelist/blacklist	None	Basic, varies by model	Rule-based, able to trigger outputs
Database export	Footage export only	Limited	Built for it
Scale (lanes)	Overview cameras around the site	One lane or a small site	Many lanes or several sites
Best suited to	Context cameras beside the plate camera	Simple access logging	Barriers, reporting, integrations

One forum poster running ANPR cameras on a recorder believed the camera did all the processing. They described the recorder's whitelist/blacklist as very basic and ended up building their own database for the plate data. That is the case for third-party software when plate reads must feed other systems.

What to check on the camera side

A representative ANPR camera datasheet lists these:

• plate-list alarms
• RS-485
• alarm I/O
• a microSD slot

Plate-list alarms and alarm I/O decide whether the camera can act on a plate without the recorder. RS-485 and the microSD slot matter for peripherals and for keeping reads if the network drops.

A one-lane kit in the research pairs a single ANPR camera with a small PoE NVR and a 1TB hard drive. That is a sensible starting point for one entrance, but it does not replace the software route above.

Bitrate, channel count and PoE budget: what the recorder must handle

Size the NVR for your busiest plate-capture stream, not the average: incoming bandwidth, 60 fps channel support and PoE wattage must all clear that peak. Fast shutters and light compression make these streams heavier than a general-purpose camera at the same resolution. Read the bitrate from the camera's own interface at the settings you will deploy, then total the highest figures across all channels.

Bandwidth and frame rate

Take a camera with a 1/1.8" sensor, 1920×1080 at 60 fps and H.265/H.265+ options. Check the datasheet for two things on the recorder: its stated incoming bandwidth, and whether it accepts 60 fps on every channel rather than only some. Also confirm it handles whichever codec mode you enable. If it doesn't, fall back to standard H.265 and budget the extra bitrate.

PoE budget

Add up the camera draws from their datasheets, using the figure with IR on. IR ANPR cameras draw more than a basic dome. As general knowledge, 802.3af ports supply up to 15.4 W and 802.3at up to 30 W, but an NVR's total PoE budget is often lower than ports multiplied by that maximum. Leave headroom.

A 16-channel PoE recorder shares one built-in budget across all 16 ports. A 16-channel non-PoE recorder paired with a separate PoE switch lets you size the power budget independently and place the switch near the cameras.

Cable runs

Copper Ethernet has a 100 m channel limit, patch leads included. For runs over 50 m, Cat5e and Cat6 both reach 100 m. Cat6 gives more margin, but solid copper conductors and staying inside 100 m matter more than the category. Beyond 100 m, add a switch part-way along the run or use fibre.

Storage and retention: a worked example per camera

Storage per camera in gigabytes is bitrate (Mbps) ÷ 8 × 86,400 seconds × days, divided by 1,000 if you work in megabytes. Event-triggered recording cuts that figure sharply on a quiet gate but much less on a busy entrance.

Illustrative calculation (assumed 4 Mbps stream, not a product figure): 4 ÷ 8 = 0.5 MB/s, and × 86,400 gives 43.2 GB per day. Over 30 days of continuous recording that is about 1,296 GB. Substitute your camera's real configured bitrate.

Scenario (assumed activity)	Per day	30 days
Continuous	43.2 GB	1,296 GB
Quiet gate, recording ~10% of the day	4.32 GB	~130 GB
Busy entrance, recording ~50% of the day	21.6 GB	648 GB

The activity percentages are assumptions. Measure a week of real triggers before you rely on them.

Factors that move the number

• Codec: H.265+ typically lowers storage against plain H.264, but the saving depends on the scene, so check it on site.
• Lanes: each lane usually needs its own camera, so multiply the per-camera result by the camera count.
• Bays and RAID: a two-bay recorder can double capacity or, where the model supports it, mirror drives. Check the spec sheet for bay count and RAID support before ordering.

Size the drive for the retention period you have decided on, then add a margin; around 20% is a sensible rule of thumb. Use surveillance-rated drives, which are built for constant writing.

If plate reads are exported to a database, the snapshots and metadata may need their own storage and retention period. Plate data is personal data under UK GDPR, so set that period deliberately.

UK GDPR retention checklist for ANPR

Neither UK GDPR nor the ICO fixes a retention period for ANPR; you keep plate data only as long as your documented purpose requires. A plate read linked to a vehicle and time is personal data, so the whole system falls under data protection law.

The Surveillance Camera Code applies to "relevant authorities" such as the police and local authorities, not to every private operator. A private site isn't bound by it directly, but UK GDPR still applies. Check the current ICO video surveillance guidance before finalising your policy, as it is updated from time to time.

• Purpose and lawful basis: write down why you read plates (for example, access control) and the basis you rely on.
• DPIA: complete one where the processing is likely to be high risk, and keep it on file.
• Retention: justify the period in writing, then set the recorder's overwrite settings to match. A disk that simply fills and overwrites gives you whatever its capacity allows, which may not be what you justified.
• Signage: name the operator and state the purpose.
• Access controls and audit log: restrict who can view or export reads, and log who did.
• Subject access requests: have a tested export procedure, including how you redact other people's data.
• Whitelist and blacklist governance: treat the lists as personal data, with a named owner and a removal process.
• Annual review: revisit purpose, retention and the lists at least once a year.

When you size storage against your chosen retention period, you can open a trade account to see account pricing on recorders and drives.