FFmpeg Installation and Usage Guide

Liang — Mon, 27 Apr 2026 08:18:34 +0000

Have you ever downloaded a video only to find it won't play on your phone? Or maybe you captured a great clip and wanted to trim a specific part for social media, but didn't know which software to use? If you want to avoid installing bloated, ad-filled video editing software, FFmpeg is exactly what you need.
FFmpeg is an open-source, free, and powerful multimedia framework. While it primarily operates via a command-line interface, once you get the hang of it, you'll find it far more efficient than any graphical user interface (GUI) software. This guide will walk you through how to install and use FFmpeg on Windows.
On a side note: A few years ago, I wouldn't have recommended FFmpeg to beginners. However, the era of AI has changed everything. Even if you have zero technical background, you can use AI to write command-line code for you. In fact, despite being a long-time FFmpeg user, I rarely write commands from scratch anymore. Now, let’s get back to the tutorial.

Part 1: Installing FFmpeg

Visit the Official Download Page: Open your browser and go to the FFmpeg download section for Windows: https://www.gyan.dev/ffmpeg/builds/
Choose a Version: The ones labeled essentials contain the basic tools, while full contains all libraries. Theoretically, the "essentials" version is enough for most tasks, but I recommend downloading the full version since modern computers have plenty of storage space.
Extract and Move Extract the downloaded ZIP file and move the folder to a location you can easily remember, such as C:\FFmpeg or E:\FFmpeg.

Part 2: Configuring Environment Variables (to make FFmpeg accessible anywhere)

Find the bin path: Go into the FFmpeg folder you just extracted and locate the subfolder named bin. For example, mine is E:\ffmpeg\bin. Copy this path.
Press the Win key, type environment in the search box.
Click on Edit the system environment variables.
Click on Environment Variables.
In the “System variables” list, find and double-click the Path variable.
Click on “New” at the top right, then paste the bin folder path you copied.
Click “OK” all the way to save.
Verify the installation: Press Win + R, type cmd to open Command Prompt, and enter the following command, ffmpeg -version.

Part 3: Basic FFmpeg Usage with AI

The best way to use FFmpeg today is to describe your needs accurately to an AI. You can ask if a specific task can be done with FFmpeg and then request the specific code. If you run into an error, just copy and paste the error message back to the AI. With a bit of practice, it becomes second nature.
To use the commands, copy the code provided by the AI and paste it into a terminal. You can use the standard Command Prompt (cmd) or PowerShell.

Recommended Prompt Template:

[Enter your requirement here]
Input parameters:
1. Full path of the input file
2. Output folder
3. Specific requirements (e.g., quality, format, speed)

Example: Hardburning Subtitles

Here is a prompt I often use to burn subtitles into a video:

Write an FFmpeg script to:
Burn subtitles into a video (Hardsubs).
**Parameters**:
1. Subtitle file path
2. Video file path
3. Use GPU acceleration (Yes/No)
4. Encoding speed and video quality
5. Output format and folder
**Requirements**:
1. Re-encode video, copy audio directly, and remove existing subtitle tracks.
2. Provide a PowerShell script that I can run directly.

The AI would generate a script similar to this:

# --- Configuration Area ---
$VideoPath    = "C:\Videos\input_video.mp4"
$SubtitlePath = "C:\Videos\subs.ass"
$OutputDir    = ""                        # Leave empty "" to output to the source folder
$UseGPU       = $true                     # $true for NVIDIA NVENC, $false for CPU
$Speed        = "p7"                      # GPU: p1 (fastest) to p7 (best quality) | CPU: ultrafast, medium, veryslow

# --- Quality Control ---
$Quality      = 27                        # Set quality level
$EncFormat    = "av1"                     # Codec: "av1", "h264", or "h265"
$OutContainer = "mp4"                     # Extension: mp4, mkv, etc.

# 1. Path Validation
if (-not (Test-Path -LiteralPath $VideoPath)) {
    Write-Host "Error: Video file not found" -ForegroundColor Red; exit 1
}

if ([string]::IsNullOrWhiteSpace($OutputDir)) {
    $OutputDir = Split-Path -Parent $VideoPath
}

$FileName = [System.IO.Path]::GetFileNameWithoutExtension($VideoPath)
$OutputFile = Join-Path $OutputDir ("{0}_hardsub.{1}" -f $FileName, $OutContainer)

# Escaping subtitle path for FFmpeg
$EscapedSubPath = $SubtitlePath -replace '\\', '/' -replace ':', '\:' -replace "'", "\'"

# 2. Determine Encoder
if ($UseGPU) {
    if ($EncFormat -eq "av1") { $VideoCodec = "av1_nvenc" } 
    elseif ($EncFormat -eq "h265") { $VideoCodec = "hevc_nvenc" } 
    else { $VideoCodec = "h264_nvenc" }
    $QualityArgs = @("-cq", "$Quality", "-b:v", "0")
} else {
    if ($EncFormat -eq "av1") { $VideoCodec = "libsvtav1" } 
    elseif ($EncFormat -eq "h265") { $VideoCodec = "libx265" } 
    else { $VideoCodec = "libx264" }
    $QualityArgs = @("-crf", "$Quality")
}

# 3. Build and Execute FFmpeg Command
$FFmpegArgs = @(
    "-hide_banner", "-loglevel", "warning", "-stats",
    "-i", $VideoPath,
    "-vf", "subtitles='$EscapedSubPath'",
    "-c:v", $VideoCodec,
    "-preset", $Speed
) + $QualityArgs + @(
    "-c:a", "copy", "-sn", "-y", $OutputFile
)

Write-Host "Processing: $FileName" -ForegroundColor Cyan
& ffmpeg $FFmpegArgs

if ($LASTEXITCODE -eq 0) {
    Write-Host "Success!" -ForegroundColor Green
} else {
    Write-Host "Failed. Check the output above." -ForegroundColor Red
}
Read-Host "Press any key to close"

I personally prefer PowerShell, but you can ask the AI to write a CMD (.bat) script as well; they work similarly.

Conclusion

The charm of FFmpeg lies in its "lightweight" yet "powerful" nature. While the command line might seem intimidating at first, it becomes very intuitive once you start playing with it. You might even find yourself preferring it over GUI tools! Don't limit yourself—give it a try.

Today's Interaction: What was the first problem you solved using FFmpeg? Feel free to share your story!