Open Source Alternatives
  • Alternatives
  • Categories
    Categories by size1,302 projects
    • Developer Tools673
    • AI & Machine Learning549
    • Business & Productivity311
    • Web Development219
    • Security & Monitoring198
    • Communication & Collaboration168
    • IT Management165
    • Design & Creative145
    • LLMOps & AI Tooling142
    • DevOps & CI/CD141
    Browse all 21 categoriesCloud & Hosting, Product & Project Management and 9 more
  • Blog
  • Advertise
SearchNotion, Slack, password manager.../
Submit
Open Source Alternatives
  • Alternatives
    • Developer Tools673
    • AI & Machine Learning549
    • Business & Productivity311
    • Web Development219
    • Security & Monitoring198
    • Communication & Collaboration168
    • Browse all 21 categories
  • Blog
  • Advertise
Submit your project

New open source projects by email

The projects we add and every new guide. Free, unsubscribe any time.

Open Source Alternatives LogoOpen Source Alternatives

Handpicked Open Source Alternatives to Paid Softwares

Add Open Source Alternatives as a preferred source on Google

Product

  • Categories
  • Tag
  • Advertise

Resources

  • Blog
  • Collection
  • Submit

Company

  • Privacy Policy
  • Terms of Service
  • Refund Policy
  • Sitemap

Alternatives

  • Claude Code
  • Jira
  • Notion
  • Slack
  • Linear
  • Wispr Flow
  • All alternatives
© 2026 Open Source Alternatives. All rights reserved.
Open SourceAlternatives
Home/Categories/Design & Creative/Avm
icon of Avm

Avm

  • 264 stars
  • BSD-3-Clause-Clear
  • Active this week
  • Last commit today

Last verified Nov 18, 2026

Build AV2 video codecs and test bitstream conformance using the official encoder/decoder reference from Alliance for Open Media.

Visit websiteGitHub264 stars
image of Avm
TL;DR

Avm (AOM Video Model) is the reference encoder and decoder for AV2, the royalty-free video codec from Alliance for Open Media succeeding AV1. AV2 targets compression efficiency comparable to H.265 and H.266 without per-device royalty fees. Under the BSD-3-Clause-Clear license, self-hosting and commercial use are permitted with attribution, though no patent rights to the AV2 codec are granted by the software license. Best for video codec researchers, compression engineers, and platform teams benchmarking AV2 before hardware encoder support arrives.

Read the full breakdownHide the full breakdownWho it is for, how it works, trade-offs, the quick start and the FAQ
who it's for

Who Avm is for#

Video codec researchers studying AV2 compression algorithms

AVM provides direct access to the reference AV2 encoder and decoder used in AOMedia's standardization process. Researchers can modify codec parameters via CONFIG_ flags, integrate VMAF for quality analysis, and run against the CTC test sequences to compare results with other codec implementations or previous codec generations.

Skip if:

If you are studying a different codec generation (AV1, H.265, H.264), use the reference implementation for that codec. AVM is AV2-specific.

Hardware encoder teams validating AV2 bitstream conformance

AVM produces the canonical AV2 bitstream that hardware encoder implementations must match. Teams developing FPGA or ASIC encoders for AV2 use AVM as the golden reference decoder to verify that their encoded output is bitstream-compliant before tape-out or silicon validation.

Skip if:

If you are validating conformance for a different codec, use the reference decoder for that codec. AVM is AV2-specific and cannot validate H.265 or AV1 bitstreams.

Platform engineers benchmarking AV2 quality before deployment

Streaming platforms and device OEMs evaluating whether to adopt AV2 for the next generation of their encoding pipeline can use AVM to run quality benchmarks against H.265 and AV1 on the CTC test sequences. VMAF integration and configurable codec parameters enable direct quality comparisons at the same bitrate.

Skip if:

If you need production-scale benchmarks with hardware acceleration, AVM's reference-grade encoding speed does not reflect what a hardware encoder achieves. Use AVM for quality analysis only, not throughput measurement.

the problem

