How the Chroma Key (Green Screen) Tool Works
AnyTool removes a green (or any chosen) screen entirely in the browser using a self-hosted single-threaded ffmpeg.wasm engine — the core (ffmpeg-core.js + the 32 MB wasm) is bundled from npm and served as a same-origin asset, so nothing is fetched from a CDN. The clip is written to ffmpeg's virtual filesystem (MEMFS) and the chromakey filter keys out the chosen color using adjustable similarity and blend, producing a foreground with the screen removed. That foreground is then overlaid onto a background — either a solid color source or an uploaded image scaled to the frame — and flattened to yuv420p for a clean H.264 MP4 read back as a blob. Note: the self-hosted core encodes VP8 only and cannot output alpha, so the tool composites the foreground onto a background rather than exporting transparency. Single-threaded is deliberate: the multi-threaded core needs SharedArrayBuffer + cross-origin isolation (COOP/COEP), which would block cross-origin ad iframes.
- Runs client-side — the video is never uploaded
- Self-hosted ffmpeg core (bundled) — no CDN
- chromakey filter keys the chosen color (similarity/blend)
- Foreground overlaid on a color source or uploaded image
- Flattened to yuv420p H.264 MP4
- Composites onto a background (VP8 core can't encode alpha)
- No backend, no signup, no size cap
