License plate recognition cameras—often called ALPR (Automated License Plate Recognition) systems—have moved from law enforcement exclusivity to mainstream commercial site security over the past decade. Today, construction sites, utility facilities, distribution centers, and parking operations use LPR to control access, document vehicle activity, and generate instant alerts when a known-threat vehicle enters the property.
Understanding how these systems actually work helps you deploy them effectively and set realistic expectations for read accuracy, integration requirements, and what the data will—and won't—tell you.
How ALPR Technology Works
An LPR camera doesn't simply "read" a license plate the way a human does. The system processes the image through several steps:
- Detection: The camera identifies a region of interest in the frame that likely contains a license plate, based on shape, contrast, and aspect ratio
- Segmentation: The plate region is extracted and pre-processed to normalize contrast and correct for angle
- Character recognition: OCR (optical character recognition) software identifies each character in the plate, using algorithms trained on thousands of plate formats
- Jurisdiction matching: The character string is matched against known formats for each state or province to validate the read and identify the issuing jurisdiction
- Database lookup: The confirmed plate is checked against configured watchlists (whitelist, blacklist, hot list) and an appropriate action is triggered
This entire process takes 200–500 milliseconds from vehicle detection to alert or gate trigger. For most access control applications, this is fast enough to operate without perceptible delay at controlled entry points.
Camera Hardware Requirements for Accurate LPR
General-purpose security cameras don't perform well as LPR systems. The requirements for accurate plate capture are specific and differ meaningfully from those for scene monitoring:
Resolution: A license plate character is typically 4–5 inches tall. For accurate OCR, the character needs to be at least 20–30 pixels tall in the image. This drives the lens focal length requirement—at 30 feet, capturing a 5-inch character at 20 pixels requires specific pixel-per-foot calculations that most wide-angle security cameras can't achieve.
Shutter speed: Vehicles moving at 10 mph travel 1.5 feet per second. At 20 mph, that's 3 feet per second. To avoid motion blur, shutter speeds of 1/1000 second or faster are needed. Most security cameras default to slower shutters for low-light performance, which introduces blur at anything above parking-lot creep speeds.
IR illumination: Dedicated LPR cameras use illuminators specifically matched to the retroreflective material used on license plates. Standard visible-light illuminators don't produce the consistent white plate image that optimizes OCR accuracy in darkness.
Contrast management: License plates are designed to have high contrast between characters and background. However, headlight glare at night can cause overexposure on the plate region. Professional LPR cameras use wide dynamic range (WDR) sensors optimized for exactly this condition.
| Specification | General Security Camera | Dedicated LPR Camera |
|---|---|---|
| Resolution at plate | Often insufficient | Engineered for 20+ px per character |
| Motion handling | Tuned for slow/no motion | 1/1000s+ shutter |
| IR illumination | General scene | Plate-optimized wavelength |
| Dynamic range | 60–90dB | 100–130dB WDR |
| Read accuracy | 50–70% (best case) | 92–99% |
Watchlists: Whitelists, Blacklists, and Hot Lists
ALPR systems derive most of their operational value from watchlist functionality. Three types of lists handle different security functions:
Whitelist (authorized vehicles): Plates on the whitelist are automatically permitted—gates open, no alert is generated, but the entry is logged. This is used for known employees, fleet vehicles, regular vendors, or any vehicle that should always be admitted.
Blacklist (denied vehicles): Any plate on the blacklist generates an immediate alert when detected. Alerts are typically sent to a monitoring center, security staff, or integrated alarm system. Gates remain closed if integrated with access control. Blacklists are used for vehicles associated with theft, trespassing, or threats.
Hot list: Often confused with a blacklist, hot lists are dynamic databases of plates of interest that are updated in real time from external sources—stolen vehicle reports, warrant databases, or law enforcement shared intelligence. Commercial ALPR systems can subscribe to aggregated hot list services.
Unknown vehicle handling: Plates not on any list are either logged quietly (lowest security setting), flagged for review (medium setting), or treated as potential threats requiring verification (highest setting). The right configuration depends on whether your site has controlled access or open public access.
Tip: Watchlist hygiene matters. A blacklist with too many entries from years of accumulated one-time incidents generates alert fatigue. A whitelist that hasn't been updated creates access control gaps when employees change vehicles. Assign someone to maintain lists on a defined schedule.
Access Control Integration
ALPR becomes significantly more powerful when integrated with physical access control. Integration enables:
- Automatic gate/barrier operation: Gate controller receives a signal from ALPR software when a whitelisted plate is confirmed—no RFID card, keypad, or intercom required
- Multi-factor access: ALPR confirms the authorized vehicle is present; a second factor (badge tap, PIN) confirms the authorized person is driving it
- Time-restricted access: Whitelist entries can include time windows—a vendor vehicle is authorized on Tuesday mornings but generates an alert if detected on a Saturday night
- Unified event log: All vehicle entries, exits, and alerts are logged in a single system timeline alongside access control events
Common integration methods include Wiegand protocol (for legacy access control panels), REST API (for modern cloud-based systems), and OSDP for newer high-security installations. Confirm integration compatibility with your existing access control platform before committing to an LPR solution.
Deployment Geometry: Getting the Camera Position Right
Camera positioning is where many LPR installations fail. Key requirements:
Mounting height: 3–6 feet above ground level captures the plate at the right angle. Too high creates a steep downward angle that foreshortens plate characters.
Approach angle: Cameras should be positioned to capture vehicles approaching head-on or at no more than a 25–30 degree angle to the vehicle axis. Side angles significantly reduce read accuracy.
Lighting control: Backlit positions (camera looking toward the sun at sunrise or sunset) are problematic. Position cameras facing away from the primary sun angle, or use high-WDR sensors rated for this condition.
Single lane, single camera: Each lane of traffic requires its own dedicated LPR camera. A camera covering two lanes introduces read errors because the system can't reliably separate plates in adjacent lanes at the required capture resolution.
Read zone distance: Determine the expected vehicle speed at capture and position the camera to provide the correct read distance for accurate capture. 20–30 feet is typical for controlled entry points; up to 80 feet for freeway or open-road applications.
Realistic Performance Expectations
ALPR systems perform at 95–99% accuracy in vendor demonstrations, which are run under optimal conditions. Real-world deployments face:
- Dirty or damaged plates (common on construction vehicles)
- Temporary plates with less-retroreflective materials
- Obscured plates (trailers, equipment blocking rear plates)
- Non-standard plate mounting angles
- Weather extremes (snow on plates, rain at specific angles)
A well-deployed ALPR system at a controlled access point with good lighting typically achieves 92–97% accuracy in practice. This means 3–8% of vehicles require manual review or verification. For high-security applications, supplement ALPR with a general overview camera that captures the full vehicle and driver for events where plate reads fail.
Note: ALPR read data should be treated as strong evidence, not absolute confirmation. Plates can be obscured, swapped, or cloned. The read rate and the alert should prompt human verification, not automatic action without review.
LPR in Mobile Surveillance Deployments
VDS integrates LPR capability into mobile surveillance deployments for construction sites, utility facilities, and open-lot environments where fixed infrastructure isn't available. Mobile LPR captures all vehicle activity at site entrances, maintains a local watchlist for known threat vehicles, and generates real-time alerts to the VDS monitoring center when a flagged plate is detected.
This capability is particularly valuable for sites with recurring threat vehicles—for example, a construction site that has experienced theft and identified a suspect vehicle—where immediate alert on reappearance can enable law enforcement intercept.
Contact the VDS team to discuss how LPR capability integrates with your site's access and monitoring requirements.