Feature Support
Runtime versions that start supporting new Rive features
Last updated
Runtime versions that start supporting new Rive features
Last updated
This article is out of date! Find the new version here.
As our Rive editor grows to support more features and toolsets in making Rive assets, sometimes our runtimes need to be updated to support these updates. These editor additions may or may not introduce an API change or feature. You may need to update the runtime version to support these features. Check below to see if a feature your Rive asset takes advantage of is supported at runtime yet or not. We generally recommend you are on the latest version of the runtimes to take advantage of follow-on bug fixes and new features. We may include notes on migrating to newer versions if a new feature warrants recent API changes.
To add support for nested inputs and nested events, bump the appropriate versions noted below to support this new feature. For more information, see Nested Artboards.
Runtime | Version |
---|---|
To load assets dynamically, instead of embedded in the riv
file, bump the appropriate versions noted below to support this new feature. For runtime specific information, see Loading Assets.
Runtime | Version |
---|---|
To receive reported Rive Events at runtime, bump to the appropriate versions noted below to support this new feature. For runtime specific information, see Rive Events.
To take advantage of basic Text support at runtime, bump to the appropriate versions noted below to support this new feature. For runtime specific information, see Text.
Note that we will proactively update the above versions as additional APIs on runtimes expose ways to dynamically set text (high and low-level), among other related features.
To take advantage of follow path at runtime, bump to the appropriate versions noted below to support this new feature.
To take advantage of Interpolation on States at runtime, bump to the appropriate versions noted below to support this new feature.
To allow any Joystick configuration from the editor to reflect at runtime, bump to the appropriate versions noted below to support this new feature.
To take advantage of Solos at runtime, bump to the appropriate versions noted below to support this new feature.
If you set speed values on states in the state machine, bump to the appropriate versions noted below for the runtime being used to support this new feature.
If you use the timeline graph editor in the Rive editor and export a .riv
file for runtime usage, bump to the appropriate versions noted below for the runtime being used to support this new feature.
Notes
rive-react
- Starting in v3.0.0
the React runtime has split into two different published packages; @rive-app/react-canvas
and @rive-app/react-webgl
, each wrapping the respective @rive-app/canvas
and @rive-app/webgl
web runtimes. We recommend using @rive-app/react-canvas
@rive-app/webgl
- There is a new flag here, useOffscreenRenderer
which is off by default. This flag will allow you to work around the various browser constraints on the number of WebGL contexts created. We highly recommend setting this option to true
when instantiating Rive in the high-level API. See more here: https://github.com/rive-app/rive-wasm#other-notes.
rive-react-native
- Starting in v3.0.0
, it will have a minimum iOS 14.0
support
No extra code is needed to support listeners, and you do not need to invoke listeners via event listener/detector code at runtime. If the Rive file has a listener as part of the state machine at design time, the runtime library has implicit event listener/detector code to trigger the listeners at the appropriate time
Notes
rive-react
- Starting in v3.0.0
the React runtime has split into two different published packages; @rive-app/react-canvas
and @rive-app/react-webgl
, each wrapping the respective @rive-app/canvas
and @rive-app/webgl
web runtimes. We recommend using @rive-app/react-canvas
@rive-app/webgl
- There is a new flag here, useOffscreenRenderer
which is off by default. This flag will allow you to work around the various browser constraints on the number of WebGL contexts created. We highly recommend setting this option to true
when instantiating Rive in the high-level API. See more here: https://github.com/rive-app/rive-wasm#other-notes
Regarding web-based runtimes and meshes:
Keep in mind that as meshes grow across larger screen areas, they become more resource-heavy on some devices
Avoid complex transforms repeatedly on the <canvas>
elements that display Rive animations (or <RiveComponent />
in the React runtimes)
We recommend using @rive-app/webgl
to display mesh on Firefox for best performance
Notes
For the web runtimes, we have deprecated rive-js
and moved to a multi-package setup for a JS runtime that runs against the context2d
and webgl
renderer:
Note that the new web runtime packages all support raster assets, and the high-level JS API did not change in this migration
@rive-app/canvas
- Renders Rive with a CanvasRenderingContext2D
renderer
@rive-app/webgl
- Renders Rive with a WebGLRenderingContext
renderer.
We recommend using the @rive-app/canvas
dependency, but check here to see which might fit your needs better
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
Runtime | Version |
---|---|
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS/macOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
❗️Coming soon
Flutter
iOS/macOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS/macOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS/macOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS/macOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS/macOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS
Android
C++
(Web) @rive-app/canvas
and @rive-app/webgl
React
React Native
Flutter
iOS
Android
C++
(Web) @rive-app/canvas
(Web) @rive-app/webgl
React
React Native
Flutter
iOS
Android
C++
(Web) @rive-app/canvas
(Web) @rive-app/webgl
React
React Native
Flutter
iOS
Android
C++
(Web) @rive-app/canvas
(Web) @rive-app/webgl
React
React Native
Flutter
iOS
Android
C++
(Web) @rive-app/canvas
(Web) @rive-app/webgl
React
React Native
Flutter
iOS
Android
C++
**(Web) @rive-app/canvas
**(Web) @rive-app/webgl
**React
React Native
Flutter
iOS
Android
C++
>= 2.7.0
>= 4.5.0
>= 6.2.0
>= 0.12.3
>= 5.6.0
>= 8.7.0
Supported
>= 2.7.0
>= 4.5.0
>= 0.12.0
>= 5.7.0
>= 8.6.1
Supported
>= 2.4.3
>= 4.3.3
>= 6.1.0
>= 0.11.17
>= 5.3.1
>= 8.4.0
Supported
>= 2.1.3
>= 4.1.3
>= 6.0.3
>= 0.11.14
>= 5.1.5
>= 8.1.3
Supported
>= 1.2.4
>= 3.0.55
>= 5.0.0
>= 0.11.6
>= 4.0.5
>= 6.0.1
Supported
>= 1.2.1
>= 3.0.54
>= 4.1.2
>= 0.11.4
>= 4.0.4
>= 5.1.5
Supported
>= 1.1.9
>= 3.0.49
>= 4.1.0
>= 0.11.1
>= 4.0.1
>= 5.0.0
Supported
>= 1.1.2
>= 3.0.42
>= 4.0.4
>= 0.10.4
>= 3.1.9
>= 4.4.0
Supported
>= 1.0.102
>= 1.0.98
>= 3.0.38
>= 4.0.1
>= 0.10.3
>= 3.1.7
>= 4.2.7
Supported
>= 1.0.97
>= 1.0.93
>= 3.0.34
>= 4.0.1
>= 0.10.0
>= 3.1.3
>= 4.2.2
Supported
>= 1.0.65
>= 1.0.62
>= 3.0.6
>= 3.0.38
>= 0.9.0
>= 2.0.21
>= 3.0.8
Supported
>= 1.0.47
>= 1.0.44
>= 3.0.1
>= 2.1.37
>= 0.8.4
>= 1.0.18
>= 2.0.24
Supported
>= 1.0.2
>= 1.0.2
>= 0.0.28
>= 2.1.36
>= 0.8.1
>= 1.0.1
>= 2.0.5
Supported