Note: The version of ffmpeg-static follows SemVer. When releasing new versions, we do not consider breaking changes in ffmpeg itself, but only the JS interface (see below). For example, ffmpeg-static@4.5.0 might download ffmpeg 5.0. To prevent an ffmpeg-static upgrade downloading backwards-incompatible ffmpeg versions, use a strict version range for it or use a lockfile.
Note: During installation, it will download the appropriate ffmpeg binary from the b6.1.1 GitHub release. Use and distribution of the binary releases of ffmpeg are covered by their respective license.
Custom binaries url
By default, the ffmpeg binary will get downloaded from https://github.com/eugeneware/ffmpeg-static/releases/download. To customise this, e.g. when using a mirror, set the FFMPEG_BINARIES_URL environment variable.
Because ffmpeg-static will download a binary specific to the OS/platform, you need to purge node_modules before (re-)packaging your app for a different OS/platform (read more in #35).
Example Usage
Returns the path of a statically linked ffmpeg binary on the local filesystem.
This npm package includes statically linked binaries that are produced by the following individuals. Please consider supporting and donating to them who have been providing quality binary builds for many years: