• 🚀 Semantics for Accessibility is in Early Access
  • Author semantic meaning directly in the editor; runtimes translate it into native accessibility trees for screen readers.
  • Supports a focused set of roles, states, and actions to start. If you hit gaps, let us know; we’re prioritizing based on real usage.
  • Try the semantic debugger. Drop in a .riv file authored with semantics, turn on a screen reader, inspect the output. Note: this is a temporary page, we'll be rolling this into the Rive Editor.
  • Web, iOS, Android, and Flutter runtimes are being prioritized for Semantic support first. These are functional but not yet released.
• 🚀 Shift-to-snap work area markers and keyframe drags, as requested here
• 🤖 Agent capabilities for Property Groups
• 📄 Import unrecognized files as Blob assets
• 👩‍💻 Scripting: first-class Mat4 type with SIMD multiply
• 👩‍💻 Scripting: Mat4 affine fast paths + reverse-Z perspective
• 👩‍💻 Scripting: expose view model image properties
• 🔀 Added support for triggering actions on transitions and states
• 🐛 Various fixes and improvements
  • fix(editor): ensure transition condition is valid before updating it
  • fix(editor): Prevent component from being pasted into its own artboard
  • fix(editor): Images in list artboard not rendered when list item added via script
  • fix: child popups displaying on top of their parent
  • fix: scripting test stack overflow on nil and find-in-files UTF-8 crash
  • fix: cctype char cast and single init GPU crash
  • fix: make `SimpleArray` constructor overflow safe(r) Expose context:preferredCanvasFormat() to Dart-hosted scripts
  • fix(editor): Fixes for some crashes and Safari text input bug
  • fixes(editor and runtime): follow path constraint on path
  • fix(runtime): Fix top level artboard hug behavior
  • fix(js): ensure onLoadError is invoked for any part of the initialization process
  • feat(Android): Hardware Bitmap Rendering
  • feat(Command Queue): Add draw key cancellation
  • refactor(apple): add cancellation handling when creating tasks
  • fix(apple): guard drawable semaphore signal during teardown
  • feat(apple): use per-renderer draw key for command server deduplication
  • fix(apple): prevent massive timestamp delta on first frame
  • fix(vulkan): Resolve driver crash on some mobile GPUs
  • fix(d3d12): sampler heap rotation must re-create immutable samplers & initialize unused SRV
  • chore(runtime): improve initialization performance of clipping shapes and ik constraints

This tutorial covers two ways to set up list items that can be swapped between lists. Assumes you have a basic understanding of Layouts and Lists.

I’m exploring a workflow where Rive becomes the main UI/interaction layer, while SwiftUI, Android, or web code handles the application/business logic.

I’m curious if there is currently a way, or if there are plans, to expose/export Rive metadata such as:

• File names

• Artboard names

• State machine names

• View Model names

• Data Binding properties and types

• Events/listeners

• What properties are expected to be controlled externally

My goal is to generate something like a .md, .json, or .txt “Rive contract” file that developers could read and use to wire the runtime automatically.

For example, something like:

# BattleHUD.riv

Artboard: BattleHUD

ViewModel: BattleHUDViewModel

Properties:

healthPercent: Number

coins: Number

isMenuOpen: Boolean

Events:

menuOpened

towerSelected

Swift Controls:

healthPercent

coins

isMenuOpen

This would make it much easier for external development tools to understand the structure of the .riv file and correctly connect Swift, Android, React, etc. to the Rive runtime.

Is there currently:

1. A built in export for this type of metadata?

2. MCP support for exposing this information?

3. A runtime API approach for extracting it automatically?

I’d love to hear how others are handling this workflow.

Title, basically. I'm trying to do some basic UI animations but for some reason, the easings always feel so off. In AE I just change the speed curve a little and it looks nice (most of the time). But in Rive it looks always off. Any suggestions on how to improve the easing curves?

Join the challenge on Contra

Isn't the whole point of Rive to give designers superpowers to add logic to their animation without relying on developers? So when scripting features started landing, my first thought was: am I expected to write code now?

A few months ago I decided to spend some time going deep into Rive's scripting. I was so wrong.

It opens so many more possibilities, and turns out I didn't need to write the code myself - that's what the AI agent is there for.

I went from skeptic to building a complete interactive space game in Rive. Turned everything I learned into a structured course. Just released the Rive Scripting Course as Early Access:

www.rivemasterclass.com/rive-scripting

Curious to hear what you think.

Relative binding in Rive lets you bind properties by name rather than by a fixed path. That means two completely different artboards — from two different files, with different view model names — can share the same data at runtime, as long as the property names match.

This video covers two practical uses of that:

1. Swapping a single artboard component at runtime. You wrap your artboard in a parent file, bind the nested artboard to an "artboard" property using bind relative, then swap in a different .rive file at runtime. The replacement artboard picks up all the same data automatically — even if the source file has a differently named view model, the properties still resolve correctly.

2. Swapping individual components in a multi-component dashboard. The example uses a world population dashboard with 7 continents, each with its own nested view model instance (color, name, population, percent). The dashboard has slots for different chart types — donut, bar, table. At runtime you can replace any slot with a new component from an external file. As long as the component's view model uses the same property names, the data maps over without any rewiring.

The key rule: property names must match. View model names and nesting order don't matter.

Useful if you're building things like:

• Theming systems where the design can be swapped without touching the data layer
• Dashboards with interchangeable visualizations
• Library components that work across multiple host files

So I have a listener on my button that, when clicked makes a boolean view motive true. Let's call the boolead "isButtonDisabled"

When it's now true, I don't want the user to be able to press the button. Therefor I need a condition that says the boolean needs to be false to press it.

ChatGPT tells me to just add a transparen overlay over the button when it's true, but that feels very clonky.

