Installing FFmpeg on Windows may sound like a task reserved for people who are perfectly happy living inside a terminal, but the process is actually quite straightforward once you understand what you are doing. FFmpeg is an open-source multimedia tool that lets you work with audio and video from the command line, making it especially useful for converting formats, inspecting files or preparing content without relying on a graphical interface.
The key is not to look for a traditional installer with “next, next, finish” buttons, because that is not how this works. On Windows, you need to download a prebuilt package, place it in a stable folder and add it to the system PATH so you can run it from any Command Prompt window. In other words, it is the kind of setup that looks more intimidating than it really is.
Download FFmpeg and prepare the folder in Windows
The first recommended step is to install 7-Zip, if you do not already have it on your PC. The FFmpeg download for Windows usually comes compressed in .7z format, so you will need a tool capable of extracting that package correctly. 7-Zip is free and fits this job perfectly, without any unnecessary extras.
Next, go to the FFmpeg builds page for Windows hosted on gyan.dev. From there, the usual choice for modern PCs is to download the ffmpeg-release-full.7z file, which is the full version and is intended for Windows 10 and later. If the computer is still running Windows 7 or Windows 8, the source indicates that you should use ffmpeg-release-essentials.7z instead, as the full build may not start on those older systems.
Once the file has downloaded, open File Explorer, go to the Downloads folder and extract the contents with 7-Zip. In Windows 11, you may first need to click Show more options to see the classic menu. After extraction, a folder with a long name will appear; rename it to FFmpeg to avoid endless paths, which always end up looking like miniature Kubernetes logs.
The next step is to place that folder at the root of the main drive, usually C:\. In practice, simply cut the FFmpeg folder from Downloads and paste it inside This PC, on the drive usually called Windows (C:) or OS (C:).
Add FFmpeg to the PATH and check that it works
At this point, FFmpeg is already on your computer, but Windows still does not know where to find it when you type a command. To make the system recognise it from any location, you need to add the C:\FFmpeg\bin folder to the PATH environment variable. This is the step that turns a downloaded folder into a genuinely usable tool.
Open the Start menu, type cmd, right-click Command Prompt and choose Run as administrator. It is important to do this with elevated permissions, because you are going to modify a system variable. In that window, enter the following command:
setx /m PATH "C:\ffmpeg\bin;%PATH%"
When it finishes, close that Command Prompt window. This detail is not decorative: the open session does not always pick up newly applied changes, so to check the installation you need to open a new window. Type cmd again, open a regular Command Prompt and run:
ffmpeg -version
If everything has gone well, Windows will display information about the installed FFmpeg version and its components. From that point on, you can run FFmpeg commands from the terminal without manually navigating to its folder. Isn’t it rather satisfying when a command-line utility responds on the first try?
There is also an alternative route using the Windows Package Manager. The source includes the command winget install -e --id Gyan.FFmpeg --exact, which may be more convenient for those who already install software from the terminal. Even so, the manual method makes it very clear where FFmpeg is located and which path is being added, which is useful when you need to diagnose problems.
Common errors when installing FFmpeg on Windows
One of the behaviours that most often confuses users at first happens when double-clicking ffmpeg.exe, ffplay.exe or ffprobe.exe: a window opens for an instant and then disappears. This is not an error. FFmpeg is not a graphical application, but a tool designed to be run from Command Prompt with commands and parameters.
If, when adding it to the PATH, you see a message similar to Access to the registry path is denied, the problem is usually that Command Prompt was not opened as administrator. Close the window, search for cmd again, right-click it and select Run as administrator before repeating the setx command.
Another classic issue is the error ‘ffmpeg’ is not recognised as an internal or external command. If it appears right after installing it, the first thing to do is close the current window and open a new one. If it continues, check that the folder is actually in C:\FFmpeg and that the bin subfolder exists inside it. Windows is not case-sensitive with folder names, so FFmpeg and ffmpeg should not make any difference.
On older computers, the error 0xc0000005 may appear when trying to launch the full version. According to the source, this is related to unsupported Windows systems, such as Windows 7 or 8, and the sensible solution is to download the Essentials build instead of the Full one. And if you work with Ubuntu through WSL, you can run the binary from /mnt/c/FFmpeg/bin or install FFmpeg directly inside Ubuntu with sudo apt install ffmpeg, which usually fits better if your entire workflow lives in Linux.
