Browser support

Mixture runs entirely in your browser: the editor, the effects, and the final MP4 export all happen on your machine, with nothing uploaded to render. That buys speed and privacy, and it costs one thing — the browser has to be modern.

The short version

• Chrome or Edge on a desktop or laptop is the best-supported path — everything works, including export with audio.
• Recent Safari (26+) and recent Firefox pass the capability check too; older versions don’t.
• Phones and touch-only tablets aren’t supported. The editor is built for a large screen and a precise pointer. (A tablet with a mouse or trackpad attached counts as desktop.)

What Mixture actually needs

Four browser capabilities, each load-bearing:

Capability	What it powers
WebGPU	Effects, filters, shaders, and glass rendering — in preview and export
WebCodecs video decoding	Video playback and frame-accurate scrubbing in the editor
WebCodecs H.264 encoding	The video track of your MP4 export
WebCodecs AAC encoding	The audio track of your MP4 export

None of these has a real fallback: without WebGPU, effects would silently vanish from your output; without WebCodecs, video layers and export can’t run at all. That’s why the editor checks rather than hopes.

How the check works

When the editor loads, Mixture probes the actual APIs in your browser — it never guesses from the browser’s name or version string. If something’s missing, you get a plain list of what and why, instead of an editor that half-works. There’s a “continue anyway” escape hatch for the curious, but what breaks past that point is what the list said would break.

Note

If your device can’t encode at your composition’s full resolution, that’s handled separately — export falls back to the largest size your hardware can encode and says so, while the project keeps its real dimensions. See Export your video.

Machine spec (an honest estimate)

There’s no hard system requirement beyond the capabilities above — the check is the real arbiter — but as a practical estimate, based on what the engine actually does (1080p/60 canvas rendering, GPU effect passes, and hardware-accelerated encode/decode through WebCodecs):

• Comfortable: a laptop or desktop from roughly the last five years — Apple Silicon Macs, or a Windows/Linux machine with a recent integrated or discrete GPU — with 16 GB of RAM. Smooth editing and full-speed 1080p exports, including several video layers at once.
• Workable minimum: hardware H.264 support and a WebGPU-capable GPU (most 2017+ machines), with 8 GB of RAM. Editing works; heavy multi-video projects and exports will be slower, and export may step down its resolution on weak encoders (your project keeps its real size).
• What actually strains it: many simultaneous video layers, 4K sources, and long compositions — RAM and the video decoder are the bottlenecks, not the canvas.

Agents and headless rendering

Agent-driven headless exports run in real Chrome for the same reason you should: the bundled test builds of Chromium lack the AAC audio encoder, so renders from them come out silent.