macOS
brew install x264local Homebrew formula metadata
sudo port install x264MacPorts ports tree · multimedia/x264/Portfile · Quelle: api.github.com
brew
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für x264 in AI-Agent-Workflows.
Installation
brew install x264local Homebrew formula metadata
sudo port install x264MacPorts ports tree · multimedia/x264/Portfile · Quelle: api.github.com
sudo apk add x264Alpine Linux edge package indexes · x264 · Quelle: dl-cdn.alpinelinux.org
sudo apt install x264Debian stable package indexes · x264 · Quelle: deb.debian.org
nix profile install nixpkgs#x264nixpkgs package indexes · pkgs/by-name/x2/x264/package.nix · Quelle: api.github.com
sudo pacman -S x264Arch Linux sync databases · x264 · Quelle: geo.mirror.pkgbuild.com
scoop install main/x264Scoop official bucket manifest trees · bucket/x264.json · Quelle: api.github.com
winget install --id VideoLAN.x264 -eWindows Package Manager source index · VideoLAN.x264 · Quelle: cdn.winget.microsoft.com
Überblick
H.264/AVC encoder
Verlauf
x264 is VideoLAN's open-source H.264/MPEG-4 AVC encoder library and command-line encoder. It is one of the defining software video encoders of the broadband-video era: a GPL project that became both a default tool for enthusiasts and a commercially licensed engine inside many professional products.
The project began in 2004, shortly after the first H.264/AVC specification was released in May 2003. x264's history is bound to VideoLAN and FFmpeg, because VideoLAN hosts the source community while FFmpeg exposes x264 through `libx264`, making it available to a huge base of transcoding workflows.
x264 was started to produce an open-source encoder that implemented the H.264/AVC standard with high quality and high performance. The project's commonly cited developer lineage begins with Laurent Aimar, then Loren Merritt, and later includes Fiona Glaser, Anton Mitrofanov, Henrik Gramner, and other contributors who worked heavily on psycho-visual tuning, rate control, threading, and hand-optimized assembly.
A major institutional turn came in 2010 with the formation of x264, LLC. The community kept the GPL version available, while the company provided commercial licensing for users who wanted to ship x264 in proprietary products without releasing their own source under the GPL. That dual path helped x264 remain both a free-software project and a commercial codec product.
x264's adoption accelerated because it arrived when H.264 was becoming the practical common denominator for web video, Blu-ray workflows, mobile devices, and streaming services. The x264 licensing site describes it as the most widely deployed AVC encoder and says its use expanded into billions of devices and commercially licensed products.
FFmpeg integration was decisive for package-manager users. FFmpeg documents x264 as an external library for H.264 encoding, enabled with `--enable-libx264`, and many frontends and scripts use FFmpeg rather than invoking the `x264` binary directly. That relationship made x264 a core codec package even on systems where users only see it through a larger media pipeline.
The standalone `x264` command commonly reads raw or YUV4MPEG video and writes an H.264 elementary stream or supported container output. Its famous operational model is preset plus quality target: users pick a speed preset, choose CRF or bitrate/rate-control settings, and let the encoder balance compression effort against time.
In daily use x264 is also a library dependency. Video tools call it through APIs such as FFmpeg's `libx264` wrapper to create H.264 streams for archival, streaming ladders, screen recordings, social video, and compatibility-focused transcodes. Its GPL licensing matters operationally: enabling it can change the license obligations of the resulting FFmpeg build.
x264 is a package-nerd landmark because it made 'software H.264 encoder' mean something specific: a small command and library with deep SIMD assembly, mature rate control, and highly tuned presets. It became a benchmark against which later encoders, including HEVC encoders, were compared.
It is also a classic example of codec packaging complexity. The same upstream can be an executable, a linkable library, a GPL licensing trigger, and a commercially licensed component, so package metadata around x264 often carries more legal and ecosystem meaning than a normal CLI tool.
Sicherheitslage
narrow executable package without higher-risk signals.
grün Risiko · niedrig Konfidenz · appliance
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
x264 | cli | globales Executable |
Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
https://www.videolan.org/developers/x264.html
Installationsmetadaten
| Paketschlüssel | brew:x264 |
|---|---|
| Version | r3222 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/x264 |
| Homepage | https://www.videolan.org/developers/x264.html |
| Repository | https://code.videolan.org/videolan/x264 |
| Upstream-Dokumentation | https://www.videolan.org/developers/x264.html |
| Lizenz | GPL-2.0-or-later |
| Quellarchiv | https://code.videolan.org/videolan/x264.git |
| Bottle | verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | x264 |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
libx264-164 2:0.164.3108+git31e19f9-2+b1
x264 video coding library
https://www.videolan.org/developers/x264.html
sudo apt install libx264-164libx264-dev 2:0.164.3108+git31e19f9-2+b1
development files for libx264
https://www.videolan.org/developers/x264.html
sudo apt install libx264-devx264 2:0.164.3108+git31e19f9-2+b1
video encoder for the H.264/MPEG-4 AVC standard
https://www.videolan.org/developers/x264.html
sudo apt install x264x264
nix profile install nixpkgs#x264libx264-164 2:0.164.3108+git31e19f9-1
x264 video coding library
https://www.videolan.org/developers/x264.html
sudo apt install libx264-164libx264-dev 2:0.164.3108+git31e19f9-1
development files for libx264
https://www.videolan.org/developers/x264.html
sudo apt install libx264-devx264 2:0.164.3108+git31e19f9-1
video encoder for the H.264/MPEG-4 AVC standard
https://www.videolan.org/developers/x264.html
sudo apt install x264x264 0.164.3108-r1
Free library for encoding H264/AVC video streams
https://www.videolan.org/developers/x264.html
sudo apk add x264x264-bash-completion 0.164.3108-r1
Bash completions for x264
https://www.videolan.org/developers/x264.html
sudo apk add x264-bash-completionx264-dbg 0.164.3108-r1
Free library for encoding H264/AVC video streams (debug symbols)
https://www.videolan.org/developers/x264.html
sudo apk add x264-dbgx264-dev 0.164.3108-r1
Free library for encoding H264/AVC video streams (development files)
https://www.videolan.org/developers/x264.html
sudo apk add x264-devx264-libs 0.164.3108-r1
Free library for encoding H264/AVC video streams (libraries)
https://www.videolan.org/developers/x264.html
sudo apk add x264-libsx264 3:0.165.r3222.b35605a-2
Open Source H264/AVC video encoder
https://www.videolan.org/developers/x264.html
sudo pacman -S x264x264
sudo port install x264main/x264
scoop install main/x264VideoLAN.x264
winget install --id VideoLAN.x264 -eQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.