The problem it solves#

Building encoder or decoder software for a new video codec requires a canonical reference to test bitstream conformance against. Without one, interoperability between independently developed implementations breaks down. The challenge for teams working with video compression is that existing reference-quality codecs either carry per-device patent royalties (H.265, H.266) or belong to previous codec generations (AV1, VP9). There is no production-grade AV2 encoder yet, and the gap between a written specification and a tested implementation is exactly where codec development fails without a reference.

The pain is sharpest for teams planning the next wave of infrastructure: streaming platforms, hardware encoder vendors, and mobile device OEMs all need to benchmark AV2's compression efficiency before committing to its deployment. Without a public reference implementation they can build, run, and modify, those evaluations cannot happen.

how Avm solves it

How it solves it#

CMake build with ENABLE_ and CONFIG_ flag families

The build system uses two distinct flag families set at cmake invocation time. ENABLE_FEATURE flags control build system behavior (ccache, debug builds, shared library output). CONFIG_FEATURE flags control codec-level parameters, defined in cmake/avm_config_defaults.cmake. Nearly every aspect of the codec can be tuned without touching C source code.

VMAF quality metric integration

Build with -DCONFIG_TUNE_VMAF=1 after installing libvmaf to enable quality-metric-guided encoding. The encoder can then target a VMAF perceptual quality score rather than a fixed quantizer. The VMAF model path can be overridden at runtime with --vmaf-model-path, allowing teams to use custom or updated models.

Multi-architecture and cross-compilation via toolchain files

x86 targets use yasm (preferred) or nasm for SIMD assembly. ARM and other architectures use CMake toolchain files in the cmake/toolchains/ directory, passed via -DCMAKE_TOOLCHAIN_FILE at configuration time. Visual Studio 2019 and Xcode builds are both documented, covering Linux, macOS, and Windows host/target combinations.

Shardable unit test suite with CTC sequences

Unit tests are built on gtest and support sharding across CPU cores via GTEST_TOTAL_SHARDS and GTEST_SHARD_INDEX. The Common Test Conditions (CTC) test sequences, used in AOMedia's AV2 standardization work, can be downloaded and run with make testdata and the examples.sh script included in the repository.

Static library and shared object build modes

The default build produces a static library. Enabling BUILD_SHARED_LIBS produces a shared object on Linux and macOS (not supported on Windows). Both modes expose the same C API, so the choice depends on the linker requirements of the application consuming AVM.

strengths · trade-offs

Strengths and trade-offs#

Strengths

  • Royalty-free codec with no per-device fees from AOMediaAV2 is designed as a royalty-free alternative to H.265 and H.266, which carry per-device licensing fees from MPEG LA. The BSD-3-Clause-Clear license permits commercial use and self-hosting with attribution. Large streaming platforms and device OEMs can evaluate AV2 without signing a patent license before deployment decisions are made.
  • Alliance for Open Media consortium backingAOMedia counts Google, Netflix, Apple, Microsoft, and Mozilla among its founding and contributing members, the same consortium that produced AV1 and VP9. Active maintenance is visible in the GitHub history: 264 stars and 82 forks reflect the codec research community's engagement, and the repository received its last push on 2026-11-17.
  • Enforced code quality via clang-format and cmake-formatGoogle C++ Coding Style is enforced with clang-format, with the specific version pinned in .clang-format for reproducibility across contributor environments. cmake-format handles build files. The README provides a pre-commit hook example that runs both formatters automatically before each commit.
  • Stable main branch plus active encoder optimization branchThe main branch is stable and thoroughly tested. The av2-enc branch carries more recent encoder optimizations not yet merged into main, giving teams a way to track encoding performance improvements while keeping conformance testing builds on the stable branch.

