ONVIF is a global standards protocol that allows IP cameras from different manufacturers to communicate with video management software. Profile S is the baseline standard for video streaming; Profile T adds H.265 encoding, metadata streaming, and HTTPS encryption. For license plate recognition applications, neither profile is strictly required — what matters is whether the camera can deliver a stable RTSP video stream at 720p or higher.
Key Takeaways
- ONVIF Profile S covers basic video streaming, PTZ control, and motion alarms — sufficient for most LPR applications
- ONVIF Profile T adds H.265/H.264 high profile, HTTPS, and rich metadata — useful for modern cameras but not required for LPR
- placa.ai connects via RTSP directly — ONVIF compliance is optional, not required
- If your camera has an RTSP stream URL, it can work with LPR software regardless of ONVIF profile
- Check your camera’s profile using the free ONVIF Device Manager tool
What Is ONVIF?
ONVIF (Open Network Video Interface Forum) is an open industry standard that defines how IP-based security devices — cameras, NVRs, access control systems — communicate with each other. Founded in 2008 by Axis, Bosch, and Sony, ONVIF allows a Hikvision camera to work with a Dahua NVR, or a Milestone VMS to manage cameras from any manufacturer, without proprietary bridges or adapters.
ONVIF defines a set of “profiles” — each profile is a collection of features that a compliant device must support. A camera claiming Profile S compliance must implement every feature in the Profile S specification. This gives buyers a guarantee of interoperability without having to test every device combination.
What Is ONVIF Profile S?
ONVIF Profile S is the foundational video streaming profile for IP cameras and video encoders. A Profile S-compliant camera supports: live video streaming via RTSP, video encoder configuration (resolution, frame rate, compression), PTZ (pan-tilt-zoom) control for PTZ cameras, relay output control for gate/alarm triggers, and basic metadata like motion detection events.
Profile S was introduced in 2011 and remains the most widely supported ONVIF profile. The majority of business-grade IP cameras manufactured after 2012 support Profile S.
What Is ONVIF Profile T?
ONVIF Profile T (“T” for “Advanced Streaming”) was introduced in 2018 to address the limitations of Profile S for modern deployments. Profile T-compliant cameras support everything in Profile S plus: H.265 (HEVC) and H.264 High Profile encoding for better compression at the same quality, HTTPS (TLS) encrypted video streaming for secure transmission, on-screen display (OSD) text overlay, event streaming with rich metadata (object classification, direction, speed), and motion region configuration.
Profile T is supported by cameras manufactured from approximately 2018 onward from major brands. Older cameras may be Profile S only.
Profile S vs. Profile T: Side-by-Side Comparison
| Feature | Profile S | Profile T |
|---|---|---|
| Live RTSP streaming | Yes | Yes |
| H.264 encoding | Baseline profile | High profile (better quality) |
| H.265 / HEVC encoding | No | Yes |
| HTTPS encrypted streams | No | Yes |
| PTZ control | Yes (for PTZ cameras) | Yes (enhanced) |
| Motion detection events | Basic | Rich metadata with object classification |
| Video analytics metadata | No | Yes |
| On-screen display (OSD) | No | Yes |
| Typical camera availability | 2012–present | 2018–present |
| Best for LPR? | Yes (sufficient) | Yes (preferred for modern setups) |
Which ONVIF Profile Matters for License Plate Recognition?
For LPR software like placa.ai, the ONVIF profile is secondary to the RTSP stream quality. What actually drives LPR accuracy is:
- Video resolution: 1080p or higher, regardless of profile
- Codec quality: H.264 High Profile (Profile T) or H.264 Baseline (Profile S) — higher profile = better image quality at the same bitrate, which helps OCR accuracy
- Frame rate: 25–30 fps for moving vehicles
- IR illumination: For nighttime reads
A Profile S camera at 4MP, 30fps, with proper IR illumination will outperform a Profile T camera at 1MP, 15fps for LPR accuracy. The profile matters less than the physical camera specifications.
The bottom line: If your camera has a working RTSP stream, it can connect to placa.ai. Profile S and Profile T both produce RTSP streams that placa.ai can consume. Profile T’s H.265 support saves bandwidth and storage but doesn’t directly improve recognition accuracy in most setups.
Does placa.ai Require a Specific ONVIF Profile?
No. placa.ai connects directly to your camera’s RTSP stream URL — it does not require ONVIF compliance at all. ONVIF is useful for automatic camera discovery on your network, but if you enter the RTSP URL manually, ONVIF compatibility is irrelevant. This means cameras with RTSP support but no ONVIF certification (some budget brands, older models) can still work with placa.ai.
How to Check Your Camera’s ONVIF Profile
Three methods:
Method 1: ONVIF Device Manager (Recommended)
- Download the free ONVIF Device Manager (available at sourceforge.net/projects/onvifdm)
- Run the tool — it automatically scans your local network for ONVIF-compliant cameras
- Select your camera from the list
- The device information panel shows which profiles the camera supports
Method 2: Camera Web Interface
- Type your camera’s IP address in a browser
- Log in with admin credentials
- Navigate to System → Device Info or Network → ONVIF
- Profile compliance is usually listed on the device information page
Method 3: Manufacturer Specification Sheet
Most camera manufacturers list ONVIF profile compliance in the product datasheet available on their website. Search for your camera model number plus “datasheet” or “spec sheet.”
When Profile Mismatches Cause LPR Failures
ONVIF profile mismatches typically cause problems when using ONVIF-based discovery (where the software finds and configures the camera automatically) rather than manual RTSP entry. Common scenarios:
- Software requires Profile T, camera only supports Profile S: Automatic discovery may fail or encrypted streams may not be available. Solution: Use manual RTSP URL entry instead of ONVIF auto-discovery.
- H.265-only software with an H.264-only camera: Some newer VMS software defaults to H.265 via Profile T. If the camera only supports H.264, you may need to force the software to use H.264. For placa.ai, this is not an issue — the system accepts both H.264 and H.265 RTSP streams.
- HTTPS-required software with a non-Profile-T camera: If the VMS requires encrypted RTSP (RTSPS), Profile S cameras (which don’t support HTTPS) cannot connect. placa.ai uses standard RTSP by default, so this is typically not a concern.
Frequently Asked Questions
My camera says it’s ONVIF compliant but has no profile listed. What does that mean?
Some manufacturers claim “ONVIF compatible” without full profile certification. This means the camera implements parts of the ONVIF protocol but has not been certified by the ONVIF organization. In practice, these cameras often work fine with RTSP-based LPR software via manual stream URL entry, but may behave inconsistently with ONVIF auto-discovery features.
Does ONVIF Profile T improve LPR accuracy?
Not directly. Profile T enables H.265 encoding which preserves more image detail at a given bitrate, potentially improving plate readability at the margin. However, the bigger factors are resolution (4MP vs 1080p), frame rate, and lighting. Profile T by itself does not meaningfully change LPR accuracy compared to Profile S if both cameras are otherwise equivalent.
Can I use a camera that supports only ONVIF Profile G (recording) for LPR?
Profile G is for NVR/DVR recording devices, not for live streaming cameras. A camera with only Profile G would be unusual — most cameras supporting Profile G also support Profile S. If your camera is Profile G only, check whether it has an RTSP stream (most do) and use manual RTSP URL entry in placa.ai.
Is RTSP or ONVIF more reliable for connecting cameras to LPR software?
RTSP direct connection is generally more reliable and has fewer compatibility issues than ONVIF auto-discovery. ONVIF adds a layer of abstraction that can fail when implementations vary between manufacturers. For LPR deployments, using the direct RTSP URL is the recommended approach regardless of camera ONVIF profile.
What is ONVIF Profile A and Profile C?
Profile A covers access control (door controllers, card readers, biometric systems) and Profile C covers door control. Neither is relevant for IP camera video streaming or LPR. LPR software connects to Profile S or Profile T cameras only — or directly via RTSP without using ONVIF at all.
Check if your cameras work with placa.ai
If your camera has an RTSP stream — Profile S, Profile T, or uncertified ONVIF — it very likely works. Connect it to placa.ai in under 10 minutes with a free trial.