Bloat Libvpx May 2026

./configure --size-limit=640x480 --enable-small --enable-small trades speed for size. It disables loopfilter optimizations and reduces memory overhead. For embedded decoding, this is often invisible to the user. Yes and no.

--disable-vp8-encoder --disable-vp9-decoder When cross-compiling, specify exactly the architecture: bloat libvpx

We aren't talking about malware. We are talking about feature creep . Yes and no

The problem isn't Google's code. The problem is that the open-source ecosystem has standardized on a as the default. We need better documentation for "embedded" or "minimal" profiles. The problem isn't Google's code

If you are just decoding video (not encoding), consider dav1d for AV1 or ffmpeg with --enable-libvpx --disable-everything . But that is a story for another day.

./configure --disable-runtime-cpu-detect --enable-static This tells the compiler: "Don't write the dispatcher. Just write the code for the CPU I am sitting on." This can cut binary size by 30-40%. Don't need VP8? (You probably don't; you want VP9). Or vice versa? You can't fully disable one easily, but you can reduce features:

From the perspective of a desktop Linux user: libvpx is lean, fast, and necessary. The "bloat" is actually future-proofing .