01 / COMPLETE DOCUMENT
GPU Canvas inside .riv
Rive owns the shader, logic and vector composition.
Loading signed .riv…
BOTH FORMATS ARE SUPPORTED. CHOOSE WHAT TRAVELS TOGETHER.
Two export formats. One instrument.
Each of these four instruments is supplied in both forms: a GPU Canvas .riv containing its visual behavior, and a browser bundle pairing an ordinary .riv interface with JavaScript and WebGPU. Use either instrument; linked controls and clocks keep their scene parameters aligned. Both diagrams are native Rive vector paths.
Loading documents…
02 / RIVE + GPU BUNDLE
.riv + JavaScript / WebGPU
Export the Rive interface together with its renderer and application logic.
Loading Rive + external WebGPU…
What travels with the file?
| GPU Canvas .riv | Ordinary .riv + external GPU | |
|---|---|---|
| Inside .riv | Native Rive UI, diagrams, animation, Luau and compiled shader assets. | Native Rive buttons, slider shapes, diagram paths, bindings and animation. No embedded script or shader. |
| What the website provides | Compatible official runtime and the file. Here JavaScript also links controls and supplies optional procedural membrane audio on both routes. | Official runtime, interface file, shader, WebGPU renderer, continuous gestures and application logic. |
| Authoring / signing | Embedded scripts are compiled and signed by Rive before production playback. | This script-free file needs no Rive script signing. Shader compilation happens in the browser. |
| Playback here | Official WebGL2 runtime with GPU Canvas enabled. | Official WebGL2 runtime for Rive, plus browser WebGPU over HTTPS or localhost. |
| Opening only the .riv | The complete visual instrument remains interactive in a compatible runtime. Procedural audio on this page requires its Web Audio bridge. | The interface remains; the GPU scene and host-driven graph updates are absent. |
The signed file is self-hosted and does not contact the signing service during playback. No visitor login is required. The CLI export retains Rive’s watermark. Signing enables compatible runtimes; it does not add support to older runtimes or unsupported devices.
Choose the bundle when an application already owns its renderer, custom data or browser libraries. Choose GPU Canvas when the visual instrument should travel together inside Rive. Both are supported delivery routes in this project; these paired studies demonstrate selected exports, rather than a converter for every possible Rive document. The optical model is the same in either package.
The same scene equations run through different graphics backends. The host compiler guards negative bases of even powers to avoid WebGPU NaNs; other rasterization and precision differences remain measurable. Control materials are composed for each instrument: Liquid spring in Material Nocturne and Resonant Membrane, and Constructive geometry in Spectral Observatory. Native Rive supplies labels and interaction geometry. The membrane phase follows official runtime advance events; the other studies expose their clock through data binding. Scroll horizontally on narrow screens to keep the two routes adjacent.