How to Install FFmpeg on Windows 11 and Add It to PATH

To install FFmpeg on Windows 11 you have three sensible routes: the built-in winget package manager, Chocolatey, or a ZIP file you unpack yourself. Whichever you pick, the binaries end up in a folder somewhere and Windows still does not know about them, so the real work is the PATH entry that follows the install. That single step is what separates a tool that runs on the first try from one that says it is not recognized as an internal or external command. Below is the whole process, including the Windows 11 app execution alias that breaks a correct install.

What you are actually installing

FFmpeg is not an application with a window and a settings page. It is a bundle of command line programs: ffmpeg.exe for converting media, ffprobe.exe for reading information about a file, and ffplay.exe for playing one back. You use them from Command Prompt, PowerShell, or Windows Terminal.

That matters for the install. There is no installer wizard and no single official build, which is why gyan.dev and the BtbN builds on GitHub come up more often than anything else. Both are trusted and both give you Windows executables. The gyan.dev essentials build is the sensible default, since it includes libmp3lame, libopus and libvpx and skips the larger download of the full build.

Option 1: install FFmpeg on Windows 11 with winget

Windows 11 ships with the Windows Package Manager, so this needs no extra software. Open Terminal from the Start menu and run:

winget install Gyan.FFmpeg

The Gyan.FFmpeg package is the community build published through the winget manifest. The download runs in the background, and when it finishes winget prints a success message with the package id.

Where it lands is the part that trips people up. Winget installs portable packages under your user profile:

C:\Users\yourname\AppData\Local\Microsoft\WinGet\Packages\Gyan.FFmpeg_<version>\

Because that is a user folder and not a machine folder, it never goes on the machine PATH. Winget also links the executables into C:\Users\yourname\AppData\Local\Microsoft\WinGet\Links, and that folder is on your user PATH only when your build of winget put it there. Check rather than assume:

where ffmpeg

If nothing comes back, open a brand new terminal and try again, since the install does not reach the window you were already using. If it still comes back empty, add the bin folder inside the package directory to your user PATH.

Winget also keeps the install tidy when you want it gone again: winget list shows what is installed and winget uninstall Gyan.FFmpeg removes it cleanly.

Option 2: install with Chocolatey

Chocolatey is the package manager for people who already use it on Windows 10 or on a work machine. If it is not installed, the setup takes a few minutes on its own, so check first by typing choco in an elevated Command Prompt. If the command exists, install FFmpeg like this:

choco install ffmpeg -y

The elevated prompt matters because Chocolatey writes into C:\ProgramData\chocolatey. The real files sit in C:\ProgramData\chocolatey\lib\ffmpeg, and Chocolatey creates shims in C:\ProgramData\chocolatey\bin that point at them. That bin folder is on the system PATH by default, so ffmpeg normally works straight away with no PATH editing.

The trade-off against winget is the footprint. Chocolatey installs a package manager and its cache, while winget is already part of Windows 11, so winget is the shorter path here.

Option 3: install from a ZIP file

This is the route to take if you want a specific build or a portable copy on a USB drive. Download from gyan.dev or the BtbN FFmpeg-Builds releases on GitHub, then follow these steps.

1. Download the archive. On gyan.dev the links sit under the essentials build for Windows. On GitHub, BtbN publishes rolling builds as numbered .zip files.
2. Create a permanent folder for it. C:\ffmpeg is the usual choice. Do not extract into Downloads, the Desktop, or a temp folder, because Windows will eventually clear those and your tools with them.
3. Right click the ZIP, choose Extract All, and set the destination to C:\ffmpeg.
4. Open C:\ffmpeg. The archive contains its own folder, so you will see C:\ffmpeg\ffmpeg-7.1-essentials_build. Either rename that inner folder to bin, or point PATH at C:\ffmpeg\ffmpeg-7.1-essentials_build\bin.
5. Confirm ffmpeg.exe sits inside the bin folder. That is the executable you are after.

Windows can extract ZIP files on its own now, so no third party archiver is needed. If the extraction fails or produces an empty folder, that is a separate problem with a guide of its own.

One caution on location. Installing into C:\Program Files works, but every folder under it needs administrator rights to modify, and some applications that call ffmpeg will not start it from there without elevation. A plain folder such as C:\ffmpeg avoids that.

Add the bin folder to your PATH

This is the step that turns a folder of files into a tool you can call from anywhere. The bin subfolder matters, because it is where ffmpeg.exe, ffprobe.exe and ffplay.exe live.

1. Press Win+Pause to open System, then choose Advanced under Advanced system settings.
2. Choose Environment Variables at the bottom of the Advanced tab.
3. In the upper box under User variables, select Path and choose Edit. Do not touch the lower machine variables unless you installed FFmpeg somewhere every account should use.
4. Choose New and type the path to the bin folder with no trailing backslash: C:\ffmpeg\bin.
5. Choose OK on the Path window, then OK on Environment Variables, then OK on System Properties.

A faster route to the same dialog is Win+R followed by environment. On Windows 10 the path is Control Panel, System, Advanced system settings, with the Environment Variables button in the same place.

