FFmpeg Full Installation Guide for Windows 11

This explains how to install the full build of FFmpeg on Windows 11, and how to add it to the system PATH so that ffmpeg, ffprobe, and ffplay can be used from any terminal or external application.

What You Get

With a proper full installation you will have:

• ffmpeg.exe – main tool for audio/video conversion and processing

• ffprobe.exe – tool for inspecting media files (codecs, streams, metadata, etc.)

• ffplay.exe – simple media player based on FFmpeg

Once installed and added to PATH, you can run:

ffmpeg -version
ffprobe -version
ffplay -version

from any Command Prompt / PowerShell window.

1. Download FFmpeg Full Build

1. Open your browser and go to the official FFmpeg website:

   1. https://ffmpeg.org → Download → Windows

2. In the Windows builds section, choose a trusted build provider, for example:

   • Gyan FFmpeg Builds (attached in this post)

   • or BtbN Builds

3. Download a 64-bit full build (often called full_build or similar), usually a .zip file, e.g.:

   • ffmpeg-7.x-full_build.zip

4. Once the download finishes, extract the .zip file. You should see something like:

ffmpeg-7.x-full_build/
bin/
ffmpeg.exe
ffprobe.exe
ffplay.exe
doc/
presets/
...

2. Choose an Installation Folder

Do not leave FFmpeg inside Downloads. Instead, move it to a stable location, for example:

• C:\ffmpeg or

• C:\Program Files\ffmpeg

Example

1. Create the folder: C:\ffmpeg

2. Move the extracted content into C:\ffmpeg, so that you have:

C:\ffmpeg\bin\ffmpeg.exe
C:\ffmpeg\bin\ffprobe.exe
C:\ffmpeg\bin\ffplay.exe

3. Add FFmpeg to the PATH (Windows 11)

To use ffmpeg from any Command Prompt / PowerShell window, you must add its bin folder to the PATH environment variable.

3.1 Open Environment Variables

You can do this in two ways.

Method A – via Start menu

1. Press Win and type: env

2. Click “Edit the system environment variables”.

3. In the System Properties window, click “Environment Variables…”.

Method B – via Settings

1. Press Win + I to open Settings.

2. Go to System → About.

3. Click “Advanced system settings”.

4. Click “Environment Variables…”.

3.2 Add the

You can add FFmpeg to:

• User variables (only your user account can use it), or

• System variables (all accounts can use it – requires admin rights).

Here is the typical way using User variables:

1. In the Environment Variables window, in the top section “User variables for ”, locate Path.

2. Select Path and click “Edit…”.

3. In the Edit environment variable window:

   • Click OK on all open dialog windows to save the changes.

   • Click “New”

   • Add the path to FFmpeg’s bin folder, for example: C:\ffmpeg\bin

💡" src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f4a1.png" title="Light bulb :bulb:" data-shortname=":bulb:" loading="lazy" width="64" height="64"> Make sure you add the bin folder, not just C:\ffmpeg.

4. Verify the Installation

1. Close all existing terminal windows (Command Prompt, PowerShell, Windows Terminal, etc.).

2. Open a new Command Prompt:

   • Press Win, type cmd, and press Enter.

3. Run: ffmpeg -version

If everything is configured correctly, you should see FFmpeg version information, something like:

ffmpeg version 7.x Copyright (c) ...
configuration: ...
libavutil ...
libavcodec ...
...

You can also test:

ffprobe -version
ffplay -version

to confirm those tools are available too.

5. Common Issues & Fixes

5.1

If you see:

'ffmpeg' is not recognized as an internal or external command,
operable program or batch file.
then:

• Double-check you added the correct pathto the Path variable, e.g.:

  • C:\ffmpeg\bin

1. Make sure you clicked OK on all windows after editing Path.

2. Close and reopen the terminal window.

3. If you had multiple FFmpeg installations, ensure the correct path is present and at the top of the list.

5.2 Multiple FFmpeg Versions in PATH

If you had older FFmpeg installations (e.g. C:\Program Files\ffmpeg-old\bin), Windows might use the first entry in Path.

To clean this up:

1. Open Environment Variables again.

2. Edit Path and remove any obsolete FFmpeg entries.

3. Keep only the path you want, e.g.: C:\ffmpeg\bin

4. Optionally, move this entry to the top of the list.

Using FFmpeg in Your Own Apps

Once FFmpeg is in PATH, any application can call it just by using the command name ffmpeg without needing a hard-coded full path.

Example: Python (subprocess)

import subprocess

cmd = [
"ffmpeg",
"-i", "input.mp4",
"-vn",
"-acodec", "mp3",
"output.mp3",
]

result = subprocess.run(cmd, capture_output=True, text=True)
print(result.stdout)
print(result.stderr)

Click to expand...

This will work as long as FFmpeg is installed and the PATH is configured correctly.

7. Uninstall or Move FFmpeg

If you want to move or remove FFmpeg:

1. Remove its entry from the Path environment variable.

2. Delete or move the C:\ffmpeg folder (or whichever folder you used).

3. Restart your terminal. Running ffmpeg -version should now fail, confirming it is removed.

8. License

FFmpeg is licensed under the LGPL/GPL (depending on how it is built and which libraries are included). For detailed licensing information, see:

• https://ffmpeg.org/legal.html

When redistributing FFmpeg binaries or using it in your software, make sure you comply with the relevant licenses.