Getting Started
Rive is a real-time interactive design tool that allows you to design, animate, and immediately integrate your assets into any platform.
There are two core parts to Rive: the editor and the runtimes. The editor is where you create your designs and animate them. The runtimes are open source libraries that allow you to load and manipulate your Rive files in Swift, Flutter, Android, JavaScript/WebGL, React, C++, and more (and we're working on more).
The Rive format and runtimes are all open-source and available through the MIT license.
Rive runs entirely in your browser. To get started, first create an account on our website. Once you've registered, you can access Rive by going to Your Files.
Make sure you've verified your account. Check your email for a confirmation link.
Read this manual! At the very least read our frequently asked questions, check out some tutorials, and read about the Rive core concepts.
Follow some artists. This allows you to stay up to date on their latest files and learn from their techniques.
Personalize your profile. Tell your followers who you are by adding a bio and other social links!
Launch Rive by navigating to Your Files. Double click on a file to open it, or click on the plus icon to create a new one.
WebGL is a browser rendering feature that allows Rive to run with desktop-class graphics performance. It comes built-in to all modern browsers and doesn't require any additional plugins. It is required to run Rive.
WebGL is usually enabled by default on most browsers. Occasionally, some configurations have this feature turned off. Read on to find out how to enable WebGL if it's disabled.
Many laptops nowadays have two GPUs: an integrated low-power GPU (to save battery) and a discrete high-power GPU (for maximum performance). The OS will automatically switch between the integrated and discrete GPU to efficiently balance battery life and performance.
A few of our Windows users have noticed that this GPU switching will occasionally cause Rive to crash. It doesn't appear to happen with macOS.
The solution is to make Windows always use the high-performance GPU with your browser. If you're a MacBook user, you may want to make macOS use the discrete GPU purely for performance reasons.
