Compare two .riv files
Load two .riv versions and diff them — see which
artboards, state machines and
View Model Instance properties were added, removed or changed. Catch breaking
changes before they reach your app. Free and client-side.
Catch breaking changes between Rive versions
A .riv file is the contract between a designer and your code: your app reads
View Model Instance properties, fires triggers and listens to
state machines by name. When a new export renames a property or drops an input, the animation still
"looks fine" but your integration breaks. A Rive diff makes those changes visible
before you ship.
What the comparison shows
- Artboards added or removed between the two files
- State machines and their inputs that changed
- View Model Instance properties — added, removed or renamed, by type
- A clear side-by-side of the runtime API your code actually integrates against
How to compare two .riv files
- Open rive.best and open the Compare panel — free, no install.
- Drop your old and new
.rivversions; both are parsed locally in the browser. - Review the diff of artboards, state machines and View Model properties between them.
Built for designer→developer handoff
Comparing files pairs naturally with the rest of rive.best: open either version in the viewer, drill into its data binding with the inspector, or test transitions in the state machine viewer — all without leaving the browser.
Frequently asked questions
Can I diff two versions of a Rive file?
Yes. rive.best loads two .riv files and compares their runtime API — artboards, state machines and View Model Instance properties — highlighting what was added, removed or renamed between versions.
Why would I compare two .riv files?
When a designer ships a new export, the data-binding API your code depends on can change silently. Comparing the old and new file catches renamed or removed View Model properties, state machines and inputs before they break your app.
Are the files uploaded when I compare them?
No. Both .riv files are parsed by the Rive WebAssembly runtime in your browser; nothing is uploaded unless you explicitly create a share link.