Trade-offs

  • -Build-from-source only, no prebuilt binaries or packagesAVM has no Homebrew cask, Docker image, or package manager distribution. Every deployment starts with git clone, CMake configuration, and a make build. x86 builds additionally require yasm or nasm. On systems without the prereqs installed, reaching the first successful encode requires substantial setup time.
  • -Research-grade code, not a production encoderAVM is the reference implementation for conformance and benchmarking, not a throughput-optimized production transcoder. Encoding speed is secondary to bitstream correctness. Teams needing high-throughput AV2 encoding for production deployments will need to wait for AV2 support in tools like FFmpeg or dedicated hardware encoders.
  • -No patent rights granted by the BSD-3-Clause-Clear licenseThe software license permits self-hosting, commercial use, and redistribution with attribution, but explicitly grants no patent rights to the AV2 codec. Shipping a product that encodes or decodes AV2-compressed content at commercial scale may require a separate patent license from Alliance for Open Media's patent pool. Confirm with legal counsel before production deployment.
versus alternatives

Avm vs alternatives#

AVM (AV2) vs H.265/HEVC and Commercial Codec Licensing

AV2 targets the same quality tier as H.265 (HEVC), aiming for comparable compression efficiency without per-device patent royalties. The comparison is not tool-to-tool but licensing-to-licensing: H.265 carries royalty obligations through MPEG LA for commercial deployment, while AV2 is designed from the ground up as royalty-free for end-users.

FeatureAVM (AV2)H.265/HEVC
Software licenseBSD-3-Clause-ClearLGPL (x265 encoder)
Patent royaltiesRoyalty-free from AOMediaMPEG LA fees for commercial use
Self-hostingBuild from sourceBuild from source (x265 is LGPL)
Encoding speedReference-gradeProduction-grade
Hardware encoder supportNone yetBroad (Intel QSV, NVIDIA NVENC, Apple VT)
Primary useResearch and conformanceProduction transcoding

AVM is the right choice when validating AV2 bitstream conformance, running codec research against the Common Test Conditions sequences, or benchmarking AV2 quality before hardware encoder support arrives in production stacks. For any production video workflow today, H.265 encoders are the better operational choice: mature hardware acceleration, production-optimized software encoders like x265, and broad toolchain support in FFmpeg make H.265 more practical than AVM's research-grade implementation.

For teams planning the codec roadmap beyond H.265, AVM provides the reference point that production AV2 implementations will eventually match.

install · quick start

Quick start#

bash
Build AVM from source; setup requires CMake 3.16+, Git, Perl, and yasm or nasm (x86 targets).
```bash
git clone https://github.com/AOMediaCodec/avm.git
cd avm
cmake .
make
```
tech stack · detected from GitHub

What it's built on#

Languages
CC++PythonRust
frequently asked

FAQ#

How does AVM differ from libaom, the AV1 reference implementation?

libaom (also from Alliance for Open Media) is the reference encoder and decoder for AV1, the previous-generation codec. AVM is its successor: it implements the AV2 codec specification, which targets higher compression efficiency than AV1. The two share a similar CMake-based build system and C codebase structure, but their bitstreams are not compatible with each other.

What is the difference between the main branch and the av2-enc branch?

The main branch is AVM's stable, thoroughly tested branch. The av2-enc branch is an active development branch focused on encoder optimization work and is generally ahead of main in encoding performance, but may be less stable. AOMedia periodically merges improvements from av2-enc into main after more thorough testing. For conformance testing and reproducible results, build from main.

Does using AVM in a product require a separate patent license from AOMedia?

The BSD-3-Clause-Clear license permits building, running, and distributing AVM with attribution, but grants no patent rights to the AV2 codec itself. Research and conformance testing use does not typically trigger commercial patent obligations, but shipping a product that encodes or decodes AV2-compressed content at commercial scale may require engaging with Alliance for Open Media's patent licensing program. Review aomedia.org's licensing terms and confirm with legal counsel before production deployment.

Is AVM suitable for real-time video encoding?

No. AVM is a reference implementation optimized for bitstream correctness, not encoding throughput. Its encoding speed is slower than production-grade encoders like x265 (H.265) or libaom (AV1). Real-time AV2 encoding will require dedicated hardware encoder support or a production-optimized software encoder, neither of which exists yet. The av2-enc branch contains more recent encoder optimizations, but the gap between reference-quality and production-grade encoding speed remains large.

What are the build prerequisites for AVM on Linux?

On Linux, you need CMake 3.16 or higher, Git, Perl, and either yasm (preferred) or nasm for x86 targets. Python is required for the unit test suite. Building the documentation requires Doxygen 1.8.10 or newer. Most Linux package managers provide all these dependencies. The README walk-through covers the full build: clone the repository, run cmake path/to/avm from your build directory, then make.

also worth a look

Similar open-source tools#

Ffmpeg Skill

Alternative toRendi

FFmpeg skill for coding agents: 42 tools, MCP server, local-first

  • 6,799 GitHub stars
  • MITLicence MIT

Rea Video

Alternative toTwelve Labs

Video reverse-engineering CLI that runs inside AI coding assistants.

  • 9,704 GitHub stars
  • Apache-2.0Licence Apache-2.0

Renderdoc

Alternative toNVIDIA Nsight Graphics

Frame-capture graphics debugger for Vulkan, D3D, and OpenGL

  • 11,320 GitHub stars
  • MITLicence MIT

Slint

Alternative toQt

Cross-platform native UI toolkit for Rust, C++, JS, and Python.

  • 24,599 GitHub stars
  • CustomLicence Triple-licensed: Royalty-free 2.0 / GPL-3.0-only / Commercial (Slint)

Brag

InDesign & Creative

Agent skill that turns any project into a launch video in one command

  • 21,753 GitHub stars
  • MITLicence MIT

Astryx

Alternative toMUI X

Agent-ready React design system with 150+ accessible components.

  • 29,723 GitHub stars
  • MITLicence MIT
by category

Open source tools in these categories#

145

Design & Creative

ComfyUI, Excalidraw, Godot Engine
673

Developer Tools

REA (Reverse Engineer Anything), Skills for Real Engineers, superpowers

Sponsors

Inbox Zero

Alternative toSuperhuman

AI email assistant that drafts replies and clears your inbox

  • 13,058 GitHub stars
  • AGPL-3.0Licence AGPL-3.0
  • #Email

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

  • 8,913 GitHub stars
  • Apache-2.0Licence Apache-2.0
  • #AI Agents

SnitchFeed

Live monitoring on LinkedIn, X, Reddit & more. Agentic social listening for startups.

Marketing & Growth

Advertise your product

New open source projects by email

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

/
  • Claude Code to OpenCode
  • Jira to Windshift
  • Notion to AppFlowy
  • Slack to Mattermost
  • Linear to GitLab
  • Wispr Flow to Handy
  • Arc to Zen Browser
  • CapCut to Concat
  • Grok Bot to rakazo
  • Superhuman to Inbox Zero
  • Discord to Stoat
  • Airtable to AITable
  • Datadog to SigNoz
  • Muse to OpenClaw
  • Railway to Coolify
  • GitHub Copilot to Cline
  • Confluence to Wiki.js
  • Microsoft Teams to Rocket.Chat
  • 1Password to KeePassXC
  • Firebase to Supabase
  • Pinecone to Qdrant
  • Zapier to n8n
  • Devin AI to OpenHands
  • Asana to Leantime
  • Claude Code to OpenCode
  • Jira to Windshift
  • Notion to AppFlowy
  • Slack to Mattermost
  • Linear to GitLab
  • Wispr Flow to Handy
  • Arc to Zen Browser
  • CapCut to Concat
  • Grok Bot to rakazo
  • Superhuman to Inbox Zero
  • Discord to Stoat
  • Airtable to AITable
  • Datadog to SigNoz
  • Muse to OpenClaw
  • Railway to Coolify
  • GitHub Copilot to Cline
  • Confluence to Wiki.js
  • Microsoft Teams to Rocket.Chat
  • 1Password to KeePassXC
  • Firebase to Supabase
  • Pinecone to Qdrant
  • Zapier to n8n
  • Devin AI to OpenHands
  • Asana to Leantime