Browser compatibility
Which browsers run Axion, what each needs, and why latency differs across browser and OS — plus when to reach for Bridge or Desktop.
Axion is browser-native: the whole rig — DSP, UI, presets — runs locally in your browser via WebAssembly, with no install. That works across every modern browser, but performance (especially latency) varies a lot by browser and operating system.
Supported browsers
- Chrome / Edge (Chromium) — recommended. Best performance and the lowest in-browser latency.
- Firefox — fully supported; latency is typically higher than Chromium.
- Safari 16.4+ — supported. Older Safari lacks the audio APIs Axion needs.
Under the hood Axion needs WebAssembly, the AudioWorklet API, and a cross-origin-isolated context (for the shared-memory audio path). Axion serves the right headers automatically; you don't have to configure anything.
Latency reality
In-browser round-trip depends heavily on the platform:
- macOS + Chrome is the sweet spot — roughly 5–13 ms with a decent interface.
- Windows browsers sit much higher (shared-mode audio), often 50–60 ms+.
- Firefox / Safari are generally higher than Chrome on the same machine.
If you're on Windows and that latency is too high for live playing, you have two native options that bypass the browser audio path:
- Axion Bridge — free Windows helper; keeps the rig in your browser but moves audio natively (WASAPI exclusive).
- Axion Desktop — the Pro native app, with ASIO for the lowest latency of all.
NOTE The browser figure is the round-trip *through the browser's audio stack*. Bridge and Desktop sidestep it — Desktop with ASIO reaches single-digit milliseconds on Windows where the browser can't.
Mobile
Axion loads and plays on modern mobile browsers (recent Chrome on Android, Safari on iOS), but mobile has far less real-time headroom than a laptop. Light rigs work; the heaviest pieces — especially full-size NAM captures — may not run glitch-free on mid-range phones. If a NAM stutters on mobile, try a lighter "feather"/Lite capture, or stick to the analytical amps.
Getting the best out of it
- Use Chrome or Edge for the lowest in-browser latency.
- Use wired headphones or monitors — Bluetooth adds tens of milliseconds and defeats the point.
- A decent USB / Thunderbolt interface matters more than the browser; built-in laptop audio is rarely low-latency.
- On Windows, reach for Bridge or Desktop when you want live-playable latency.
If something specific isn't working — audio won't start, the interface is missing, crackle under load — see Audio troubleshooting.