ONVIF helps a viewing app find and understand a camera. RTSP helps it set up and control the camera’s live stream. In many camera systems, they work together.
Standards for cameras and viewing applications to work together.
The name originally expands to Open Network Video Interface Forum. ONVIF is the industry organization behind standardized interfaces for network security devices. Its specifications cover functions such as discovery, device information, media configuration and camera control.
Supported functions depend on the device, client and ONVIF profiles they implement. An ONVIF connection does not mean every camera feature is available in every app.
A protocol for setting up and controlling a live media session.
A viewer uses RTSP to negotiate a streaming session and request playback. Depending on the server and stream, it can also control actions such as pausing or ending that session.
RTSP is not a video codec. Formats such as H.264 or H.265 describe how video is encoded. RTP commonly carries the media, over transport arrangements such as UDP or TCP.
An industry forum and its family of interoperability specifications.
A protocol for controlling streaming sessions.
Main job
Help an app discover, inspect and configure compatible devices.
Set up, start and control media delivery.
Find cameras automatically?
Supports local discovery when the camera and network allow it.
Does not provide ONVIF-style discovery. You usually need the stream address.
Read device details?
Can expose device information and available media profiles.
Can describe a stream, but does not replace ONVIF device management.
Control camera features?
May support settings, events or pan/tilt/zoom, depending on the implemented features.
Controls the media session rather than general camera settings.
Work without the other?
A camera may answer ONVIF requests even when its live stream is unavailable.
A known RTSP address can work without using ONVIF discovery.
ONVIF features are organized into profiles; streaming-session behavior is defined by RTSP. Actual compatibility depends on both the camera and the client.
How they work together in Fortivia.
In Fortivia ONVIF Manager, a typical ONVIF camera connection follows these steps:
Find the camera
Click Scan. ONVIF discovery looks for compatible cameras on the local network.
Test and choose a stream
Enter the camera’s ONVIF credentials. The app requests device details, available media profiles and a stream address.
Open the live view
The player uses the returned RTSP address to establish a session and receive the video and available audio.
Direct RTSP takes a shorter route. Supply a compatible stream address and credentials yourself. The player connects to that address without first using ONVIF to discover the camera or select a media profile.
Different addresses for different jobs.
ONVIF service address
http://192.0.2.10:8083/onvif/device_service
An endpoint for device-service requests. It is not the address you normally enter into a media player to watch video.
RTSP stream address
rtsp://192.0.2.10:8554/live/main
An address used by a compatible player to establish the camera’s media session.
These are illustrative examples using a documentation IP address. Use your camera’s actual address, port and stream path; they vary by device. Enter credentials in the app’s credential fields.
Camera options
Major brands with ONVIF-capable cameras.
ONVIF is available on cameras for home use and professional installations. These representative models have manufacturer-documented ONVIF support. Product information was reviewed on ; regional availability, hardware revisions and supported firmware can vary.
Profiles G, S, T and M, as listed in the manufacturer’s product specifications.
PoE means Power over Ethernet: a compatible network cable connection can carry both power and data. These examples are not a Fortivia compatibility certification; the listed hardware models have not been verified with Fortivia ONVIF Manager.
Check the exact product before buying. Official ONVIF conformance is tied to a specific model and firmware version. Use the ONVIF Conformant Products database to verify a conformance claim. Manufacturer-documented support and official ONVIF conformance are different claims.
Battery-powered products can have different streaming limitations from plug-in models. For example, TP-Link documents model exclusions and special power requirements in its Tapo ONVIF/RTSP FAQ. Check the exact model rather than assuming every camera from a brand behaves alike.
Turn a compatible smartphone into a camera for everyday check-ins on a room, pet or workspace. If you already have a suitable spare phone, reusing it can reduce the need to buy dedicated camera hardware.
Enable the app’s supported ONVIF and RTSP functions to connect locally with Fortivia ONVIF Manager on Windows, Fortivia Camera Viewer on a compatible phone, or another compatible viewer. Fortivia IPCam also offers a separate browser-viewing workflow.
Low-cost refers to the opportunity to reuse existing hardware. Check current app licensing and access requirements; this does not imply every feature is free or that hosted remote access is included.
Set up your home camera
Install Fortivia IPCam on a compatible iPhone or Android phone and grant the required permissions.
Keep the camera phone powered and the app active. Position it securely for the view you need.
For local viewing, enable ONVIF and RTSP, configure ONVIF credentials and connect the phone and viewer to the same local network.
In Fortivia ONVIF Manager, scan for the phone, test its credentials, open the stream and save the device.
Choose whether to record on the camera phone or save separate clips in the viewing application.
Availability depends on the app build, platform, device and network. Supported ONVIF/RTSP functionality is not a claim of official ONVIF certification. Phone recordings and viewer recordings are separate copies.
Choose the hardware for the location. A reused phone can suit an indoor home setup. For an exposed outdoor location, choose equipment with an appropriate weather rating and mounting arrangement; dedicated cameras may also offer PoE and purpose-built night vision.
Common questions.
Why can the ONVIF test pass while the live stream fails?
Reading camera information and opening video are separate operations. A successful device-service test confirms that the tested ONVIF request worked; playback still needs a reachable stream address, accepted stream credentials, a running streaming server and a video format the player can decode.
Check the selected stream profile and RTSP address, confirm the camera remains active, and verify that the camera’s streaming port is reachable. The camera may use different credentials or ports for different services.
Can I use RTSP without ONVIF?
Yes, when the camera provides a compatible RTSP stream and you know its address. Direct RTSP still requires network access and any authentication the camera expects. It does not add ONVIF discovery or camera-management features.
Does ONVIF mean every camera feature will work?
No. Check the supported profiles and features on both sides. A camera offering video, audio and pan/tilt/zoom does not mean every viewer implements all three. Fortivia ONVIF Manager focuses on discovery, live viewing and local recording.
Why might a browser view work when ONVIF playback does not?
A browser viewer can use a different connection path from local ONVIF and RTSP. A working browser session does not establish that the camera’s ONVIF service or RTSP stream is available to a local client.
Are browser and ONVIF credentials always the same?
No. In Fortivia IPCam, configure and use the ONVIF credentials for the local camera connection. Browser-viewing credentials are a separate setting.
Put your camera connection to work.
Use Fortivia IPCam on a compatible phone and a compatible viewer on your local network. Choose the connection method supported by your camera and client.