Downloads of v 5.1.2:


Last Update:

26 Sep 2022

Package Maintainer(s):

Software Author(s):

  • FFmpeg Contributors


ffmpeg libavcodec foss cli audio video convert cross-platform media full

FFmpeg Full

  • 1
  • 2
  • 3

5.1.2 | Updated: 26 Sep 2022



Downloads of v 5.1.2:


Software Author(s):

  • FFmpeg Contributors

  • 1
  • 2
  • 3
FFmpeg Full 5.1.2

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install FFmpeg Full, run the following command from the command line or from PowerShell:


To upgrade FFmpeg Full, run the following command from the command line or from PowerShell:


To uninstall FFmpeg Full, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade ffmpeg-full -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade ffmpeg-full -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install ffmpeg-full
    name: ffmpeg-full
    version: '5.1.2'
    state: present

See docs at

chocolatey_package 'ffmpeg-full' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '5.1.2'

See docs at

cChocoPackageInstaller ffmpeg-full
    Name     = "ffmpeg-full"
    Version  = "5.1.2"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'ffmpeg-full':
  ensure   => '5.1.2',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 26 Sep 2022.


FFmpeg is the leading multimedia framework, able to decode, encode, transcode, mux, demux, stream, filter and play pretty much anything that humans and machines have created. It supports the most obscure ancient formats up to the cutting edge. No matter if they were designed by some standards committee, the community or a corporation. It is also highly portable: FFmpeg compiles, runs, and passes our testing infrastructure FATE across Linux, Mac OS X, Microsoft Windows, the BSDs, Solaris, etc. under a wide variety of build environments, machine architectures, and configurations.

The FFmpeg project tries to provide the best technically possible solution for developers of applications and end users alike. To achieve this we combine the best free software options available. We slightly favor our own code to keep the dependencies on other libs low and to maximize code sharing between parts of FFmpeg. Wherever the question of "best" cannot be answered we support both options so the end user can choose.

Security is a high priority and code review is always done with security in mind. Though due to the very large amounts of code touching untrusted data security issues are unavoidable and thus we provide as quick as possible updates to our last stable releases when new security issues are found.


  • This package is for the stable static full ffmpeg version.
    For a list of libraries included, go to
    (provides everything included in the 'essentials' build with additional libraries)
    note that the list of libraries at the URL above will give those for the most recent version and may differ slightly from this package version

$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

$packageArgs = @{
  PackageName    = $env:ChocolateyPackageName
  FileFullPath64 = "$toolsPath\ffmpeg-release-full.7z"
  Destination    = $toolsPath

Get-ChildItem $toolsPath\* | Where-Object { $_.PSISContainer } | Remove-Item -Recurse -Force #remove older package dirs
Get-ChocolateyUnzip @packageArgs

Write-Host "Removing extracted archive."
Remove-Item $packageArgs['FileFullPath64'] -ea 0

$maxTries = 3

for ($tries = 0; $tries -lt $maxTries; $tries++) {
  Write-Host "Sleeping for 2 seconds to allow anti-viruses to finish scanning..."
  Start-Sleep -Seconds 2
  try {
    Write-Host "Renaming ffmpeg directory to common name (Try $($tries + 1) / $maxTries)"
    Move-Item $toolsPath\ffmpeg-* $toolsPath\ffmpeg
    Write-Host "Successfully renamed directory."
  catch {
    if (($tries + 1) -eq $maxTries) {
      throw "Unable to rename directory, and max tries achieved. Aborting installation..."
    else {
      Write-Warning "Unable to rename directory. Retrying..."
md5: 1C7C6328BF30C29ED6C971C69E7D3D11 | sha1: E08F7DDF80DC9D6230E21E438B938657B68438E4 | sha256: 037BDB2183189DC0EFA642B1FDE7D6B33C6114036FA06FAF35F777E8DF07D863 | sha512: 2320A8AA93A6557F618402EC47D6996D42527F8D4FCBD94FA635248F3415BF2636022118141AF4B5DC15FFD0EB167B7322C61260A84774C9AE848BF52CD23931

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
FFmpeg Full 5.1.1 902 Thursday, September 1, 2022 Approved
FFmpeg Full 5.1 1038 Sunday, July 24, 2022 Approved
FFmpeg Full 1700 Friday, April 8, 2022 Approved
FFmpeg Full 5.0.1 152 Thursday, April 7, 2022 Approved
FFmpeg Full 5.0 1440 Sunday, January 16, 2022 Approved
FFmpeg Full 4.4.1 975 Monday, October 25, 2021 Approved
FFmpeg 4.4 1154 Thursday, April 29, 2021 Approved

This package has no dependencies.

Discussion for the FFmpeg Full Package

Ground Rules:

  • This discussion is only about FFmpeg Full and the FFmpeg Full package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or FFmpeg Full, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus