Looking back on 25 years of code, collaboration, and quiet, but massive impact.
Illustration by Lluc Pallejà of squeakycarrot.com
As GPAC approaches 100 million downloads across its ecosystem of tools, we’d like to take a moment to reflect — and thank the people who made it possible: our users, contributors, testers, and long-time supporters.
From the early academic days at Télécom Paris to the growing set of tools used in research, prototyping, packaging, streaming, and browser-based applications, GPAC has always had one core mission: to give developers high-quality, efficient, and modular building blocks for multimedia workflows.
What’s in the 100 Million?
The number includes cumulative downloads across:
- The core GPAC framework
- MP4Box, our popular MP4 multiplexer/demultiplexer
- MP4Box.js, used in browser environments
- Other associated GPAC tools and libraries available via GitHub, npm, and other repositories
We know download numbers don’t tell the whole story. Open-source software is widely reused, embedded, and adapted — sometimes anonymously. But when a project like GPAC crosses a milestone like this, it’s a signal of sustained interest, real-world use, and global relevance.
🌍 Where GPAC Shows Up
While we don’t always know who our users are, we’ve seen GPAC show up in:
- Academic research papers, standardization contributions and student projects
- Streaming architecture experiments
- Streaming media workflows as used by Netflix with the help of Motion Spell
- Browser-based applications using MP4Box.js
- Open-source media toolkits and larger software stacks
We welcome this diversity. It keeps the project grounded, evolving, and truly open.
The upcoming GPAC release will include new features and refinements based on feedback from our contributors and community — especially in areas like:
- CMAF packaging
- Pro workflows in DRM and Advertising
- Enhanced GPAC Filters documentation
- Browser-based video handling with MP4Box.js
We’ll also continue efforts to make our tools easier to adopt, whether you’re building for experimentation or integrating GPAC into production environments.
Whether you downloaded GPAC once, use it daily, or contributed code, tests, bug reports, or documentation — thank you.
If you’re using GPAC in your work, we’d love to hear about it. You can drop us a note, contribute to the GitHub discussion, or just share a link. Your stories help shape the future of the project.
Here’s to the next 100 million — and to keeping GPAC useful, efficient, and open.
The GPAC team