Browser support & performance — Aperveil docs
WebGPU browser support, fallbacks and performance for Aperveil shaders: secure contexts, reduced motion and how to read the timings.
Browser support & performance
Live rendering requires WebGPU and a secure context. It runs in current versions of:
- Chrome and Edge: Windows, macOS and ChromeOS; Chrome on Android 12 or newer
- Safari 26: Mac, iPhone and iPad
- Firefox: Windows (from 141) and Apple silicon Macs (from 145)
Firefox on Linux, Android and Intel Macs is still rolling it out; there, and wherever a GPU adapter is not available, the fallback takes over. Last checked October 2026.
Browser support alone does not guarantee an available GPU adapter. Aperveil landings use poster fallbacks; most have a poster for each Look, while Glass Reel and Glass Medusae use one shared poster.
Standard Export Kits do not bundle that landing poster. Add your own fallback in the host interface, keep essential content readable without WebGPU and respect reduced-motion preferences.
Start with a sensibly sized surface, avoid unnecessary simultaneous canvases and profile on your target devices. Shader timings are recorded samples, not a promise of frame rate: compare the same resolution, quality and DPR, and test idle and pointer movement separately.