RAV Rive Animation Viewer
Select any chapter below to jump directly to that part of the overview.
-
Standalone Applications
- New
RAV Rive Animation Viewer
Inspect, debug, and test Rive animations on desktop. ViewModel controls, event console, transparency overlay, and standalone export.
$0.00
$0.00
Description
Inspect
Debug
Deliver
01 / Drop
02 / Test
03 / Ship
Open.Inspect.Ship.
The desktop workbench for Rive animations. Load any .riv, drive ViewModels and state machines live, then export the exact code your app needs.
macOS 11+ · Windows 10+ · no web project required
Load any .riv
Bind ViewModels
Drive state machines
Debug every event
Export ready code
Four minutes with RAV
See the whole workflow.
From opening a file to exporting production-ready instantiation code—the main product tour shows the complete path before you install.
The complete runtime view
Your .riv file, finally visible.
RAV connects directly to the Rive runtime and exposes the state behind the animation—without asking you to scaffold a test app first.
Nine live regions · hover with a pointer, tap a region, or use Tab for keyboard focus
Every property, live.
Booleans, numbers, strings, enums, colors, triggers, nested instances, dynamic lists, and state machine inputs—all rendered as working controls.
See what fired and why.
Filter native, Rive user, UI, and MCP events. Search the stream, expand payloads, and use the JavaScript console against the live runtime.
Leave with working code.
Choose the controls to serialize, preserve current state, copy the instantiation snippet, or export a self-contained HTML demo for handoff.
Six serious tools in one
Built for the gap after export.
Rive’s editor is where the animation is authored. RAV is where it gets interrogated, proven, and translated into something the rest of the team can ship.
Touch every value.
RAV reads the ViewModel hierarchy and state machine inputs for you. Change values, fire triggers, switch instances, and watch the canvas respond immediately.
- Nested ViewModels + dynamic lists
- Numbers, strings, colors, enums, triggers
- Artboard, playback, and instance switching
Shape the runtime live.
The CodeMirror 6 editor holds the actual Rive initialization object—not a simplified proxy. Edit it, apply it, and re-instantiate the running file without rebuilding a web project.
- Artboard, state machine, autoBind, and autoplay
- Layout, canvas size, and lifecycle callbacks
- Clear live vs unapplied source indication
See every signal.
The structured event console makes runtime behavior legible. Watch native state changes, authored Rive events, UI actions, and MCP commands arrive in one timestamped stream.
- Native, Rive User, UI, and MCP source filters
- Search, follow mode, timestamps, and copy
- Expandable payloads for event detail
Interrogate the live instance.
Switch the bottom panel into a full JavaScript REPL and execute code against the running Rive instance. Inspect objects, test accessors, and verify assumptions without leaving RAV.
- Expandable object inspection
- Command history and level filtering
- VM Explorer helpers for paths and values
Turn state into code.
Pick exactly which controls belong in the handoff. RAV carries the selected runtime, layout, artboard, playback target, and live values into the output.
- CDN or local package instantiation
- Compact snippet or full scaffold
- Self-contained HTML demo export
Let an agent drive.
The bundled native sidecar gives Codex, Claude, and other MCP clients a direct line into the same runtime session—no screen scraping and no fragile click automation.
- Open files + inspect live structure
- Drive values, playback, and editor code
- Generate snippets + export demos
Agent workflow
Let an agent take the controls.
Watch an MCP client inspect the open file, read live state, drive ViewModel values, and work with the same Rive session you see in RAV.
RAV MCP Demo
See an MCP client inspect and drive the live Rive session through RAV.
The shortest path to confidence
One file in. Proof out.
No starter repository. No debug UI to build and throw away. RAV turns a .riv into a working runtime lab in seconds.
Open the .riv.
Drag in a file or open it from Finder. RAV discovers the available artboards, playback targets, instances, and controls.
Push every edge.
Drive values, fire triggers, switch state, inspect events, change runtime settings, and verify what actually happens.
Export the proof.
Copy production-ready instantiation code or send a standalone interactive demo that preserves the verified state.
The useful details
Small things that save hours.
RAV is a focused desktop utility, but it respects the full complexity of a production Rive file.
Artboard switching
Switch artboards, playback targets, and ViewModel instances without reopening the file.
Dual consoles
Use the structured event log or a JavaScript REPL with timestamps, filtering, and copy.
Live script editor
Edit the Rive initialization object in CodeMirror and apply changes without losing state.
Runtime choice
Test Canvas or WebGL2 against latest, pinned, or custom runtime versions.
State preservation
Reset and reload while preserving artboard, playback, instance, and live control values.
VM Explorer
Inject helper commands for discovering ViewModel paths, reading values, writing controls, and firing triggers.
Flexible canvas
Use auto or fixed pixel dimensions, aspect lock, fit, alignment, and custom backgrounds.
Signed updates
New releases are detected, downloaded, and installed from the in-app update chip.
Before you download
Good to know.
Is RAV really free?
Yes. RAV is free and open source. The AEScripts checkout gives you the current desktop builds and keeps future versions attached to your account.
Which platforms are supported?
RAV supports Apple Silicon and Intel Macs running macOS 11 or later, plus Intel/AMD Windows machines running Windows 10 or later.
Does it replace the Rive editor?
No. Rive is where you author the animation. RAV is the focused desktop environment for runtime inspection, QA, debugging, and developer handoff after the file leaves the editor.
Do I need to know JavaScript?
Not for the core workflow. RAV auto-generates controls for the file and can export the working instantiation code. The live editor and console are there when you want deeper control.
What does the standalone export contain?
A self-contained HTML demo with the .riv embedded, your selected runtime and layout, the current artboard/playback state, and only the ViewModel controls you chose to include.
Know the file before it ships.
Open any Rive animation, expose its live state, test it hard, and leave with something the next person can run.
Free · Open source · macOS 11+ · Windows 10+
Discussions
Want to talk about it?
Head over to r/aescripts to chat with fellow users about this product.
Need Support?
Please open a support ticket to be connected directly with the author of this product
Version History
2.4.2 -
Jul 26, 2026
Changed
Developer ID distribution trust — macOS applications and nested executables are now signed with the IVG Design Developer ID Application certificate, hardened runtime, and secure timestamps instead of an ad-hoc identity.
Notarized direct downloads and updates — Tauri notarizes and staples the app before creating the updater archive; CI separately notarizes and staples each final DMG, then proves the DMG and updater archive contain the same signed app before publication.
Single signed MCP sidecar — Packaged apps now contain only Tauri's signed Contents/MacOS/rav-mcp Cargo binary. The redundant unsigned Resources copy was removed, while development builds create the debug sidecar beside the app executable.
Release safety controls — Release jobs now have bounded timeouts, pinned Actions, non-cancelling concurrency, complete artifact inventory checks, and an explicit draft verification gate before latest.json or the public release can advance.
Version and documentation consistency — Release preparation validates every product version source, the version tooling covers both lockfiles and website metadata, and release documentation distinguishes Apple code signing from Tauri updater signatures.
Website dependency security — Updated Next.js and its ESLint configuration to 16.2.12, with patched PostCSS 8.5.23 and Sharp 0.35.3 resolutions, eliminating all production dependency audit findings in web/.
Fixed
Packaged MCP sidecar discovery — RAV now resolves rav-mcp from the running application's executable directory instead of Tauri's generic executable-directory resolver. This restores automatic MCP bridge startup for packaged macOS apps affected by the 2.4.1 regression and refreshes an existing stable client launcher after an app update.
Gatekeeper acceptance — New macOS installs no longer require users to bypass Gatekeeper by right-clicking Open.
Atomic updater publishing — Manifest generation now refuses to publish unless Apple Silicon macOS, Intel macOS, MSI, and NSIS updater payloads and signatures are all present.
Runaway workflow risk — The automatic repair workflow is manual-only, release runs cannot race each other, and every release job has a maximum execution time.
Developer ID distribution trust — macOS applications and nested executables are now signed with the IVG Design Developer ID Application certificate, hardened runtime, and secure timestamps instead of an ad-hoc identity.
Notarized direct downloads and updates — Tauri notarizes and staples the app before creating the updater archive; CI separately notarizes and staples each final DMG, then proves the DMG and updater archive contain the same signed app before publication.
Single signed MCP sidecar — Packaged apps now contain only Tauri's signed Contents/MacOS/rav-mcp Cargo binary. The redundant unsigned Resources copy was removed, while development builds create the debug sidecar beside the app executable.
Release safety controls — Release jobs now have bounded timeouts, pinned Actions, non-cancelling concurrency, complete artifact inventory checks, and an explicit draft verification gate before latest.json or the public release can advance.
Version and documentation consistency — Release preparation validates every product version source, the version tooling covers both lockfiles and website metadata, and release documentation distinguishes Apple code signing from Tauri updater signatures.
Website dependency security — Updated Next.js and its ESLint configuration to 16.2.12, with patched PostCSS 8.5.23 and Sharp 0.35.3 resolutions, eliminating all production dependency audit findings in web/.
Fixed
Packaged MCP sidecar discovery — RAV now resolves rav-mcp from the running application's executable directory instead of Tauri's generic executable-directory resolver. This restores automatic MCP bridge startup for packaged macOS apps affected by the 2.4.1 regression and refreshes an existing stable client launcher after an app update.
Gatekeeper acceptance — New macOS installs no longer require users to bypass Gatekeeper by right-clicking Open.
Atomic updater publishing — Manifest generation now refuses to publish unless Apple Silicon macOS, Intel macOS, MSI, and NSIS updater payloads and signatures are all present.
Runaway workflow risk — The automatic repair workflow is manual-only, release runs cannot race each other, and every release job has a maximum execution time.
2.4.0 -
Jul 15, 2026
Changed
MCP status clarity — The runtime-strip MCP indicator is green when the bridge is healthy and ready, blue for 30 seconds after agent commands are received, yellow while connecting, red after a bridge failure, and muted when MCP is disabled.
Build and test toolchain maintenance — Refreshed Vite and Vitest to security-patched releases within their existing major versions, and made local build stamps explicitly identify uncommitted worktrees as `dirty`.
Atomic cross-platform releases — GitHub releases remain drafts while Apple Silicon, Intel macOS, Windows, updater signatures, and the merged `latest.json` are built; the workflow publishes only after the complete matrix succeeds.
Visual export command parity — `rav_export_demo_visual` now validates exact selection keys and forwards the dialog's selected controls, CDN/local package source, and compact/scaffold snippet mode to the saved demo instead of exporting with hidden defaults.
Website and reference refresh — Added the static annotated app overview and Script Editor guide, synchronized the MCP reference and machine-readable discovery copies, and documented the reproducible Vercel deployment path.
Fixed
Desktop build dependency alignment — Updated and aligned the Tauri core, build tooling, JavaScript API/CLI, desktop plugins, Rust dependency graph, and declared Rust minimum so local and release builds use one compatible, security-audited toolchain.
Dynamic ViewModel list population — List instances now populate on file load and rebuild whenever their controlling count changes, instead of remaining empty or stopping at the first 10 rows. Authored list entries use readable one-based labels such as `Row 1`, `Row 2`, and so on.
Export and snippet list parity — Standalone HTML demos and generated instantiation snippets now preserve the live player's dynamic list behavior and current row count. List-family selections expand across every current item, while excluded controls such as `focusIndex` stay out of the exported Properties panel and serialized control snapshot.
Single ViewModel instance visibility — The VM Instance selector now remains visible and populated when a file has one default instance, including a one-based fallback label for unnamed instances.
Playback and ViewModel load synchronization — RAV now records the actually playing or detected state machine after load, always populates the VM Instance selector, preserves the runtime's working auto-bound default, and uses a clean `autoBind: false` reload for explicit instance choices.
ViewModel instance export parity — Generated CDN/local snippets and standalone HTML demos now serialize and bind the selected ViewModel instance before applying exported control values, so their playback and triggers match RAV.
Live MCP ViewModel traversal — `rav_get_vm_tree`, `rav_vm_get`, `rav_vm_set`, and `rav_vm_fire` now traverse the currently bound nested ViewModels and dynamically sized lists, expose zero-based paths such as `rows/0/playerName`, reject stale out-of-range indices, and label list nodes consistently with the Properties panel.
Delayed snapshot restoration — Generated snippets and standalone demos retain unresolved ViewModel and state-machine values and retry them across binding callbacks and animation frames, allowing dynamic list items to receive their exported values after they materialize.
RAV MCP load reliability — File-open commands receive a longer load window for cloud-backed files, and event-log replies safely serialize cyclic runtime payloads instead of failing the MCP request.
MCP status clarity — The runtime-strip MCP indicator is green when the bridge is healthy and ready, blue for 30 seconds after agent commands are received, yellow while connecting, red after a bridge failure, and muted when MCP is disabled.
Build and test toolchain maintenance — Refreshed Vite and Vitest to security-patched releases within their existing major versions, and made local build stamps explicitly identify uncommitted worktrees as `dirty`.
Atomic cross-platform releases — GitHub releases remain drafts while Apple Silicon, Intel macOS, Windows, updater signatures, and the merged `latest.json` are built; the workflow publishes only after the complete matrix succeeds.
Visual export command parity — `rav_export_demo_visual` now validates exact selection keys and forwards the dialog's selected controls, CDN/local package source, and compact/scaffold snippet mode to the saved demo instead of exporting with hidden defaults.
Website and reference refresh — Added the static annotated app overview and Script Editor guide, synchronized the MCP reference and machine-readable discovery copies, and documented the reproducible Vercel deployment path.
Fixed
Desktop build dependency alignment — Updated and aligned the Tauri core, build tooling, JavaScript API/CLI, desktop plugins, Rust dependency graph, and declared Rust minimum so local and release builds use one compatible, security-audited toolchain.
Dynamic ViewModel list population — List instances now populate on file load and rebuild whenever their controlling count changes, instead of remaining empty or stopping at the first 10 rows. Authored list entries use readable one-based labels such as `Row 1`, `Row 2`, and so on.
Export and snippet list parity — Standalone HTML demos and generated instantiation snippets now preserve the live player's dynamic list behavior and current row count. List-family selections expand across every current item, while excluded controls such as `focusIndex` stay out of the exported Properties panel and serialized control snapshot.
Single ViewModel instance visibility — The VM Instance selector now remains visible and populated when a file has one default instance, including a one-based fallback label for unnamed instances.
Playback and ViewModel load synchronization — RAV now records the actually playing or detected state machine after load, always populates the VM Instance selector, preserves the runtime's working auto-bound default, and uses a clean `autoBind: false` reload for explicit instance choices.
ViewModel instance export parity — Generated CDN/local snippets and standalone HTML demos now serialize and bind the selected ViewModel instance before applying exported control values, so their playback and triggers match RAV.
Live MCP ViewModel traversal — `rav_get_vm_tree`, `rav_vm_get`, `rav_vm_set`, and `rav_vm_fire` now traverse the currently bound nested ViewModels and dynamically sized lists, expose zero-based paths such as `rows/0/playerName`, reject stale out-of-range indices, and label list nodes consistently with the Properties panel.
Delayed snapshot restoration — Generated snippets and standalone demos retain unresolved ViewModel and state-machine values and retry them across binding callbacks and animation frames, allowing dynamic list items to receive their exported values after they materialize.
RAV MCP load reliability — File-open commands receive a longer load window for cloud-backed files, and event-log replies safely serialize cyclic runtime payloads instead of failing the MCP request.
1.7.6 -
Jul 15, 2026
Changed
Build numbering now auto-increments per local build using a persisted counter (`.cache/build-counter.txt`) instead of staying pinned to git commit count.
Fixed
Restored reliable desktop drag/drop file opening by handling window-level drop payloads and fallback URI/path payloads (`text/uri-list` / `text/plain`) in the frontend.
Added native Tauri drag/drop forwarding (`WindowEvent::DragDrop`) to the existing open-file handoff path, so `.riv` drops are received even when browser-style file payloads are absent.
Build numbering now auto-increments per local build using a persisted counter (`.cache/build-counter.txt`) instead of staying pinned to git commit count.
Fixed
Restored reliable desktop drag/drop file opening by handling window-level drop payloads and fallback URI/path payloads (`text/uri-list` / `text/plain`) in the frontend.
Added native Tauri drag/drop forwarding (`WindowEvent::DragDrop`) to the existing open-file handoff path, so `.riv` drops are received even when browser-style file payloads are absent.
Compatibility
Standalone Applications
Windows (Intel/AMD), macOS (Apple Silicon), macOS (Intel)
EULA
END USER LICENSE AGREEMENT
This software ("the Software Product") and accompanying documentation is licensed and not sold. This Software Product is protected by copyright laws and treaties, as well as laws and treaties related to other forms of intellectual property. The author owns intellectual property rights in the Software Product. The Licensee's ("you" or "your") license to download, use, copy, or change the Software Product is subject to these rights and to all the terms and conditions of this End User License Agreement ("Agreement").
Acceptance
YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT BY SELECTING THE "ACCEPT" OPTION AND DOWNLOADING THE SOFTWARE PRODUCT OR BY INSTALLING, USING, OR COPYING THE SOFTWARE PRODUCT. YOU MUST AGREE TO ALL OF THE TERMS OF THIS AGREEMENT BEFORE YOU WILL BE ALLOWED TO DOWNLOAD THE SOFTWARE PRODUCT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, YOU MUST SELECT "DECLINE" AND YOU MUST NOT INSTALL, USE, OR COPY THE SOFTWARE PRODUCT.
License Grant
This Agreement entitles you to install and use one copy of the Software Product. In addition, you may make one archival copy of the Software Product. The archival copy must be on a storage medium other than a hard drive, and may only be used for the reinstallation of the Software Product. This Agreement does not permit the installation or use of multiple copies of the Software Product, or the installation of the Software Product on more than one computer at any given time, on a system that allows shared used of applications, on a multi-user network, or on any configuration or system of computers that allows multiple users. Multiple copy use or installation is only allowed if you obtain an appropriate licensing agreement for each user and each copy of the Software Product.
Restrictions on Transfer
Without first obtaining the express written consent of the author, you may not assign your rights and obligations under this Agreement, or redistribute, encumber, sell, rent, lease, sublicense, or otherwise transfer your rights to the Software Product.
Restrictions on Use
You may not use, copy, or install the Software Product on any system with more than one computer, or permit the use, copying, or installation of the Software Product by more than one user or on more than one computer. If you hold multiple, validly licensed copies, you may not use, copy, or install the Software Product on any system with more than the number of computers permitted by license, or permit the use, copying, or installation by more users, or on more computers than the number permitted by license.
You may not decompile, "reverse-engineer", disassemble, or otherwise attempt to derive the source code for the Software Product.
Restrictions on Alteration
You may not modify the Software Product or create any derivative work of the Software Product or its accompanying documentation. Derivative works include but are not limited to translations. You may not alter any files or libraries in any portion of the Software Product.
Restrictions on Copying
You may not copy any part of the Software Product except to the extent that licensed use inherently demands the creation of a temporary copy stored in computer memory and not permanently affixed on storage medium. You may make one archival copy which must be stored on a medium other than a computer hard drive.
Disclaimer of Warranties and Limitation of Liability
UNLESS OTHERWISE EXPLICITLY AGREED TO IN WRITING BY THE AUTHOR, THE AUTHOR MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED, IN FACT OR IN LAW, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OTHER THAN AS SET FORTH IN THIS AGREEMENT OR IN THE LIMITED WARRANTY DOCUMENTS PROVIDED WITH THE SOFTWARE PRODUCT.
The author makes no warranty that the Software Product will meet your requirements or operate under your specific conditions of use. The author makes no warranty that operation of the Software Product will be secure, error free, or free from interruption. YOU MUST DETERMINE WHETHER THE SOFTWARE PRODUCT SUFFICIENTLY MEETS YOUR REQUIREMENTS FOR SECURITY AND UNINTERRUPTABILITY. YOU BEAR SOLE RESPONSIBILITY AND ALL LIABILITY FOR ANY LOSS INCURRED DUE TO FAILURE OF THE SOFTWARE PRODUCT TO MEET YOUR REQUIREMENTS. THE AUTHOR WILL NOT, UNDER ANY CIRCUMSTANCES, BE RESPONSIBLE OR LIABLE FOR THE LOSS OF DATA ON ANY COMPUTER OR INFORMATION STORAGE DEVICE.
UNDER NO CIRCUMSTANCES SHALL THE AUTHOR, ITS DIRECTORS, OFFICERS, EMPLOYEES OR AGENTS BE LIABLE TO YOU OR ANY OTHER PARTY FOR INDIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL, PUNITIVE, OR EXEMPLARY DAMAGES OF ANY KIND INCLUDING LOST REVENUES OR PROFITS OR LOSS OF BUSINESS) RESULTING FROM THIS AGREEMENT, OR FROM THE FURNISHING, PERFORMANCE, INSTALLATION, OR USE OF THE SOFTWARE PRODUCT, WHETHER DUE TO A BREACH OF CONTRACT, BREACH OF WARRANTY, OR THE NEGLIGENCE OF THE AUTHOR OR ANY OTHER PARTY, EVEN IF THE AUTHOR IS ADVISED BEFOREHAND OF THE POSSIBILITY OF SUCH DAMAGES. TO THE EXTENT THAT THE APPLICABLE JURISDICTION LIMITS THE AUTHOR'S ABILITY TO DISCLAIM ANY IMPLIED WARRANTIES, THIS DISCLAIMER SHALL BE EFFECTIVE TO THE MAXIMUM EXTENT PERMITTED.
Limitation of Remedies and Damages
Any claim must be made within the applicable warranty period. All warranties cover only defects arising under normal use and do not include malfunctions or failure resulting from misuse, abuse, neglect, alteration, problems with electrical power, acts of nature, unusual temperatures or humidity, improper installation, or damage determined by the author to have been caused by you. All limited warranties on the Software Product are granted only to you and are non-transferable. You agree to indemnify and hold the author harmless from all claims, judgments, liabilities, expenses, or costs arising from your breach of this Agreement and/or acts or omissions.
Governing Law, Jurisdiction and Costs
This Agreement is governed by the laws of New York, without regard to New York's conflict or choice of law provisions.
Severability
If any provision of this Agreement shall be held to be invalid or unenforceable, the remainder of this Agreement shall remain in full force and effect. To the extent any express or implied restrictions are not permitted by applicable laws, these express or implied restrictions shall remain in force and effect to the maximum extent permitted by such applicable laws.
Updated: Oct 21, 2025 1:35 AM