An LPR security camera captures vehicle plates and converts them into searchable numbers. For a gate, parking entrance or traffic checkpoint, the right camera depends on capture distance, vehicle speed, plate format, lighting and how you will use the result. This guide explains those decisions and compares documented Hikvision and Dahua ANPR models.
Table of Contents
- Start With the Job: Plate Evidence or Automatic Recognition?
- What Is an LPR Security Camera and How Does It Work?
- LPR vs ANPR vs Regular Security Cameras
- Key Specs That Determine License Plate Capture Success
- Choose an LPR Camera by Distance and Speed
- Installation: Angle, Plate Size and Night Settings
- Example Plate Captures
- NVR, Plate Search and Gate Integration
- US Privacy and Data Retention
- Project Specification Checklist
- Frequently Asked Questions
Start With the Job: Plate Evidence or Automatic Recognition?
| Your requirement | What the system must do | What to select |
|---|---|---|
| Review a vehicle incident | Record a readable image of the plate | A camera and lens configured for license plate capture; automatic recognition is optional |
| Search entries by plate number | Read characters and store searchable events | An LPR/ANPR analytics engine plus compatible event storage and search |
| Open a barrier for approved vehicles | Read, compare with an allowlist and send a control signal | An ANPR camera or processor, allowlist logic and a compatible barrier controller |
| Watch a parking lot or driveway | See people, vehicles and incidents across the scene | Overview security cameras; add an LPR camera only at the plate capture point |
Do not make a single wide-angle overview camera responsible for reading plates across an entire parking lot. Plate recognition needs a defined capture area. The rest of the parking lot needs its own surveillance coverage.
What Is an LPR Security Camera and How Does It Work?
LPR means license plate recognition; ANPR means automatic number plate recognition. Both refer to software that reads a plate from an image. ALPR is another common name. License plate capture is different: it records a readable image but does not automatically turn the plate into text.
- Capture: A camera records the vehicle at a defined point. Lens, shutter, exposure and illumination must preserve the plate characters.
- Recognize: Analytics locate the plate and read its characters. The software runs in the camera, on a recorder or on a separate server, depending on the system.
- Use the event: The system stores a plate number, time and associated image, searches past events or sends an access-control command.
Some ANPR models also identify vehicle type, color, brand and direction. These are model-specific analytics, not universal LPR features. Likewise, supported plate countries and regional algorithms depend on the camera's firmware and configuration.
LPR vs ANPR vs Regular Security Cameras
| Camera or system | Readable plate image | Search by plate number | Best use |
|---|---|---|---|
| Standard security camera | Possible at short distance with suitable light and exposure; not designed for consistent moving-vehicle plate capture | No, unless separate recognition software processes its images | General surveillance, vehicle color, activity and context |
| Dedicated license plate capture camera | Optimized for a defined lane, including challenging night scenes | Only when paired with recognition analytics | Plate evidence where text-based searching is not required |
| LPR / ANPR camera or system | Yes, within the model's stated installation limits | Yes, when the recorder or software stores and indexes LPR events | Gates, parking access, vehicle logs and plate-based searches |
A high megapixel count does not make a wide-angle security camera an ANPR camera. The plate needs enough pixels, sharp focus, suitable exposure and recognition software. See Axis's license plate capture white paper for the difference between capturing and recognizing plates.
Key Specs That Determine License Plate Capture Success
| Specification | What it changes | Buyer check |
|---|---|---|
| Documented capture distance | The distance at which the model is designed to read plates | Use the ANPR capture range, not the DORI distance or general night-vision range |
| Vehicle speed limit | Whether moving vehicles stay within the model's rated detection conditions | Compare the actual speed at the capture point with the rating for that model and installation type |
| Lens and capture width | How large the plate appears in the image and how many lanes fit | Confirm focal-length version, measured lane width and plate pixel size |
| Shutter, gain and lighting | Control motion blur, noise and washed-out reflective plates | Test daytime and night images at the real vehicle speed |
| Plate-region support | Which national plate formats the software recognizes | Check the exact regional algorithm and firmware, especially for US/Canadian projects |
| Event and control interfaces | Whether the plate read can trigger searches, notifications or gates | Confirm the recorder/VMS, API, physical alarm output and controller requirements |
| Outdoor protection | Survival in dust, rain and exposed mounting areas | Check IP/IK ratings and permitted power source on the exact SKU |
Three values must not be confused: a sensor's maximum electronic shutter speed is not a rated vehicle speed; a camera's DORI “recognize” distance is not its ANPR recognition distance; and a general video IR range is not necessarily its ANPR illumination range.
Choose an LPR Camera by Distance and Speed
The models below show why it is unsafe to recommend one shutter speed, lens or capture distance for every LPR project. The values come from the manufacturers' published product specifications.
| Camera / version | Motorized lens | Documented ANPR capture distance | Rated vehicle speed | Documented width / illumination |
|---|---|---|---|---|
| Dahua ITC413-PW4D-Z1 / IZ1 | 2.7–12 mm | 3–8 m (10–26 ft) | Up to 80 km/h (50 mph) | Detection width 3–4 m; ANPR illumination 10 m |
| Dahua ITC413-PW4D-Z3 / IZ3 | 8–32 mm | 8–30 m (26–98 ft) | Up to 120 km/h (75 mph) | Detection width 6–8 m; ANPR illumination 30 m |
| Hikvision iDS-2CD7A46G0/P-IZHS(Y) | 2.8–12 mm or 8–32 mm | Lens-dependent; no single ANPR distance is stated in the cited product specification | 120 km/h front in checkpoint mode; 80 km/h side | IR range 50 m (2.8–12 mm) or 100 m (8–32 mm); these are not ANPR capture-distance claims |
Sources: Dahua ITC413-PW4D Series specifications; Hikvision iDS-2CD7A46G0/P-IZHS(Y) specifications. Speed and accuracy claims apply under the manufacturers' specified conditions.
What the accuracy figures actually mean
| Manufacturer's model | Stated plate recognition rate | Scope of the claim |
|---|---|---|
| Hikvision iDS-2CD7A46G0/P-IZHS(Y) | ≥98% (vehicle capture rate ≥99%) | Recommended installation and lighting conditions; Hikvision's global page lists supported regions mainly across Europe, the Middle East, Asia-Pacific and Africa |
| Dahua ITC413-PW4D Series | ≥98% for European plates; ≥96% for other supported plates | Recommended installation and lighting conditions; exact country/region algorithm must match the project |
For North American installations: Dahua lists the United States and Canada within its supported plate-region options. The cited Hikvision global specification does not list the Americas in its main LPR regions. Do not assume a camera supports local plates merely because its specification says “120+ countries.” Confirm the supplied regional firmware and recognition package for the destination country before ordering.
For a stop-and-go entrance at 3–8 m, the Dahua Z1/IZ1 range is a documented match. At 8–30 m, the Z3/IZ3 range is a documented match. For a Hikvision project, select the lens and capture position using its installation guidance, then verify plate size and speed on-site. A 120 km/h rating does not mean the camera will read plates 100 m away.
Installation: Angle, Plate Size and Night Settings
Plan the capture point before mounting the camera. Record the distance to the plate, camera height, side offset, lane width and actual vehicle speed. Then test with the plates used at that site.
| Installation check | Practical rule | Why it matters |
|---|---|---|
| View angle | Aim close to the vehicle's travel axis. Axis recommends keeping the combined angle between camera and vehicle below 30°, not treating horizontal and vertical limits as separate allowances. | Steeper angles reduce character detail and increase motion across the image. |
| Plate size | Zoom to the actual capture point and inspect pixels across the plate. Axis calculates about 74 pixels across a standard European plate as a basic imaging minimum; smaller plates need more resolution. | Global “70-pixel” or “150-pixel” rules do not apply to every plate format and OCR engine. |
| Capture width | Keep the target lane as tight as the use case permits. The Dahua Z1/IZ1 has a published 3–4 m detection width; the Z3/IZ3 has 6–8 m. | A wider scene spreads the available pixels over more road surface. |
| Shutter and gain | Start with the manufacturer's ANPR profile. Adjust exposure to stop motion blur, and limit gain if reflective plates are overexposed. | Short exposure freezes vehicles but admits less light. |
| IR and headlights | Use the model's ANPR illumination rating. Test with headlights on and with actual nighttime traffic. | Ordinary video IR-range claims do not establish nighttime plate-read range. |
| WDR / HLC | Do not enable high WDR by default. Test the ANPR profile and the available HLC/WDR settings against moving plates. | Some WDR techniques produce motion artifacts. Axis recommends WDR off unless a suitable artifact-free mode is available. |
Source: Axis, License Plate Capture. The numerical angle and pixel guidance is from Axis; Hikvision and Dahua projects must also follow their model-specific installation instructions.
Field acceptance test before buying in volume
- Lock the test conditions: Record the camera model/firmware, lens setting, distance, mounting geometry, lane width, plate country and speed at the capture point.
- Test the real traffic: Include approaching and departing vehicles, day and night, headlights on, and the fastest normal approach speed.
- Measure two results separately: Vehicle capture rate = vehicles with a stored plate event ÷ vehicles passing the capture point. Correct plate read rate = events with the full plate string correct ÷ captured plate events. Record missed vehicles and incorrect characters.
- Test the business workflow: Search by number, retrieve the linked image/video, check allowed and denied plates, then disconnect the network to confirm the required fallback behavior.
A manufacturer's laboratory recognition figure and the site's measured acceptance result answer different questions. Use both, and set your project pass criteria before testing.
Example Plate Captures
The image and footage below give a visual example of plate capture. A sample alone does not prove the recognition rate at another distance, speed or location. For a project review, label each sample with the camera model, lens, distance and day/night conditions.
NVR, Plate Search and Gate Integration
Reading the plate is only one step. Confirm where the text is processed, where events are stored and how the result reaches the equipment that needs it.
Camera-side vs recorder/server-side recognition
| Factor | Camera-side ANPR | Recorder or server-side ANPR |
|---|---|---|
| Recognition work | The camera runs the plate analytics and sends event data | The recorder/server analyzes incoming images or video |
| Network and processing | Can send compact text events plus snapshots; uses the camera's processing hardware | Uses recorder/server processing and receives the video/images needed for analysis |
| Equipment selection | Confirm the camera's plate regions, event protocol and outputs | Confirm which camera streams, channels and analytics packages the recorder/software supports |
| Licensing | Check the exact camera firmware, management platform and required integrations | Check the exact NVR/VMS product and license schedule |
Do not assume “no license” for edge ANPR or “per-channel license” for all server systems. Fees belong to the specific product and platform, not the processing architecture.
Can any ONVIF NVR search LPR plates?
No. Showing a camera's video through ONVIF does not prove the recorder can receive plate metadata, search plate events or control a barrier. ONVIF Profile M defines analytics metadata and events, including license plate information, but support is conditional on the actual device and client features. Verify the exact camera firmware and NVR/VMS implementation before promising a cross-brand plate search.
Hikvision and Dahua also provide native platform and API integration paths. The Dahua ITC413-PW4D specification explicitly lists API and SDK support, two relay outputs, RS-485 and Wiegand. Check the specific controller's wiring and protocol before installation. For standard camera/NVR connection steps, see the cross-brand ONVIF setup guide; video connection alone is not ANPR integration.
Gate automation and searchable event workflow
- The camera or system detects an approaching vehicle and reads the plate.
- The software compares the plate string with an approved or restricted list.
- The configured controller receives a supported relay/API/serial command and opens the barrier when its access rules are met.
- The system records the time, recognized plate, image and decision for authorized review.
For a multi-entry site, confirm how lists synchronize and what happens if the network, recorder or recognition service fails. A local camera relay and a central access-management platform have different failure paths.
Ask for an integration demonstration of all four functions: live video, plate text, plate-number search and gate output. Seeing only the live video feed is not enough.
Equipment needed for two common project types
| Project | Equipment and checks |
|---|---|
| One controlled entrance with a local allowlist | ANPR camera with the right plate-region package and lens; supported camera power/PoE switch; compatible barrier controller and safety devices; appropriate mounting, surge protection and fallback access method. Confirm whether the camera's local relay can handle the complete access rule. |
| Multiple entrances with plate search and central management | ANPR cameras at defined capture points; network and power sized for the actual devices; compatible NVR/VMS or management platform that indexes plate events; central list management, access outputs, storage and backup power as required. Verify software licenses, bandwidth and retention settings on the chosen platform. |
US Privacy and Data Retention
There is no single US-wide number of days that every private LPR installation must retain plate data. State rules differ by operator and use. Do not copy a police retention deadline into a private parking-lot specification.
| Legal example | Who the rule addresses | What the text establishes |
|---|---|---|
| California SB 34 / Civil Code §§1798.90.51–.53 | ALPR operators and end users, including non-government operators within the statute's definitions | Requires security practices and a usage/privacy policy addressing purposes, access and retention/deletion; this is not a blanket 60-day rule for private parking lots |
| California Vehicle Code §2413 | California Highway Patrol | Sets a 60-day limit on its LPR data, with stated investigative/evidence exceptions |
| Virginia Code §2.2-5517 | Law-enforcement agencies and vendors contracting with them under the statute | Sets 21 days for covered system data, subject to stated exceptions; it is not a general rule for every private business |
For a commercial project, define the operating purpose, authorized users, audit logs, access and sharing controls, plate-data retention and deletion process. Check local laws and any customer-sector requirements before selecting a retention period. The site owner should have its applicable policy reviewed by qualified counsel; this article is technical purchasing information, not legal advice.
Project Specification Checklist
Before requesting cameras, NVRs or access hardware for a project, record these details:
- Location and plates: Destination country/state, plate formats, single- or double-line plates, standard or specialty plates.
- Capture point: Number and width of lanes, distance, camera height, side offset, direction and actual vehicle speed.
- Conditions: Day/night operation, headlights, ambient light and the intended IR/white-light approach.
- Outcome: Plate image only, searchable text, allowlist/blocklist, barrier control or vehicle attributes.
- System: Existing NVR/VMS and firmware, API/relay requirements, PoE/power, local storage, network outage behavior and data retention.
- Acceptance: Required capture and correct-read results, test traffic and agreed pass/fail conditions.
For product specifications, compare the Dahua ANPR camera range or review the Hikvision iDS-2CD7A46G0/P-IZHS model details. Confirm the exact lens, suffix, country support and recorder before placing a project order.
Frequently Asked Questions About LPR Security Cameras
Can a regular security camera read license plates?
It can capture a readable plate image when the vehicle is close enough, the lighting is suitable and the exposure freezes the characters. It does not automatically convert a plate image into searchable text without LPR software. For consistent moving-vehicle recognition, use a system rated and configured for that capture point.
Can LPR cameras read plates at night?
Yes. Dedicated models use short exposure times and controlled illumination for night capture. Use the manufacturer's ANPR illumination range and test reflective plates with headlights on. General night-vision range is not a plate-read rating.
How far away can an LPR camera read a plate?
The Dahua ITC413-PW4D-Z1/IZ1 has a documented ANPR capture range of 3–8 m; Z3/IZ3 has 8–30 m. Other models have different ranges. The Hikvision iDS-2CD7A46G0/P-IZHS(Y) offers two lens ranges, but its published general IR/DORI figures should not be presented as guaranteed LPR distances.
What shutter speed is needed for a moving plate?
There is no universal shutter value by mph alone. Required exposure also depends on the camera angle, plate size, lighting and image processing. Choose a camera whose rated vehicle speed covers the site, then use its ANPR settings and adjust exposure from moving-plate tests. Axis's technical guide provides angle-and-speed-based exposure examples.
How accurate are Hikvision and Dahua ANPR cameras?
Hikvision specifies ≥98% license plate recognition for the iDS-2CD7A46G0/P-IZHS(Y) under recommended installation and lighting conditions. Dahua specifies ≥98% for European plates and ≥96% for other supported plates for the ITC413-PW4D Series under its stated conditions. These figures are not guarantees for every country, mounting layout or light level.
Can an ANPR camera open a gate without a separate recognition server?
Yes, where the selected edge-ANPR camera has the needed allowlist logic and compatible control output. The Dahua ITC413-PW4D Series includes two relay outputs and interfaces for access equipment. The barrier controller, wiring, safety interlocks and fallback rule must still be confirmed.
Will an ONVIF-compatible NVR store and search plate numbers?
Not automatically. ONVIF video compatibility and ANPR metadata/search integration are separate capabilities. Test the exact firmware pair for plate events, snapshots and text search; check Profile M feature support or the vendor's native integration.
Request a Project Equipment Quote
For Hikvision or Dahua ANPR equipment, send your lane layout, target plate region, capture distance, vehicle speed and existing recorder/controller models. We can check model availability, regional variants and required accessories against that specification.