FFmpeg Compliance

zshot ships a binary build of FFmpeg, which is licensed under the LGPL. Per those licenses, we make available — for every published zshot release — the exact upstream FFmpeg source we built against, and the binary tarballs produced by our build.

Latest release

The table below lists the FFmpeg version bundled with the latest zshot release, along with direct links to the corresponding source tarball and to the platform-specific binary tarballs we install into the application.

For older zshot releases, the corresponding FFmpeg source and binary tarball URLs are emitted by the --open-source-licenses flag of that release.

How we build FFmpeg

Our FFmpeg binaries are produced by an open-source build script maintained alongside zshot. The script:

1. Downloads the official FFmpeg source release archive (the same file linked under “Source” in the table above).
2. Builds in a clean container/VM using a deterministic dependency list.
3. Publishes the resulting binaries plus an unmodified copy of the source archive to the same public bucket linked above.

If you want to reproduce, audit, or rebuild from source, the source tarball is the canonical input — fetch it, follow FFmpeg’s standard ./configure && make flow, using the configure flags output by the --open-source-licenses flag of zshot

Substituting your own FFmpeg

The LGPL right to relink against your own FFmpeg build is real and exercised. Before each release is published, we replace the bundled FFmpeg libraries in the shipped macOS and Linux packages with a separately compiled build and confirm zshot still launches and links against it. Replace the libav*/libsw* libraries that ship inside the package with your own matching build to use it.