RIV→REV
Runs in your browser · no sign-up · nothing uploaded

Online .riv → .rev converter

Rebuild a Rive runtime animation (.riv) into an editor project (.rev): play the original animation first, then review a per-category inventory — artboards, vector paths, fills and strokes, timeline keyframes, state machines, embedded assets, constraints and data bindings — and download the editable .rev. All of it stays on your machine.

Drop your .riv file here

One file at a time · or click to browse

Choose a .riv file

Loading format dictionaries…

Preview before you convert

The uploaded file plays locally with Rive’s own runtime: switch artboards, timelines and state machines, drive bool/trigger/number inputs, and confirm it is the animation you meant.

A counted inventory, not marketing copy

Artboards, paths and vertices, fills and strokes, keyframes and easing, states and transitions, embedded assets, constraints and bindings — every figure comes from this file’s object stream.

Every reference is re-targeted

.riv addresses objects by list ordinal, .rev by object-id pair. Each reference is resolved through the rive-cpp containment model before rewriting; a 110k-object project takes about 3 seconds.

Reproducible and embeddable

Byte-identical to the Python reference across 26 samples (images, audio, scripts, nested components). The converter itself has no third-party runtime, so it can be self-hosted or dropped into your own pipeline.

Three steps back to an editable project

  1. 01Tick the authorisation box, then drop in the .riv from the Rive community or a live project — one at a time.
  2. 02While it parses, use the local preview: switch artboards, timelines and state machines and drive them live.
  3. 03Check the inventory, download the .rev and drop it into the rive.app editor to keep working; export a fresh .riv afterwards and repeat.

Under the hood: .riv and .rev share the same property keys, but Id, FractionalIndex and double use different wire encodings, and the editor-only fields are synthesised from parent and list structure.

Buy an activation key

Converting and previewing cost nothing; the editable .rev download needs one activation key. Keys are delivered the moment you pay — paste it into the unlock box and download.

Keys bind to this browser; paste the same key again on another machine.

FAQ

Are my files uploaded anywhere?

No. Decoding, re-encoding and previewing run entirely inside your browser; the page never sends file contents to a server. Only the format dictionaries (about 100 KB gzipped) and the MIT-licensed preview runtime (about 2.7 MB) are fetched once, then cached.

Why do I have to confirm authorisation first?

A .riv is often someone else’s published runtime artefact, and decompiling or re-editing it can touch their copyright and asset licences. The box records that you own the file or hold permission to modify and restore it — a precondition for using this tool, and the kind of record you want when the result feeds a commercial project.

What survives the conversion?

The layer tree and parent-child links, shapes, fills and strokes, bones and skin weights, every timeline and keyframe (including easing curves), state machine states, transitions and inputs, embedded fonts and images, and constraint and data-binding references. They come back as editable objects rather than being baked into bitmaps.

What is unrecoverable by definition?

Three things: layer lock flags, state-graph node coordinates, and component library publication links (which library, which version). Runtime files never export them, so no tool can conjure them back; this page rebuilds them with defaults — unlocked, laid out by topology, component-ness inferred from nesting.

Which Rive versions are supported?

Verified on runtime 6.x and 7.x files, including a 110k-object project. Output is pinned to editor format v7.1 / schema 32, so open it in a recent Rive editor (web or desktop 0.9+).

How do I open the resulting .rev?

Drop it straight into the rive.app editor window, or use File → Open in the desktop app. It is an ordinary project from then on: edit, save-as, collaborate.

Why is the .rev bigger than the .riv?

A .rev is a project snapshot: besides runtime data it writes object id pairs, sibling order, timeline back-references and state-graph coordinates — usually 30%–80% larger. Those fields are exactly what makes it editable.

Can I use this commercially or self-host it?

The converter has no server dependency: host the folder on your own domain and it runs offline. The Rive web runtime used for previewing is MIT licensed, so keep its copyright notice when redistributing. Output belongs to your project — just make sure you hold the rights to the source file.

Why do downloads need a key?

Converting and previewing stay open; downloading the editable .rev takes a one-off key or a plan. Payment delivers a key instantly — paste it into the unlock dialog to download. Keys bind to this browser on activation, and single-use keys are consumed once the download runs.