Skip to main content
MigrationUpdated November 20266 min read

Migrating from Rive to ExodeUI

The short answer

Export a .riv file, drop it on /import/rive, and it converts in your browser: shapes, bones, IK, constraints, nested artboards, flex layouts, text and state machines come across. Triggers, booleans and numbers become the same three input types. Data binding, scripting, listeners, draw rules, text modifiers and blend states are not imported yet, so plan to rebuild those by hand.

What matters

  • A .riv file converts in the browser. No upload, no account, no queue.
  • State machines survive with their inputs. Blend states are flattened into plain states.
  • Bones, IK, constraints and nested artboards import. Mesh-heavy character rigs are the weak spot.
  • Listeners, draw rules, data binding and scripting do not import. Budget a rebuild for those.
  • Unity, Unreal and C++ runtimes do not exist here. If you ship into a game engine, stay on Rive.

Why people leave Rive

The reasons are usually practical rather than ideological. Rive is free to build with, but free exports play a Rive splash screen, so shipping anything real means Cadet at $9 per seat per month. Cadet is capped at three seats, and Voyager, where unlimited files and libraries actually start, is $32 per seat per month. Enterprise is $120 per seat per month and is required by their terms once annual revenue passes $10 million.

The second reason is the file. A .riv is a packed binary. You can ship it, but you cannot read it, diff it, review it in a pull request, or fix a value by hand at 2am. ExodeUI stores components as .exode JSON (compiled to .bexode for shipping), so the same file is both the source and the build artefact.

The mapping, input by input

If your Rive file leans on state machines rather than heavy character rigging, the mental model transfers almost unchanged. These are the pieces and where they land.

Rive concept to ExodeUI concept
In RiveIn ExodeUINotes
.riv file.exode JSON, or compiled .bexodeThe JSON version is readable and diffable in git
Trigger inputTrigger inputFires a transition on demand
Boolean inputBoolean inputTrue/false conditions on transitions
Number inputNumber inputDrives blend values, progress and ranges
Text / data bindingText inputData binding itself is not imported: set the value from your code
State machineState machineStates, transitions and conditions import
Blend statePlain stateFlattened on import, so re-add the blend by hand if you need it
Listener (pointer, hover)Object interaction rulesRebuild these; listeners are not imported
ScriptingNode logic and inputsNo scripting layer. Logic is nodes plus state conditions
Bones, IK, constraintsImportedArrives as editable layers, not a flat image
Unity / Unreal / C++ runtimeNot availableRuntimes here cover React, Vue, Svelte, Angular, Solid, React Native, SwiftUI and Flutter

What does not come across

Be specific about this before you commit. The importer measures itself against the Rive renderer on a corpus of 387 open-source rive-runtime test files, and lands close on 238 of them. That is a real number, not a marketing one, and the files it misses are mostly the ones below.

Data binding, scripting, artboard lists, listeners, draw rules, text modifiers, blend states, and layout grid and wrap are not converted. Blend states come through as ordinary states, so the visuals survive but the intensity behaviour does not. Text modifiers and draw rules have no equivalent yet. If your component depends on two or three of these, converting may cost more than rebuilding.

What your code looks like afterwards

The runtime takes the file plus the inputs your component needs, and reports events back to your app. React, Vue, Flutter, SwiftUI, React Native and the others all follow the same shape: one canvas component, one file, inputs in, events out.

React
import { ExodeUICanvas } from 'exodeui';

// toggle.bexode lives in /public
export function Toggle() {
  return (
    <ExodeUICanvas
      src="/toggle.bexode"
      fit="Layout"
      autoPlay
      interactive
      inputs={{ checked: true }}
      onTrigger={(name) => {
        // fires the events you defined in the file
      }}
      style={{ width: '100%', height: 64 }}
    />
  );
}

Nothing is code-generated. The file stays the source of truth, so a designer can change the spring in the editor without a merge conflict in a component file.

What it costs after the move

Rive charges per seat and gates the splash screen. ExodeUI Professional is $5 per month billed yearly, and the Community plan is free. Seat maths is only part of it, though: if you were on Cadet mainly to remove the splash screen from a handful of components, the move pays for itself immediately. If you were on Voyager for libraries and embed hosting, check that you do not need the hosting part, because we do not sell a CDN.

We make ExodeUI, so treat its column as the vendor talking about its own product. The rebuild estimate below is the number most people underestimate.

Then count the rebuild. A state-machine-driven UI component usually takes an afternoon. A character rig with meshes and heavy blend work can take much longer, and may not be worth moving at all.

Published plans, November 2026
RiveExodeUI
Free plan$0, exports play a Rive splash screen$0 Community plan
Entry paid plan$9 / seat / month (Cadet, 3 seats max)$5 / month billed yearly (Professional)
Mid plan$32 / seat / month (Voyager, 25 seats max)—
Enterprise$120 / seat / month, required above $10M annual revenueContact us
Source fileBinary .riv, plus a text source format via their CLIOpen .exode JSON, compiled to .bexode

When you should stay on Rive

Rive is genuinely better for some of this work and we are not going to pretend otherwise. If you are rigging characters with meshes and heavy blend states, Rive has years of tooling we do not match. If your target is Unity, Unreal, consoles or C++, Rive has runtimes and we do not.

Rive also has long-term support agreements and automotive customers, and a stock marketplace. If those are why you picked it, moving is the wrong call. The honest split is that Rive is a graphics and character tool that also does UI, and ExodeUI is a UI tool that does motion and logic.

Questions

How do I move a Rive file into ExodeUI?

Export a .riv file from Rive, open /import/rive and drop it on the page. It converts in your browser, plays with its state machine inputs so you can check it, and you can download the .exode file or open it in the editor. You do not need an account to convert it.

Do Rive state machines and inputs survive the conversion?

Triggers, booleans and numbers come across as the same three input types, along with states, transitions and their conditions. Blend states are flattened into plain states, so the visuals survive but the blending behaviour does not.

What does not convert from Rive?

Data binding, scripting, artboard lists, listeners, draw rules, text modifiers, blend states, and layout grid and wrap are not imported. Our importer runs against a corpus of 387 open-source rive-runtime files and lands close on 238 of them, so test your own file before you commit to a migration.

Is my .riv file uploaded anywhere?

No. The conversion runs in your browser and the file stays on your device. Only a usage count is recorded.

How much does Rive cost compared with ExodeUI?

As of November 2026 Rive is free with a splash screen on exports, Cadet is $9 per seat per month, Voyager is $32 per seat per month and Enterprise is $120 per seat per month. ExodeUI has a free Community plan and Professional is $5 per month billed yearly. ExodeUI does not include a CDN, an asset marketplace or game-engine runtimes.

Is ExodeUI affiliated with Rive?

No. We make ExodeUI. It is not affiliated with or endorsed by Rive, and you should only import files you have the right to use.

Related

Open the editor and try it on your own file

Free Community plan. No credit card. One open .exode file runs in React, Vue, Flutter and more.

Open the web editor
ExodeUI

EXODEUI DESKTOP

A little space for good ideas.

Choose your platform to get the official ExodeUI installer.

Looking for Intel Mac or other builds? Explore the web studio or check all download options.

Prefer the browser? Try for free in your browser →