"Make a card that glows when you hover, highlights each word, and twinkles like a star."
Examples
Everything below was generated by Polymation — animations authored from a prompt, and real conversions between formats. The Rive examples are live and interactive; the conversions show the actual per-decision loss report Polymation produces every time.
Live 3D — in your browser
This Spline scene was authored from scratch by Polymation (no Spline app) and is rendering live, right now, in the real Spline web runtime. Drag to rotate it.
From a prompt
Describe what you want in plain language; Polymation writes the .riv directly — shapes, state machines, physics, text, interactions. Hover the cards to interact.
"A ball that drops and bounces with real gravity and squash."
"A smooth, seamless loading spinner."
"An animated on/off toggle switch."
"Morphing geometric shapes in a loop."
Conversions — with an honest loss report
Cross-format conversion is lossy by physics (a 2D vector rig is not a 3D scene). So Polymation never silently drops anything: every conversion ships a per-decision report — what came across clean, what was reconstructed, what was dropped (and why), and what needs your call. These are real outputs from the examples below.
A conversion to Spline can write either form — runtime .splinecode (shown live below) or editable .spline — and both are offered here, so you can ship it or keep editing. Both 3D scenes here are rendering in the real Spline runtime.
Rive → Spline
Input — Rive (.riv) · live
Three 2D shapes — a gradient box, a floating circle, a triangle — with a gradient fill, opacity and a float animation.
The circle's float animation plays in the live runtime 3D (right): it rises once on load, so hit ▶ Replay float to see it again. The Rive input (left) bobs up and back on a loop; the 3D copy rises once, because Spline's start transition plays once. Drag the 3D to rotate.
.splinecode — the runtime auto-fires Start on load, so the sphere rises once in the live 3D (use ▶ Replay).Spline → Rive
Output — Rive (.riv) · live
Each 3D mesh becomes its flat 2D footprint with the material color; the scene background becomes a Rive artboard background.
Lottie → Rive
Input — Lottie (.json) · live lottie-web
A gradient card, a morphing blob (animated bezier path), and a dot easing back and forth with overshoot — playing in the real lottie-web player.
Both sides are playing live. The blob's path morph became real Rive vertex keyframes (position + curve handles per point), the easing curves carried over 1:1, and the gradient survived intact. It converts back to Lottie too — grab the round-tripped .json above. Also accepts .lottie (dotLottie) files, including interactive dotLottie 2 packages, whose state machines and colour themes arrive as Rive state machines and view models wherever Rive can express them; the rest is named in the report. The reverse works too: any Rive scene exports to Lottie for web/iOS/Android players, or to an interactive dotLottie that keeps its states, guards, transitions and pointer interactions; what dotLottie cannot hold, such as blend states, is named in the report.
Make your own
Everything here came from a prompt or a conversion. Install Polymation in your MCP client and try it — 3 free exports, no account.
Download free Subscribe — $10/mo