Rive Inspector

Open any .riv file in your browser and inspect everything inside it — artboards, state machines, events, and every View Model Instance (VMI) data-binding property — live, while the animation plays. Free, no account, nothing uploaded.

Inspect a .riv file now — free, in your browser →

What the Rive inspector shows

Inspect, don't just preview

Most .riv tools play the animation and stop there. An inspector goes further: it shows the runtime API surface of the file — what your code can actually read and write once you ship it. That matters the moment a designer hands you a .riv and you need to know what the view model exposes, which events fire on each transition, and whether the file you received matches the spec you agreed on.

Because you can mutate values live — toggle a boolean, fire a trigger, set a number or color — you can verify behavior in seconds instead of wiring up a test harness in your own app first.

How to inspect a .riv file

  1. Go to rive.best — the inspector loads instantly, no sign-up.
  2. Drag your .riv file anywhere onto the page, or click the dropzone to browse.
  3. Pick an artboard and a state machine from the sidebar.
  4. Read and mutate every VMI property while the canvas renders, and watch the event log as states change.

Private by design

The file is parsed by the Rive WebAssembly runtime inside your browser. Nothing is uploaded to a server unless you explicitly create a share link, there is no account, and closing the tab leaves no copy anywhere. Client confidentiality, NDA work and unreleased designs are safe to inspect.

Frequently asked questions

Can I inspect a .riv file without the Rive editor?

Yes. Drop the .riv into the rive.best inspector and it lists the file's artboards, state machines, events and every View Model Instance property — no Rive editor, account or install required. The file is parsed by the Rive WebAssembly runtime directly in your browser.

What is the difference between a Rive viewer and a Rive inspector?

A viewer plays the animation. An inspector also exposes the file's runtime API surface: which state machines and inputs exist, what events fire on each transition, and which data-binding properties the View Model Instance exposes — the things your code interacts with when you ship the file.

Does inspecting change my .riv file?

No. The inspector mutates values in memory at runtime so you can test behavior, but the .riv file on disk is never modified — and nothing is uploaded unless you explicitly create a share link.

Open the Rive Inspector →