Two things to get right here. Add the folder, not ffmpeg.exe, since PATH holds directories. And use the user list rather than the machine list, so you can change it later without administrator rights and without affecting other accounts.

Verify the install in a fresh terminal

Close every open terminal window and open a new one. Terminals that were already running keep the environment they started with, so they cannot see the new PATH entry.

ffmpeg -version

A working install prints the version, the configuration line and the library versions. If you see that, the tool is live. Next check that the encoders you need came with the build:

ffmpeg -hide_banner -encoders | findstr libmp3lame

In PowerShell use ffmpeg -hide_banner -encoders | Select-String libmp3lame. A line mentioning libmp3lame means MP3 encoding is available. The same check works for libopus, libx264 or hevc.

If the command is still not found, run where ffmpeg. An empty result means the PATH entry is missing or was saved to the wrong list. A result pointing at the WindowsApps folder means the app execution alias is shadowing your install.

The app execution alias that breaks the install

Windows 11 creates placeholder executables for Store apps in C:\Users\yourname\AppData\Local\Microsoft\WindowsApps. When FFmpeg was still listed in the Microsoft Store, one of those placeholders was named ffmpeg.exe. The Store version has since been deprecated, and the placeholder is often left behind pointing at a package that no longer exists.

The symptom is confusing because the install is perfect. You type ffmpeg, Windows opens the alias, and the alias tries to launch a missing app, showing a message such as This app can't run on your PC or You can't use this app on your PC. A second variant shows a Microsoft Store page instead of doing any work.

1. Open Settings.
2. Go to Apps, then Advanced app settings, then App execution aliases.
3. Find ffmpeg in the list and switch it off.

You can reach the same screen by searching for app execution aliases in the Start menu. Once it is off, where ffmpeg should show only your real install. Windows 10 keeps the same alias folder, though you will hit it far less often there.

Why not the Microsoft Store

Search the Store for ffmpeg and you will find listings that claim to be the official version. None of them are official Microsoft apps. Microsoft never shipped ffmpeg as its own software, and the Store build that circulated for a while has been deprecated, which is why the broken alias exists.

There are practical reasons to avoid that route even if a listing is still reachable. A Store install is sandboxed, updates on the Store schedule rather than on yours, and it is awkward to run from a script. Winget, Chocolatey and the ZIP from gyan.dev all put real executables on disk that any program can call.

With the tool installed, the next step is a real job. The guide to converting MP4 to MP3 for free starts with a single command, and the video compression walkthrough covers shrinking a file you already have. If something still refuses to run, the ffmpeg troubleshooting guide works through each error message in order.

Frequently asked questions

Do I need to restart Windows after installing FFmpeg?

Only sign out and sign back in, and only if you edited the machine PATH. A change to your user PATH applies to programs started after the change, so closing the current terminal and opening a new one is enough for a normal install.

Where does winget install Gyan.FFmpeg?

Into your user profile, under C:\Users\yourname\AppData\Local\Microsoft\WinGet\Packages, in a folder named after the package. Because it lands in a user folder it is never added to the machine PATH, and depending on the build the Links folder is not always on your PATH either. Run where ffmpeg to see what Windows can find.

Which FFmpeg build should I download from gyan.dev?

The essentials build for everyday work. It includes libmp3lame, libopus and libvpx, which covers audio conversion and most video tasks, and the download is smaller than the full build. The full build adds extra encoders such as libsvtav1 and libfdk_aac that you only need for specific formats.

What is the ffmpeg app execution alias on Windows 11?

A placeholder file called ffmpeg.exe in C:\Users\yourname\AppData\Local\Microsoft\WindowsApps that Windows creates for Store apps. When it sits earlier in PATH than your real install, typing ffmpeg opens the alias and you get a message that the app cannot run on your PC. Turn the ffmpeg alias off in Settings, Apps, Advanced app settings, App execution aliases.

Do I need administrator rights to install FFmpeg?

Not for the manual ZIP route or for winget, as long as you install into a folder you own such as C:\ffmpeg. Chocolatey needs an elevated Command Prompt because it writes into C:\ProgramData. Editing your own user PATH in the Environment Variables dialog needs no administrator rights either.

What to remember

• Pick one install method. Mixing winget, Chocolatey and a manual ZIP gives you three copies and no idea which one runs.
• A ZIP install needs a permanent folder such as C:\ffmpeg, and the executables live in the bin subfolder inside it.
• Adding C:\ffmpeg\bin to your user PATH is the step most installs leave out.
• Verify in a terminal you opened after the change, with ffmpeg -version.
• If Windows says the app cannot run on your PC, check the app execution alias in Windows 11 Settings.
• The Microsoft Store copy was never an official Microsoft app and has been deprecated, so use winget, Chocolatey, or a trusted build site.

Install it, add C:\ffmpeg\bin to your user PATH, then open a new PowerShell window and run ffmpeg -version. If the command answers with a version and a configuration line, the tool is ready and you can move straight to a real conversion task such as turning an MP4 into an MP3. If it stays silent, run where ffmpeg and read the first path, because that single line tells you whether you are looking at a missing PATH entry or an app execution alias standing in the way.