ONVIF Device Manager (ODM) is a free, open-source Windows utility for discovering compatible network cameras, checking their ONVIF information and viewing supported live streams. It can help you find the RTSP address needed by another video application.
Start with the original SourceForge project, connect your computer to the camera network, and use the device's authorized ONVIF credentials. ODM is an independent project; it is not an ONVIF organization certification tool or a guarantee that every camera will work.
Sources checked November 14, 2026. This guide covers the classic SourceForge Windows project and documented workflows; it does not claim a hands-on device or installer test.
Download and version boundaries
Use the original ODM project on SourceForge and open Files. At the time checked, the listed installer was odm-v2.2.250r.msi, with a file modification date of January 11, 2024. A file timestamp is not a release history or a promise of ongoing support. The project was registered in 2010, and its public source tree contains much older work.
The historical Synesis user guide describes a .NET Framework 4 application from the Windows XP/Windows 7 era. Those historical requirements are useful context, not advice to install an unsupported operating system. We could not establish a current Windows 11 certification or support matrix for this classic build. Use your organization’s supported Windows environment and check whether the installer can run there.
| Question | Practical answer |
|---|---|
| Is this an official ONVIF organization download? | No. The linked SourceForge project is independently maintained. ONVIF publishes standards and its own conformance information. |
| Does it have a native Mac or Linux installer? | The original project lists Windows. Similarly named Linux projects and newer forks are separate software with separate requirements. |
| Will all ONVIF devices work? | Discovery, authentication, media and optional settings can differ by device, firmware and supported services. |
| Can it display H.265? | Milestone’s documentation warns that the classic ODM does not support H.265 or FIPS 140-2. Start with a permitted H.264 profile for video diagnosis. |
Check a product and its firmware against the ONVIF conformance database when formal conformance matters. A successful ODM connection is a useful functional observation, not a conformance certificate. Conversely, an ODM failure does not prove a device is nonconformant.
Prepare and install
Before starting, collect the camera’s local IP address if known, its model, an authorized local username and password, and any separate ONVIF account details. A mobile app’s cloud account may be unrelated to the device login.
- Connect the computer and camera to the same trusted LAN. Check camera power and the Ethernet link, or confirm its Wi-Fi connection in the router.
- In the camera or recorder’s own interface, complete initial activation and enable ONVIF if the model requires it. Follow that manufacturer’s instructions for creating an ONVIF user.
- Download the MSI from the project’s Files page, check that the filename matches the intended package, and run the installer. Read any license and Windows permission prompts yourself.
- If a .NET dependency is missing, use Microsoft’s supported installation guidance for your Windows version. An old guide’s dependency number does not justify downloading a runtime from a random mirror.
- Launch ODM. If Windows asks about network access, use an application-specific permission for the trusted network under your IT policy. Keep the firewall active.
- Find the deviceLocal discovery or a known ONVIF service address.
- AuthenticateAn account permitted to access the device's ONVIF service.
- Read the streamA media profile and the RTSP URI it returns.
Discover or add a camera
On startup, ODM searches the local network and lists discovered devices on the left. Select Refresh after checking the connection if the list stays empty. Identify the right device by its model, address and identification information before changing anything.
Discovery traffic is normally limited to the local network segment. Being on the same Internet connection does not ensure that guest Wi-Fi, a VPN, VLANs or a recorder’s private PoE network will pass it. For example, a laptop on the router LAN may see the NVR while cameras on its internal PoE ports remain inaccessible.
If you know the ONVIF service address, use Add and enter its URI. The Milestone example documents this manual-add workflow. A common address shape is:
http://192.168.1.50:80/onvif/device_serviceThis is an illustration, not a universal camera endpoint. Replace the host, service port and path with the values documented for your device. An ONVIF service URI is different from an RTSP video URL. Adding it manually will not create a route into an isolated network or enable ONVIF on a device that lacks it.
For port roles and network checks, use our companion RTSP and ONVIF ports guide.
Sign in with the right credentials
Enter the authorized device/ONVIF username and password in the login area above the device list and use Log in. Reselect the device if necessary, then open its information and media pages.
A device appearing in the list does not mean authentication succeeded. Discovery may reveal a name and address before access to video or settings is granted. Where a manufacturer requires a separate ONVIF user, use that account rather than guessing the camera’s cloud password.
If login fails, verify one known credential in the manufacturer’s interface, check the ONVIF user’s permissions, and compare the device clock with the computer clock. Avoid repeated guesses, which can trigger account lockout. Use the manufacturer’s recovery procedure if the password is lost; ODM is not a password-recovery tool.
Find the RTSP stream URL
- Select the authenticated device and the desired video source or media profile, if multiple entries are available.
- Open Live video. In the classic interface, look for the RTSP URI associated with the selected stream. The historical guide documents an RTSP link in this view.
- Copy the complete returned URI into the network-stream field of your intended player or NVR. Supply the authorized username and password through that application’s login prompt where possible.
- Confirm the picture is from the expected camera and profile. A main stream and substream can use different addresses, resolution and bitrate.
An RTSP URL may look like rtsp://192.168.1.50:554/example-stream, but do not substitute that sample path for the address your device returns. A URI beginning with http:// and ending with device_service is a control endpoint, not the video stream to paste into an RTSP player.
If the returned URI contains a private recorder-side address that the computer cannot reach, copying it elsewhere will not fix connectivity. Reach the camera through the supported network path first. Keep stream addresses containing credentials out of screenshots, public posts and shared logs.
Check live video and settings
Use a supported H.264 stream as an initial video check. If the device information loads but the picture does not, treat media decoding and stream reachability as separate checks from authentication. Trying a lower-bitrate H.264 substream can help distinguish a stream problem from a load problem, provided that profile is available.
ODM may expose device information, time, network, imaging, profiles, events and PTZ controls. Availability depends on what the device implements and what your account can access. Do not assume a missing page means the camera lacks the equivalent function in its own software.
Read existing values before making changes. Changing an IP address or media profile may interrupt a recorder using the old settings. Use the manufacturer utility for activation, firmware and recovery tasks unless the manufacturer explicitly documents an ODM workflow. For Hikvision network setup, see SADP and HiTools Delivery.
Troubleshoot common problems
| Symptom | Check in this order |
|---|---|
| No devices appear | Power and link → correct LAN adapter → guest/VLAN/PoE isolation → ONVIF enabled → application firewall permission → Refresh. |
| Known IP opens in a browser, but discovery fails | Confirm the device’s ONVIF service and documented port. Try its service URI with Add; web access alone does not establish ONVIF availability. |
| Device appears, but access is unauthorized | Confirm the local or separate ONVIF account, its permissions and clock settings. Stop repeated login attempts. |
| Information loads, but live video is black | Check the selected profile and returned host/port. Try a supported H.264 stream in a suitable player; the classic client’s codec limitations can matter. |
| Camera works in a phone app only | Confirm that the model exposes ONVIF or RTSP locally. A cloud-only camera cannot gain those services by installing ODM. |
| Several adapters or a VPN are active | Confirm routing to the camera LAN with your administrator. Use the intended network connection rather than disabling network protections. |
| A setting is absent or fails to save | Check account rights and the manufacturer’s supported ONVIF services. Make the change through the device’s documented interface if needed. |
Frequently asked questions
Is ONVIF Device Manager free?
The original SourceForge project is open source and lists GPLv2. Use the actual project download rather than a website asking you to pay to unlock a repackaged installer.
Does it record video or replace an NVR?
Use it for discovery, inspection and supported live viewing. Milestone documents the classic client as a live-stream tool without capturing and saving that stream. Use a supported recorder or VMS for retention, scheduled recording and normal playback.
Can I find cameras remotely with it?
Local discovery does not search a cloud account. Remote access needs an authorized network route and compatible device services; an IP address alone is insufficient. Do not publish camera service ports to make a local discovery test work.
Why do newer ODM downloads have different features?
Independent forks can change the decoder, interface or platform support. This guide describes the original SourceForge package. Features advertised by another repository should be checked against that repository’s own release and documentation.
For recording-space planning after checking your media settings, use the CCTV storage calculator with the recorded stream’s average bitrate.
Sources and next steps
- Original ODM project and current file listing: project identity, platform, license and observed installer.
- Original project source tree: historical project context.
- Synesis ONVIF Device Manager User Guide, hosted by a camera supplier: historical system requirements and interface reference. It is not a current Windows support statement.
- Milestone Open Network Bridge documentation: manual service-URI entry and classic client limitations.
- ONVIF conformant products: formal product and firmware conformance checks.
Continue with RTSP and ONVIF ports for connection details, or all technical guides for device-specific help.