FFmpeg —
Run arbitrary upstream FFmpeg CLI arguments, stream-copy media, or perform a real libx264 encode entirely in the browser.
Unofficial WebAssembly distroUpstream software,
Upstream software,
compiled for WebAssembly.
Current, reproducible WASM builds of native projects — preserving upstream CLIs where practical, with exact toolchains, capability gaps, smoke tests and source handoff.
catalog v—
ffmpeg — ✓ tracked
libarchive — ✓ tracked
imagemagick — ✓ tracked
libvips — ✓ tracked
ghostscript — ✓ tracked
watcher upstream checking…—tracked projects
—available today
—published variants
—current upstream pins
Release Health Dashboard
A release is healthy only when the whole distribution path works.
Loading release, Registry, workflow, Playground and supply-chain checks…
| Project | Build gate | Release assets | Playground | Freshness | Provenance + SBOM | npm | Overall |
|---|---|---|---|---|---|---|---|
| Loading release health… | |||||||
Live check pendingDistribution health workflow ↗
Cross-browser Compatibility Lab
Real npm operations, tested in three browser engines.
Tested versions and browser engines are recorded separately from build capabilities. Results come from completed main-branch CI, not from a static claim.
| Published npm package | Chromium | Firefox | WebKit |
|---|---|---|---|
| Checking main-branch browser evidence… | |||
Pending verified compatibility results.
Lab workflow ↗
✓ PASS Verified package operation ! UNSUPPORTED Measured missing browser capability — NOT TESTED No current matching result
Results apply to the exact npm package version and profile shown, under the CI test environment. Threaded FFmpeg and libvips require cross-origin isolation (COOP/COEP) and SharedArrayBuffer in production.
Version Gap Dashboard
See exactly how far each WASM build trails upstream.
Loading the latest watcher snapshot…
| Project | Upstream | WASM Zoo | Reference WASM | Gap | Verified |
|---|---|---|---|---|---|
| Loading upstream status… | |||||
Updated automatically by the upstream watcherWatcher workflow ↗
Automation Contract
Candidates can be automated without automating review.
The catalog declares the reviewed candidate boundary. Promotion changes stay review-only; merge, tags, GitHub Releases and npm publication remain human-controlled.
| Project | Candidate mode | Candidate profiles | Promotion path | Promotion rehearsal |
|---|---|---|---|---|
| Loading reviewed automation policy… | ||||
Derived from package manifests in
catalog.json; this is not a live operations monitor.Automation policy ↗Feature Matrix
Native capability is not the same thing as browser capability.
WASM Zoo distinguishes features that are included, deliberately removed, target-inapplicable, optional, or not yet verified.
Loading feature matrix…
✓ Included− Intentionally excludedN/A Browser-inapplicable◐ Optional / platform? Unknown / not tested
Live demos
Use the published cores before integrating them.
libarchive —
Run bsdtar, bsdcpio, bsdcat and bsdunzip against local files using the published browser build and in-memory filesystem.
ImageMagick —
Run the upstream magick CLI for identify, resize and basic PNG/JPEG conversion entirely in the browser.
libvips —
Compare Browser Core and Browser Full, then resize and encode JPEG/PNG/WebP with the pinned libvips browser API.
Ghostscript —
Render local PDF/PostScript files with the upstream gs CLI, including PDF → PNG and PostScript → PDF workflows in a browser Worker.
Why Zoo exists
The difficult part is keeping native software buildable and inspectable.
Upstream tracking
Daily release checks show exactly when a Zoo pin falls behind.
Candidate builds
A new release can trigger an isolated build and real browser smoke test without silently changing the reviewed pin.
Capability diff
Expose what is present, absent, target-inapplicable or intentionally removed instead of hiding it behind a package name.
Reproducible releases
Exact refs, build info, checksums, license notices and matching source travel with the artifact.
Build catalog
Native projects in the Zoo
Loading catalog…
Release contract
A binary is not enough.
01Exact upstream and compiler refs
02Machine-readable feature/build manifest
03Meaningful browser runtime smoke test
04SHA-256 checksums
05License notices and corresponding source
06in-toto / SLSA provenance generated after browser smoke success
07CycloneDX 1.6 SBOM for every published profile