# Install x264 with Homebrew H.264/AVC encoder. Version r3222 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:x264 ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install x264 ``` Evidence: provider-native install command ## Package facts - **Package key:** brew:x264 - **Package manager:** Homebrew - **Version:** r3222 - **Source summary:** H.264/AVC encoder - **Homepage:** - **Generated:** 2026-08-03T00:40:33+00:00 ## Executables - x264 (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: r3222 ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 2003-05: The first H.264/AVC specification is released. - 2004: The x264 project starts as an open-source AVC encoder. - 2008: Fiona Glaser joins the x264 development effort, one of several contributors associated with later quality and performance work. - 2010: x264, LLC is formed to provide commercial licensing while GPL development continues. - 2010s: x264 becomes deeply embedded in FFmpeg-based transcoding and professional encoding workflows. ### Related projects - VideoLAN hosts the x264 source project and is also known for VLC. - FFmpeg integrates x264 through `libx264` and is the path by which many users invoke it. - x265 is the HEVC successor-era encoder that explicitly leverages ideas and optimizations from x264. - OpenH264 is a separate H.264 encoder project with different licensing and deployment tradeoffs. ### Sources - - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Combined YAML source View the package source record on GitHub. [combined/x264.yml](https://github.com/automic-vault/db/blob/main/combined/x264.yml) ## Sources - Nucleus package database - Geiger risk classifier - curated package history - pkgdb category and tag curation