LPR Cameras Are a Useful Tool -- Not a Gate Policy
License plate recognition can speed up access, improve your logs, and flag suspicious vehicles. But any facility that relies on a plate read alone to open the gate is vulnerable in ways that are easy to exploit and hard to detect. Here is what LPR can and cannot do -- and how to deploy it responsibly.
LPR systems identify a vehicle by its license plate and can be configured to trigger gate access when a plate matches an approved list. The problem is that a plate read confirms a plate number -- not a person, not a vehicle, and not a legitimate right of entry. Spoofed plates, stolen plates, ghost plates, and physically altered plates can all defeat or confuse an LPR system. LPR should assist your access process, not replace the human or credential layer that confirms who is actually there.
Key Takeaways
- 1An LPR system reads a plate number -- it cannot verify that the vehicle matches the plate, or that the person driving has a right to be there
- 2Plate spoofing is straightforward: a duplicate plate placed on a different vehicle will pass an LPR whitelist without triggering any alert
- 3Stolen plates present a silent risk -- a tenant's plate stolen and placed on another vehicle grants the thief access until the tenant reports it
- 4Ghost plates, temp tags, and obscured or damaged plates can cause false negatives -- legitimate tenants denied entry -- or unpredictable reads
- 5LPR works best as a log and assist layer: it tells staff who is arriving, speeds up identification, and flags unrecognized plates -- the access decision should still involve a second factor
License plate recognition has become a standard feature in self-storage and gated facility access systems. The pitch is straightforward: enroll a tenant's plate, and the gate opens when they arrive. No fob, no PIN, no intercom. Frictionless access.
The problem is that frictionless access and secure access are not the same thing. An LPR camera reads a plate number. It does not know whether the vehicle is the one that plate belongs to. It does not know who is driving. It does not know whether the plate was borrowed, cloned, or stolen. If your gate opens on a plate match alone, you have built your access policy on a number that anyone motivated enough can replicate.
Spoofed plates: the easiest attack on an LPR-only gate
Plate spoofing means placing a duplicate of a legitimate plate on a different vehicle. Custom plate blanks are available online. A motivated person who knows a tenant's plate number -- from seeing the vehicle on the property, from a photo, or from any other observation -- can have a copy made and drive up to your gate with a plate your LPR system will recognize and approve.
The LPR system sees the number it is looking for and opens the gate. Nothing in the read tells it that the plate is on a different vehicle than the one it has seen before. Unless you have a camera capturing the vehicle make and color alongside the plate -- and a person comparing them -- the spoof goes undetected.
Stolen plates: a risk that starts outside your facility
Plate theft is common and often goes unreported for days. A tenant parks their vehicle somewhere in the city, someone removes one or both plates, and those plates get used on a different vehicle. If the thief also knows where the tenant stores -- and that the facility uses LPR access -- they now have a working key to your gate.
The tenant may not notice the plates are missing for several days if the vehicle is not used regularly. During that window, their plate is active on your approved list and a different vehicle is using it. By the time the theft is reported and the plate is flagged, the access may have already been used.
There is no technical fix for this at the LPR layer. It is a structural limitation of using a plate number as a trust signal. The plate number tells you what the plate says. It cannot tell you what the plate is attached to or whether the plate is where it is supposed to be.
Ghost plates and temp tags: legitimate vehicles your system will not recognize
Ghost plates are dealer plates or temporary registration tags used on vehicles that have not yet been permanently registered. They are common in states where buyers drive a vehicle for 30 to 90 days before a permanent plate is issued. A tenant who has just bought a new vehicle may show up with a paper temp tag in the rear window and a plate frame from the dealer -- nothing that looks like the aluminum plate your LPR camera was trained to read.
LPR systems that rely on optical character recognition perform poorly on paper temp tags. The font, contrast, and reflective properties are different from a standard plate. Depending on weather conditions and the angle of the camera, a temp tag may produce an inconsistent read, a partial read, or no read at all.
Physical plate damage creates a similar problem in the other direction. A plate that has been bent, faded by sun exposure, partially covered by a trailer hitch receiver, or obscured by a bike rack may produce a read that is close to the enrolled plate but not an exact match. Depending on how the confidence threshold is set, this can result in a legitimate tenant being denied entry -- or, if the threshold is set permissively, in partial plate matches being accepted when they should not be.
Deliberate plate obfuscation: a problem from another context that affects yours
Speed camera and toll evasion has created a market for products specifically designed to defeat optical plate recognition: tinted plate covers that reduce reflectivity, sprays that claim to wash out under flash, frames that partially obscure the plate edges, and custom modifications that alter the spacing or shape of individual characters to confuse OCR engines.
These modifications are often illegal -- most states prohibit covers or alterations that make a plate unreadable -- but they are widespread. The same vehicle that uses a tinted cover to avoid a toll camera will show up at your gate and your LPR system will struggle with it for exactly the same reason.
From your facility's perspective, this creates two problems. An enrolled tenant with an obfuscated plate may fail to trigger a valid read and get stuck at the gate. An unknown vehicle with an obfuscated plate may produce an inconsistent read that partially matches an enrolled plate, depending on your system's matching logic. Neither outcome is one you want to handle reactively.
How LPR should fit into your access process
None of the above means LPR is not worth deploying. It is a genuinely useful layer in a multi-factor access system. The mistake is positioning it as the decision point rather than an assist.
Used well, LPR does several things that improve your operation. It logs every plate that arrives at the gate with a timestamp -- useful for incident investigation and for verifying when a specific vehicle was on site. It can push an alert to staff when an unrecognized plate attempts entry, prompting a closer look rather than an automatic denial. It can surface a tenant's name and unit number on the office screen when their vehicle is recognized, so the staff member at the intercom already has context before the tenant says a word.
What it should not do is open the gate on its own. The access decision -- the moment the gate opens -- should require a second factor. A PIN entered at the keypad, a credential on a mobile app, a confirmation through the intercom, or a visual confirmation by a staff member. LPR brings the relevant information to the surface quickly. A human or a verified second credential makes the call.
This is not a theoretical concern -- it is a policy decision that should be made deliberately when the system is designed, not discovered after an incident makes the gap visible.
LPR tells you what the plate says. It cannot tell you whether the right person is behind the wheel.
Your Checklist
- Review whether your current LPR configuration opens the gate on a plate match alone -- if yes, add a second factor requirement
- Confirm your LPR camera is mounted at plate height, not at general surveillance height
- Verify that your system logs all entry attempts including unmatched plates, with captured images
- Deploy a separate wide-angle camera for gate area coverage -- do not use the LPR camera for both jobs
- Add a tenant communication step: when a plate read fails, the tenant has a clear fallback (intercom, PIN, app) and does not need to call the office
- Review your confidence threshold setting with your installer -- confirm it is set to match full plate reads, not partial ones
Common Mistakes to Avoid
Configuring LPR as a standalone gate trigger with no second factor
A plate whitelist that opens the gate without a PIN, credential, or staff confirmation is vulnerable to spoofing, stolen plates, and partial-match errors. LPR should surface information and assist verification -- not complete it unilaterally.
Setting the confidence threshold too low to reduce false negatives
Lowering the match threshold to reduce instances of legitimate tenants being denied entry also increases the chance that a partial or near-matching plate triggers access. The right fix for frequent false negatives is camera position, lighting, and read distance -- not a looser match threshold.
Not logging plates that fail to match
Every plate that arrives at your gate -- matched or unmatched -- should be logged with a timestamp and a captured image. Unmatched plates are often where interesting activity hides. A vehicle that attempts entry repeatedly on unmatched plates warrants attention before an incident makes the pattern obvious.
Positioning the LPR camera where it also needs to serve as a general area camera
LPR cameras have a narrow field of view optimized for plate capture at a specific read distance. Using the same camera to cover the gate area generally produces a plate read that is acceptable and an area image that is not. Deploy a dedicated LPR camera for plate reads and a separate wide-angle camera for area coverage at the entry.
Frequently Asked Questions
What is the right camera position for reliable LPR reads at a gate?
LPR cameras should be mounted at roughly bumper-to-plate height -- typically 2.5 to 4 feet off the ground -- and angled slightly downward toward the plate. The read distance should match the camera's specified capture range, usually between 10 and 30 feet depending on the lens. Vehicles should be traveling slowly or stopped at the read point. High-angle or wide-angle positions produce inconsistent reads and should be reserved for general surveillance coverage, not plate capture.
Can LPR work reliably at night?
Yes, with the right hardware. LPR cameras designed for low-light use incorporate IR illuminators tuned to the wavelength that makes plate reflectors glow clearly on camera. Standard security cameras with general IR do not produce the same plate contrast. If your LPR reads are inconsistent at night, the camera is either not spec'd for low-light plate capture or the IR is not positioned to illuminate the plate angle correctly.
Should I still enroll tenant plates in my system even if LPR is not the gate trigger?
Yes. Enrolling plates is still valuable even when LPR is not the access decision point. It gives your access logs vehicle-level context alongside credential-level data, enables the system to surface tenant information on staff screens when a recognized vehicle arrives, and creates a record that is useful for incident investigation. The enrollment is worth doing independent of whether the plate read opens the gate.
What should staff do when LPR flags an unrecognized plate?
Treat it as a prompt to verify through another channel -- the intercom, a credential check, or a visual confirmation. An unrecognized plate does not mean the person should be denied entry; it means the plate alone is not sufficient to grant it. The person may be a new tenant whose plate has not been enrolled, a tenant with a recently changed plate, or someone visiting a tenant. The flag is a cue to ask, not an automatic denial.
Thinking about adding LPR to your facility -- or reviewing how your current system is configured?
We design LPR deployments that work as part of a layered access strategy, not as a replacement for one. Licensed in NY and NJ.