Eight package repositories, one discouraged source build, and a config script for packagers
ZoneMinder is a free, open source Closed-circuit television software application developed for Linux which supports IP, USB and Analog cameras.
At a glance
- What is it?
- ZoneMinder is a GPL-2.0 suite for capture, analysis, recording and monitoring of CCTV cameras on a Linux host, built around the Video For Linux interface. The project steers you to distro packages, treats source builds as a last resort, and hands packagers a script for the defaults that cmake and autotools cannot set.
- Who is it for?
- ZoneMinder fits a Linux host with V4L cameras and a distro that already has a package repository, or a packager willing to build one. It does not fit a Windows machine, a camera model you need a compatibility guarantee for.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ZoneMinder/zoneminder5,991 ★ · +54
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| ZoneMinder/zoneminder | 5.9k | 6k |
54 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Eight package repositories carry the install, and source builds are the fallback it warns about
ZoneMinder puts package repositories first and calls them the recommended installation method. The list is long enough to matter, because it names a source for every major Linux family:
Ubuntu via Isaac Connor's PPA
Debian from their default repository
RHEL/CentOS and clones via RPM Fusion
Fedora via RPM Fusion
OpenSuse via third party repository
Mageia from their default repository
Arch via the AUR
Gentoo via Portage OverlaysTwo distros share one upstream project, RPM Fusion, and two more ride their own default repositories, so the packaging effort is spread thin and uneven by design. When no repository hosts packages for your distro, the instruction is not to compile the tree yourself but to build a package for your distribution, adapting another distro's packaging instructions, since each distro differs but not by much. Distro specific steps live at the ReadTheDocs site, where all of the project documentation now sits.
The source build is described as a trap: manual init scripts, hand installed extras, stale files
The section on compiling from source is titled as discouraged, and the reasons it gives concern your filesystem rather than the compiler. Historically the route was the traditional configure, make, make install sequence, with every dependency resolved and installed beforehand. After the build you copied the init and logrotate scripts into place yourself, and you installed the optional packages jscalendar and Cambozola by hand. Uninstalls could leave stale files behind that caused trouble on the next upgrade, and because every step was manual, upgrading meant repeating all of them. The repository top level still shows what a build consumes:
CMakeLists.txt
cmake/
utils/zmeditconfigdata.sh
zm.conf.in
zmconfgen.pl.in
zmlinkcontent.sh.in
zoneminder-config.cmakeThe project is explicit that turning ZoneMinder into a package is no harder than building it from source, and someone who has compiled the tree before will find the packaging steps easier. That work belongs in a separate environment built for development, a virtual machine, Docker or mock, and never on the production server that will run the cameras. Building from source is what the package instructions are built around, not an equal alternative to them.
zmeditconfigdata.sh edits ConfigData.pm before cmake or configure ever runs
Packagers hit a wall early, because many ZoneMinder configuration variable defaults cannot be set at build time through autotools or cmake. The answer is a shell script that lives in utils/, called zmeditconfigdata.sh, which manipulates any variable stored in ConfigData.pm without patching the source. The worked example in the documentation turns on Cambozola support, which ships switched off by default, by naming the variable and the value:
./utils/zmeditconfigdata.sh ZM_OPT_CAMBOZOLA yesTiming is where this bites. The script is meant to be called from the root build folder before you run cmake or configure, so a packaging script has to call it before either of those runs. The rest of the configuration machinery is visible nearby, with conf.d/ sitting next to the zm.conf.in and zmconfgen.pl.in templates, and the script is the only lever the project hands you for values those files do not already set. It also solves a narrower problem than the name suggests: it edits values in a configuration module, not build logic, so anything needing a new compiler flag or dependency still needs a real packaging recipe around it.
The Dockerfile runs the ZM webserver here, and its documentation is admitted to be unfinished
Official images for amd64 and arm64 are published on Docker Hub as zoneminder/zoneminder and on the GitHub Container Registry as ghcr.io/zoneminder/zoneminder, and CI rebuilds them every day from the zmrepo packages. The latest tag follows the newest release, tags such as 1.38 and 1.38.6 pin a series or an exact version, dev carries nightly builds of master, and each tag has an -es variant with the event server. The ZoneMinder/zmdockerfiles repository holds a compose file that runs ZoneMinder with MariaDB, and Docker issues belong there rather than in the main tracker. The top level carries .dockerignore and .gitmodules next to CMakeLists.txt and distros/. Build checks and the documentation build are configured in the same tree through .cirrus.yml, .gitlab-ci.yml and .readthedocs.yaml, so the automation lives here even though the image does not.
Step 3 of the pull request flow is optional and preferred at the same time
Contributions follow a written procedure, and it is more prescriptive than most projects bother with. Read the posting rules before opening an issue in the tracker, and note the split the project asks for: bugs and security issues go to GitHub Issues following the issue template, while feature requests and questions belong in the user forum or the Slack channel. The branch flow itself is three commands:
git checkout -b 456-my-new-feature
git commit -am 'Added some feature'
git push origin 456-my-new-featureCreating the feature branch is the step marked optional and preferred simultaneously, which reads as advice rather than a gate. The project also asks you to commit early and often instead of bunching changes into one commit. With master as the default branch, a contributor working from it is building on whatever that branch holds that day, which is one more reason the packaging notes tell you to start from an official release when a snapshot misbehaves.
V4L is the design center, and IP camera support is promised as most, not all
ZoneMinder describes itself as an integrated set of applications covering capture, analysis, recording and monitoring of any CCTV or security camera attached to a Linux machine. The interface it is designed around is Video For Linux, so the target is any distribution exposing V4L. Its tested history is spelled out as BTTV capture cards, various USB cameras, and support for most IP network cameras. That last phrase carries the weight: most, so anyone who needs a guarantee for a specific camera has to test it. The repository top level hints at the shape of the code rather than answering compatibility: src/, web/, onvif/, db/, conf.d/, dep/, scripts/, tools/, tests/, docs/ and distros/ all sit side by side, and what each one contains is left to the documentation site.
Release names track the churn, from 1.36.38 in February 2026 to 1.38.4 in August
The tag history shows a steady cadence under colorfully named releases. 1.38.4 shipped as Seek and Destroy 1.38.4 on August 11, 2026, and 1.38.5 and 1.38.6 followed under the same name on October 5, 2026. The default branch, master, last received a push on November 2, 2026, so the code on master is newer than anything a package repository can install. That gap is the practical reason the packaging advice keeps repeating itself: a snapshot can carry changes no release has, which is exactly why the project asks you to build an official release first when a snapshot fails, so you can separate a broken build process from a broken branch. CHANGELOG.md and version.txt in the tree are where the detail sits, and the release names are the only friendly labels in that history. Around them sit the files a project this size accumulates: SECURITY.md for reports, CONTRIBUTING.md and code_of_conduct.md for the rules, funding.json, and two assistant instruction files, AGENTS.md and CLAUDE.md. The README header points at a Slack invite and a Discord server, so the conversation happens off the issue tracker as well as on it.
Editorial conclusion
ZoneMinder fits a Linux host with V4L cameras and a distro that already has a package repository, or a packager willing to build one. It does not fit a Windows machine, a camera model you need a compatibility guarantee for. Before installing, read the packaging notes for your distro, keep in mind that master took a push on November 2, 2026 while the newest tag is 1.38.6 from October 5, 2026, and confirm your own hardware because the project promises only most IP cameras.
Frequently asked questions
How do I install ZoneMinder on my machine?
ZoneMinder calls package repositories the recommended method and names a source for Ubuntu, Debian, RHEL/CentOS, Fedora, OpenSuse, Mageia, Arch and Gentoo. If your distro has none of them, the project asks you to build a package for your distribution rather than compile from source.
Where do I get ZoneMinder packages for Ubuntu?
Ubuntu packages come from Isaac Connor's PPA. The rest of the list runs through RPM Fusion for RHEL/CentOS and Fedora, the default repositories for Debian and Mageia, a third party repository for OpenSuse, the AUR for Arch, and Portage Overlays for Gentoo.
How do I reach the ZoneMinder web interface?
The README sends all documentation to zoneminder.readthedocs.org. For the Docker compose setup from the zmdockerfiles repository, it says to open http://localhost:8080/zm.
Which IP cameras are compatible with ZoneMinder?
ZoneMinder says it supports most IP network cameras, alongside BTTV capture cards and various USB cameras, and it is designed for distributions exposing the Video For Linux interface.
Is ZoneMinder free to run?
ZoneMinder is free and open source software released under the GPL-2.0 license, built for Linux machines and distributed through distro package repositories. Releases carry names such as Seek and Destroy 1.38.6, tagged on October 5, 2026.
Does ZoneMinder run on Windows as an NVR?
The project is designed to run on Linux distributions that support the Video For Linux interface. Every install source it names belongs to a Linux distro, so a Windows host sits outside what the documentation covers.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/zoneminder-zoneminder)Star history chart for your README
[](https://hysenlabs.com/projects/zoneminder-zoneminder)Was this useful?