Rive State Machine Viewer

Open a .riv file and watch its state machine run live — fire triggers and inputs, follow every transition in a tailing event log, and debug behavior in your browser. Free, client-side, and no Rive editor required.

Test a Rive state machine now — free →

See state machine transitions as they happen

A Rive state machine decides which animation plays based on inputs — booleans, numbers and triggers — plus data-binding values. When a file misbehaves after export, you need to see which input fired which transition. rive.best runs the state machine with the official Rive runtime and streams a live event log of StateChange, Play, Loop and custom Rive events, with a regex filter to cut the noise.

Why not just use the editor preview?

The Rive editor previews the file as you design it, but it can't show you how the exported runtime build behaves once your code starts setting inputs and binding data. This viewer opens the shipped .riv the way a real runtime does — auto-binding the default View Model Instance — so what you test is what your users get.

How to view and debug a state machine

  1. Open rive.best — free, no sign-up or install.
  2. Drag your .riv file onto the page; nothing is uploaded.
  3. Pick the artboard and state machine from the sidebar.
  4. Fire triggers and inputs and watch the event log and current state update as transitions fire.

Drive transitions with inputs and data binding

Classic state-machine inputs and modern View Model Instance data binding are both exposed: toggle a boolean, set a number, fire a trigger, or change a bound property, and confirm the transition behaves as designed. Pin the inputs you care about to a watch list so you can keep an eye on them while the machine runs. It's a full Rive inspector as well as a state-machine viewer.

Frequently asked questions

Can I preview a Rive state machine without the editor?

Yes. The official Rive web preview focuses on animations; rive.best runs the exported state machine in the browser and shows a live event log of every StateChange, Play, Loop and custom event — so you can verify transitions without opening the Rive editor.

How do I debug a Rive state machine?

Load the .riv, pick the artboard and state machine, then fire triggers and flip boolean and number inputs while watching the tailing event log with a regex filter. The current state is shown and updates as transitions fire, so you can pinpoint which input caused which transition.

Can I see which state is currently active?

Yes. The viewer surfaces the latest state change and a running history of transitions, so you always know the active state and how the machine got there.

Does it support data-binding inputs and View Model properties?

Yes. Alongside classic state-machine inputs, rive.best lists every View Model Instance data-binding property and lets you mutate it live, so you can drive transitions through data binding too.

Open the Rive state machine viewer →