Publishing — Framer
Publish a Framer site with an Aperveil shader: how it loads, browsers without WebGPU, reduced motion and changing a shader later.
Publishing
The code file carries the shader; the engine that draws it loads from the Aperveil CDN, and Framer bundles it into your site when you publish. A published page draws the shader on its own, with nothing to configure.
- Until the GPU starts, the component shows the shader's ground colour. Where a browser has no WebGPU, it shows the Look's poster instead, without moving the layout.
- It stops drawing while it is out of view or its tab is hidden, and holds still for visitors who ask for reduced motion.
- Keep headings, links and anything a visitor must read in Framer layers, not in the shader.
To change a shader, change its controls in the panel. To take a newer version from aperveil.com, copy it again and replace the code file's contents. Files copied earlier keep working: each names the engine it was made with, and every engine stays on the CDN.
Browser support and performance are the same as on every platform: see browser support & performance.
Color Looks, browser support, performance and access are the same on every platform: see the overview.