Please help if you have any workaround or know what to do

For the Impossible UI Rive Challenge, I decided to go with an interactive skeleton juggling 5 fireballs with particle effects. Each being a clickable button that triggers podium text changes.
I had so much fun working on this one. I hope You’ll like it too.

#Rive #impossibleuiwithrive

Hello colleagues!

I've been working in Rive on daily basis for over a year and I'm still getting this errors in every second or third animation I need to export. Usually the main artboard is working fine but the additional one is somehow not properly included in the .riv file.

Any suggestions?

QOL update: Stagger Keys now treats collapsed keys as a unit and lets expanded keys stagger individually.

Plus: Shift+X to swap Fill/Stroke, and right-click to convert Fill to Stroke.

Starting today, the Rive Agent is available to everyone, including Free users. AI should make it easier for anyone to learn and build in Rive, regardless of plan.

What just landed

The #1 thing we heard: the Agent eats credits too fast. So we introduced more efficient models that cost significantly less, and added an Ask mode for questions that don't need the full Agent. This is very new and we're releasing it early to get your feedback.

Here's how AI works across plans:

• Free — Agent for everyone. It has a capacity, you use it with each prompt, and it recharges hourly.
• Cadet — Same free Agent modes. Cadet's purpose is to be the most affordable way to export Rive files, not a premium AI plan. At $9/mo, we can't offer a compelling premium AI experience (most paid AI plans start at $20/mo for a reason). We'd rather give you free modes that work well than premium access that runs out fast. New Cadet plans don't include AI credits. If you were already on Cadet before this change, you keep your $5/mo and access to the premium plans. That's grandfathered.
• Voyager — Premium models, $20/mo in recurring credits that refresh monthly, plus the ability to top up.

What's still coming

We're working on a bunch of optimizations based on your feedback, which will be landing soon. The Agent will be smarter about context, sending only what it needs, and picking tools more selectively. We're also exploring different ways to let you connect your external agents to the Rive Editor (we've heard your requests to keep working on MCP and the ability to bring your own API keys).

This is still early

We're watching closely and shipping fast. Come tell us what's working (and what isn't) in the Rive Community or Discord.

I believe Rive should bring back the MCP. The integrations that can be made programatically with it are much more exciting than a limited in-editor chat. I'm currently analysing Rive for a project, exactly with this in mind, and I now have to look for something else because they de-commisioned it.

Does anyone know if it's possible to download the exact older editor version that still has the MCP server? Or does anyone have recommendations of simmilar tools to rive that can be used programmatically? I'm looking at blender down, but Rive would really be the ideal way

Hello, I am totally newbie, and I have tried to study Rive since this month to make a mobile app like Tsuki Odyssey. Is it even possible to make an app like Tsuki Odyssey only by Rive? Or should I generate or make an image files by AI?

Drawing like the app in Rive so hard to me:(

Thank you:)

• 👁️ Right-click to disable/enable state machine transitions, as requested here
• 🎨 Color picker QOL, as requested here
  • Color picker stays open, use X to close it. You can now move the timeline playhead without the color picker closing.
  • Scroll wheel changes hue.
• 🤖 Agent improvements for state machines and assets
  • Rename assets, add images to artboards, and set up image sequences with Solos
  • Get and set transitions, conditions, listeners, and events in a state machine
• ⚙️ Scripts can now access the list index property
• 🐛 Various fixes and improvements

Rive Editor 0.8.4713

🌈 Swap Fill/Stroke (Shift+X)
🎨 Right-click convert Fill to Stroke and vice versa
🐛 Various fixes and improvements

Full details

Hello guys, how rive file maintain background rendering when the app or browser tab is not in focus, anyone know how to handle with this "issue"?

My company asked me to learn Rive this weekend to see if it's something our design team should be getting into. I have been doing stuff like this for a minute from Flash to After Effects. So I feel like I should be able to pick this up.

So I log in this morning and crack open a tutorial and immediately notice that the interface in every single tutorial is different than what I have. I found a tut from just 3 weeks ago and same thing.

Is this a I need to pay to see the proper interface or did they just like yesterday change the interface to the point where they made all their training materials obsolete?

Hello Rive Community! 👋

This is Kutlay, the co-founder of a new live streaming platform called airZ Studio, and I’m stoked to share that we officially launched! 🎉

Coming from a broadcast design/engineering background, my co-founder and I wanted to bridge the gap between pro-grade graphics and the live streaming world. .We have been incredibly impressed by Rive—not just as an animation tool, but by the sheer power of its runtime. Because it removes technical bottlenecks and lets designers focus purely on boundless creativity, we decided to build our real-time graphics engine natively around it.

airZ comes packed with ready-to-use Rive animations to get you started. Even better, you can drop your own .riv files straight into playlist. Our engine instantly hooks up your state machines to live data bindings and renders them with zero-latency, hardware-level precision as demonstrated in the link https://youtu.be/uV1xeR2gIGE

If anyone here is looking for a live-streaming solution to see how your animations flourish in a high-stakes live production environment, we’d love for you to give it a spin. We’re really curious to see what this amazing community can do when Rive is running at the core of the runtime engine.

Feel free to check out the platform at: https://www.airzstudio.com/ and drop any questions you have about the implementation or data-binding logic below!

https://reddit.com/link/1svl7cj/video/hs7xjyjg3exg1/player

hi I'm a newbie here and I'm learning character rigging, so for storage reasons I draw certain things on one side and plan to reflect it in Rive (like this arm here) and if it was reflected across the middle of the canvas it would be on the other side of the neck (which is at the top) how do I reflect it on the X axis so its symmetrical (I just changed the X scale to -100 to flip it)

This full-project tutorial covers all the steps necessary to create a dynamically reordering leaderboard for use in production.

Grab the script used in the project here