Your output may look different than mine, but it will be a somewhat similar list of directories. usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/john/.local/bin:/home/john/bin

'PATH' is a variable in your environment set to a list of colon seperated directories the shell uses to locate binaries.

To globally install it I need to move the binary into my shell's path. Or using the absolute path to the binary. Without any further steps I can start using ffmpeg with my relative path to the binary.

Please read readme.txt! (hit 'q' to exit out of 'less') $ less ffmpeg-git-20180203-amd64-static/readme.txt $ ls ffmpeg-git-20180203-amd64-staticįfmpeg ffprobe GPLv3.txt manpages model qt-faststart readme.txt Now I have the directory 'ffmpeg-git-20180203-amd64-static'. You may have to run it twice once to uncompress and again to untar the directory. Note: If you need to do this on Windows, use 7-Zip to unpack it. With the build and the build's md5 hash downloaded you can check its integrity. Otherwise you can use the binary's absolute path. There's no installation necessary in order to use a static binary, but you may want to place it in your shell's PATH to easily call it from the command line. What is a static build and how do I install it?Ī static build is basically a binary with all the libs included inside the binary itself.

Static ffmpeg builds