A JavaScript/TypeScript and Web Assembly (WASM) runtime library for Rive.
This library allows full control over Rive files with a high-level API for hooking up many simple interactions and animations, as well as a low-level API that allows you to drive your own render loop to create multiple artboards, animations, and state machines all in one canvas.
- ⭐ Rive Overview
- 🚀 Getting Started & API docs
- 🔍 Supported Browsers
- 🧵 Threads and the replay worker
- 📚 Examples
- 🏃 Migration Guides
- 👨💻 Contributing
- ❓ Issues
Rive is a real-time interactive design and animation tool that helps teams create and run interactive animations anywhere. Designers and developers use our collaborative editor to create motion graphics that respond to different states and user inputs. Our lightweight open-source runtime libraries allow them to load their animations into apps, games, and websites.
🏡 Homepage
Follow along with the link below for a quick start in getting Rive JS integrated into your web applications.
For more information, see the Runtime sections of the Rive help documentation:
Rive can be used in all major browsers. We're constantly working to improve performance with our renderer so that animations playback smoothly for all.
@rive-app/webgl2-threads loads a threaded build on pages that are cross origin isolated. There, instances created with enableGPUCanvas: true hand their canvas to one worker shared by every instance on the page: each frame advances and records on the page's thread while the worker replays the previous frame on the GPU, so the two no longer add up on the page's thread. This is on by default wherever the browser can draw WebGL2 on a transferred OffscreenCanvas.
- Turn it off for the whole page with
RuntimeLoader.setReplayWorker(false)before the runtime loads, or for one instance withuseReplayWorker: false. Both keep replay on the page's thread, as do builds without threads, pages that are not isolated, and browsers without WebGL2 onOffscreenCanvas. - A canvas handed to the worker stays with it. Setting its
widthandheightproperties still resizes it (the browser owns its attributes from then on), but the page can no longer get a context from it, and any later instance on that canvas renders through the worker too, reusing the same WebGL context. - Images in those files decode on the worker, off the page's thread.
- The page records at most two frames ahead of the worker and skips a frame rather than queue more; the next frame advances by the time skipped.
Check out some of the demos using this JS/WASM runtime in the Rive documentation.
For even more examples and resources on using Rive at runtime or in other tools, checkout the awesome-rive repo.
Using an older version of the runtime and need to learn how to upgrade to the latest version? Check out the migration guides below in our help center that help guide you through major version bumps; breaking changes and all!
We love contributions! Check out our contributing docs to get more details into how to run this project, the examples, and more all locally.
Have an issue with using the runtime, or want to suggest a feature/API to help make your development life better? Log an issue in our issues tab! You can also browse older issues and discussion threads there to see solutions that may have worked for common problems.