Butter Motion vs Rive and Lottie
A designer sends you a file called loader.riv and says the logo animation is done. You drag it into Premiere and Premiere shrugs. Same story with the .json a developer pulls out of a Lottie library: it is an animation, it plays beautifully in a browser, and your sequence has no idea what to do with it.
That is not a flaw in either tool. Rive and Lottie were built for products, not for cuts, and they are extremely good at the thing they were built for. This is a look at what it takes to get their output onto a timeline, and at the cases where an editor should stop trying.
Everything below about Rive and LottieFiles comes from their own sites, read on 2 September 2026. Two gaps we could not close: LottieFiles' pricing page refuses our reader, so no amounts for them appear here, and Rive's export documentation says nothing either way about an alpha channel in video exports, so we do not claim one exists.
They are runtimes, not renders
Rive calls itself "an end-to-end pipeline for interactive graphics", where "Rive's editor, file format, and runtimes work seamlessly together". The centre of it is the State Machine: you "create interactivity visually using animations as states", and the graphic reacts to "hovers, clicks, taps, and more". A finished file ships as .riv and gets played by a runtime in JavaScript, Flutter, iOS, Android, React, React Native, C++, Defold, Unity or Unreal.
Lottie is the older idea and a simpler one: a vector animation stored as JSON that a player draws at runtime. LottieFiles' own docs describe the .json export as having "universal compatibility, all Lottie players", and .lottie, the compressed variant, as 60 to 80 percent smaller.
Notice what neither sentence mentions. Frames, a sequence, a codec, an alpha channel. These formats describe motion so an app can draw it live, which is exactly why a button can bounce when you tap it, and exactly why a video editor cannot drag one into a timeline.
Getting to a file your sequence understands
Both have an exit into video, and both have conditions.
Rive renders through its Cloud Renderer. You build render presets, add them to the queue, and collect the results in the Completed tab. In Animate Mode the formats are H.264, GIF, PNG sequence, SVG sequence and WebM, and their documentation states plainly that "exporting video and images is available on paid plans". Free accounts get the editor and three collaborative files, so the moment you need a deliverable, you are on a plan. Cadet is $9 per seat a month with a three seat cap, Voyager is $32 with libraries, embed hosting and $20 of monthly agent credits per seat, and Enterprise is $120 with SSO and SOC2 Type II.
For an overlay, the open question is transparency. Their export page does not mention alpha for any of the video formats, so if the graphic has to sit on footage, plan on a PNG sequence, or test a WebM before you promise anything to a client.
Lottie Creator, the browser editor, exports Lottie JSON, dotLottie, MP4, WebM, GIF and MOV. Their format list flags exactly one of those for transparency: WebM, "modern web video, smaller than MP4, transparency support". The free workspace holds five private files and ten public animation downloads a month, and LottieFiles bills annually across the board, since "all plans (Free, Individual, Team, and Enterprise) run on an annual billing cycle".
There is also a shortcut worth knowing, and it is the fairest thing in this article. By LottieFiles' description on their Premiere Pro plugin page, the plugin reaches their library from inside the app and inserts animations as MOV or MP4, with a transparent background on by default and no chroma keying. That page did not open for our reader on 2 September 2026, so take those details as their claim rather than as something we checked. If what you need is a stock spinner, a like animation or an arrow, it is a two click job and nothing in this article beats it.
| Butter Motion | Rive | Lottie / LottieFiles | |
|---|---|---|---|
| Built for | Clips on a Premiere timeline | Interactive graphics in products | Vector animation played by apps and sites |
| Native output | MP4 H.264, or MOV ProRes 4444 with alpha | .riv for runtimes | .json or .lottie for players |
| Video export | The whole point | H.264, WebM, GIF, PNG and SVG sequence, paid plans only | MP4, MOV, WebM, GIF from Lottie Creator |
| Documented transparency in video | Yes, MOV ProRes 4444 on every plan | Not stated in their export docs | WebM listed with transparency support |
| Where it renders | Locally, from the panel | Their Cloud Renderer | Their service |
| Interactivity | None | State Machine, listeners, data binding | Player controls playback |
| Free tier | None | Editor and 3 collaborative files | 5 private files, 10 public downloads a month |
The After Effects route, and what it drops
Plenty of Lottie work still starts in After Effects with the LottieFiles panel, which lives under Window then Extensions and exports the composition as JSON. If you already know After Effects, that is a real workflow.
It is also the part where a motion designer's expectations meet the format. LottieFiles' own compatibility page says that "not all After Effects features can be converted to Lottie format due to the limitations of the JSON-based animation format", and then lists what does not survive: every 3D feature including cameras and lights, adjustment layers, layer styles such as drop shadows and glows, most effects including blurs, distortions and generators, and complex expressions. Effects support is narrow by design, "only certain effects like fill, stroke, and tint are supported". Shape layers, paths, strokes, fills and the transform properties all come through fine.
For a UI animation, that list costs you nothing. For a broadcast style title with a soft glow behind it, it costs you the look.
Where Butter Motion is simply the shorter route
We do one thing, and it starts and ends inside Premiere. You describe the clip in the panel, watch a live preview, and the finished animation renders on your own computer into a _ButterMotion folder beside your .prproj, imports into a bin of its own, and drops at the playhead. A transparent clip goes onto a track above your footage on purpose. See Rendering to the timeline.
Transparency is a chip you set before generating, not a plan you upgrade to. Transparent comes back as MOV in ProRes 4444, with a background as MP4 in H.264, on every plan and every quality tier. See Background and transparency.
The clip is also shaped for your sequence before it exists: 3 to 20 seconds, 16:9, 9:16 or 1:1, 720p through 4K, and 24, 25, 30, 50 or 60fps, none of which changes the price. Only the quality tier does, at 7, 10 or 15 credits. See Duration, format and resolution and Quality tiers and 3D.
One more thing comes with that. The 3D that Lottie explicitly cannot carry is available on the Ultra tier with no surcharge, because we are producing frames rather than a vector document.
Where Rive and Lottie win, and it is not close
The graphic has to react. A toggle, a loader that follows real progress, a character that looks at the cursor. Rive's State Machine and data binding exist for that, and no rendered clip can imitate it.
It ships inside a product. An app or a site wants a file that scales, weighs kilobytes and redraws at any resolution. A ProRes MOV is the wrong object entirely.
One animation, many platforms. The same .riv plays through the iOS, Android, Flutter, React and Unity runtimes, and a Lottie JSON plays anywhere a Lottie player runs. We render a clip for one timeline.
You need a library rather than a generation. By their description, the LottieFiles Premiere plugin puts a large catalogue two clicks from your sequence and handles transparency for you. For generic icon motion that is faster than describing anything.
You are the designer, not the editor. Rive's editor gives you exact control over vectors, states and timing, and Lottie Creator is a real editor in a browser. Butter Motion has customization controls for colours, text, numbers and fonts, and words for everything else. That is a different kind of steering wheel.
Worth saying plainly, since these comparisons invite the wrong conclusion: an editor covering the routine graphics themselves is not the same as doing without a designer. The set pieces, the brand system and anything with a real design problem in it still go to one.
Which one to reach for
If the animation is going into a product, use the product tools. Rive when it has to respond to the user, Lottie when it just has to play, and neither decision has anything to do with us.
If the animation is going onto a timeline in a cut that ships as video, the shortest honest path is the one that ends in the right file. That is the LottieFiles Premiere plugin when a library asset will do, and Butter Motion when the graphic has to be specific to this project: your client's chart, your headline, your brand colour, in real alpha, at your sequence's frame rate, with the finished file already in the project folder when the render ends.
Two plans, 500 or 2,000 credits a month, everything unlocked on both. See Pro and Studio and What is Butter Motion.