What metadata engine does MediaPeek use and is it open source?
Updated
MediaPeek parses media metadata with mediainfo.js v0.3.7, a WebAssembly port of MediaInfoLib v25.10, and the project is open source — its source code, issues, and releases are maintained publicly on GitHub. This matters if you want to know what is actually reading your files and whether you can verify or self-host the tooling.
The metadata engine
MediaPeek's "Metadata engine" section states the parsing stack directly:
| Component | Version | Role |
|---|---|---|
| mediainfo.js | 0.3.7 | WebAssembly port of the MediaInfo library |
| MediaInfoLib | 25.10 | Underlying metadata parsing library |
| WebAssembly | — | Runtime that executes the parser |
The practical consequence: metadata analysis runs in WebAssembly rather than on a remote server. Combined with MediaPeek's partial-fetch design, the app reads only the byte ranges it needs from a URL and parses them locally in the browser. For example, if you point it at a large video file, it does not need a full download to report codec, resolution, or bitrate information.
MediaPeek credits the library explicitly: mediainfo.js is a WebAssembly port of MediaInfo, copyright (c) 2002–2026 MediaArea.net SARL.
Open source and maintenance
The site describes MediaPeek as "built in public, maintained on GitHub." From the project page you can:
- Browse the source code repository
- Review open issues
- Track releases
- Follow ongoing development
That gives you a way to check how the WebAssembly parsing is wired up, confirm version bumps, and see whether reported problems are being addressed — rather than taking the engine description on faith.
Third-party badges and trademarks
MediaPeek displays format badges sourced from Apple TV (SD, HD, 4K, HDR, HDR10+) and Apple Music (Lossless, Hi-Res Lossless, Apple Digital Master, Spatial Audio, AAC). The site notes that third-party marks remain the property of their respective owners and are referenced for identification only. Trademark notices cover Dolby (Dolby Vision, Dolby Atmos, Dolby Audio), IMAX, DTS and DTS:X, HDR10+, and AV1 (Alliance for Open Media).
What this means for you
- If you need to verify the parser: the mediainfo.js/MediaInfoLib versions are published, and the GitHub repository lets you inspect the implementation.
- If you care about where analysis happens: parsing is WebAssembly-based, consistent with the browser-side, partial-fetch approach described on the site.
- If you need licensing clarity for badges: the site attributes badge assets and trademarks to their owners; it does not state separate licensing terms for those assets beyond that attribution.