Prebuilt Binaries (No Python Required)
To use the ONVIF CLI without installing Python or additional dependencies, download a prebuilt binary distribution for your platform from the GitHub Releases page.
Each release includes platform-specific archives containing the ONVIF CLI executable and its required runtime files. Alternatively, download the latest archive for your platform and architecture from the table below.
| Platform | Architecture | Download |
|---|---|---|
| Linux | AMD64 (64-bit) | onvif-linux-amd64.tar.gz |
| Linux | ARM64 (aarch64) | onvif-linux-arm64.tar.gz |
| Windows | x64 (64-bit) | onvif-windows-win64.zip |
| Windows | x86 (32-bit) | onvif-windows-win32.zip |
| Windows | ARM64 | onvif-windows-arm64.zip |
| macOS | Intel (AMD64) | onvif-macos-amd64.tar.gz |
| macOS | Apple Silicon (ARM64) | onvif-macos-arm64.tar.gz |
Installation
Linux
- Download the TAR.GZ archive matching your Linux architecture.
- Extract the archive into a permanent location.
- Create a symbolic link in
~/.local/binso the executable can be invoked from any directory.
For example, for Linux AMD64, assuming the archive is in ~/Downloads:
mkdir -p ~/.local/opt ~/.local/bin
unzip ~/Downloads/onvif-linux-amd64.tar.gz -d ~/.local/opt
chmod +x ~/.local/opt/onvif/onvif
ln -sf ~/.local/opt/onvif/onvif ~/.local/bin/onvif
Ensure ~/.local/bin is included in your PATH. If necessary, add the following to ~/.bashrc or ~/.zshrc:
Reload your shell configuration or open a new terminal, then verify:
Replace onvif-linux-amd64.tar.gz with the archive matching your system.
Windows
- Download the ZIP archive matching your Windows architecture.
- Extract the archive. It contains an
onvifdirectory with the executable and its bundled dependencies. - Move the extracted
onvifdirectory to a permanent location, such as%LOCALAPPDATA%\Programs\ONVIF. - Add that directory to your user
PATHenvironment variable.
To configure PATH, open Edit environment variables for your account, select Path, click New, and enter:
Open a new terminal and verify the installation:
You can now invoke onvif from any working directory in PowerShell or Command Prompt.
macOS
- Download the TAR.GZ archive matching your Mac's processor: Intel or Apple Silicon.
- Extract the archive into a permanent location.
- Create a symbolic link in
~/.local/bin.
For example, for Apple Silicon:
mkdir -p ~/.local/opt ~/.local/bin
unzip ~/Downloads/onvif-macos-arm64.tar.gz -d ~/.local/opt
chmod +x ~/.local/opt/onvif/onvif
ln -sf ~/.local/opt/onvif/onvif ~/.local/bin/onvif
Ensure ~/.local/bin is included in your PATH. If necessary, add this line to ~/.zshrc:
Open a new terminal and verify:
For Intel Macs, use onvif-macos-amd64.tar.gz instead.
Understanding the Distribution
Info
The LICENSE and NOTICE files provide licensing and attribution information for the distribution.
The prebuilt binaries use PyInstaller's --onedir mode. Each archive contains the executable, bundled runtime dependencies, and project license documents.
The extracted directory has the following structure:
onvif/
├── onvif # Linux and macOS
├── onvif.exe # Windows only
├── LICENSE
├── NOTICE
└── _internal/
└── ... # Bundled runtime and dependencies
The _internal directory contains the Python runtime components, third-party dependencies, and bundled resources required by the executable.
Keep the executable and _internal directory together. Do not delete, rename, or move _internal independently. The application may fail to start or operate correctly if its bundled files are missing.