Spline vs three.js for a landing page
Choose Spline if a designer will build the scene and keep editing it, and you can afford a runtime plus a scene file on the page. Choose raw three.js, or react-three-fiber in a React codebase, if you need full control and have the engineering time. Choose Lottie or Rive if the motion is really 2D. And if what you want is one small object that answers the pointer, a ready-made interactive 3D illustration is the shortest route to a working page. The rest of this guide sets out the trade-offs, with numbers only where they can be checked.
What you are choosing between
Spline is a visual 3D design tool. You model, light and animate in its editor, then export a public URL, a viewer web component, or code for vanilla JS, three.js, React, Next.js or react-three-fiber (Spline docs). Spline's own comparison is fair about the split: three.js is the pick when you want full control of the renderer, shaders and every frame in code (Spline vs Three.js).
three.js is the open-source WebGL library that Spline's three.js export and Linejig both build on. You write the scene, camera, materials, interaction and render loop yourself.
react-three-fiber describes itself as a React renderer for three.js (r3f docs). Same engine, written as components, which suits a React app where the 3D shares state with the rest of the page.
Lottie and Rive are 2D. Lottie plays vector animation exported as JSON; Rive plays files from its own editor, with state machines. Plenty of "3D hero" ideas turn out to be 2D motion once sketched.
Pre-built interactive figures are objects someone has already modelled and wired up. Linejig's library is one: small real objects drawn as 3D line illustrations on three.js, each with one hero part that answers hover and click.
Weight
The figures below were measured at the time of writing by gzipping the published files on jsDelivr. A CDN serving brotli will send less, and your own build may tree-shake more.
- three.js r160, minified module: about 165 KB gzipped (the file). Your scene code and models come on top. react-three-fiber adds its own code to that.
- Lottie: the full lottie-web player is about 75 KB gzipped and the lighter SVG-only build about 45 KB (lottie-web). Each animation's JSON is extra.
- Rive: the WebAssembly file in
@rive-app/canvas-lite, the smaller canvas package, is about 370 KB gzipped on its own (package), before the JavaScript wrapper and your.rivfile. - Spline: depends on the scene. Spline's optimisation guide says export size and loading time vary with geometry, textures and compression, and that the editor shows an estimate (optimise your scene). Measure your own scene in the network panel rather than trusting a single number.
- Linejig: the engine is about 40 KB gzipped on top of three.js, and each figure adds 4 to 7 KB (docs). three.js is the larger share: the 165 KB above at least, and more for the unminified module the embeds currently load. The browser fetches both once, so a second figure on the site costs only its own few kilobytes.
Effort and control
Control and effort rise together.
A ready figure takes minutes: one iframe line copied from the library, or a module that mounts many figures on one shared canvas. In exchange you get the objects the library has and the settings it exposes (style, brand colour, light or dark, intro, floor grid), not your own model.
Spline is mostly design time, and the scene stays in a tool a designer can keep working in. One detail from its docs worth knowing before you plan interactions: animations and events are only enabled when exporting to vanilla JS and React.
Raw three.js takes the longest to look finished. Camera fit, pointer handling, resizing, pixel ratio, sleeping when nothing moves, cleaning up: you own all of it, which is the right deal when the 3D is the product.
react-three-fiber removes much of that glue in a React codebase, at the cost of putting the 3D inside your React tree. Lottie and Rive split the work between a motion designer and a developer who drops in a player.
Accessibility and reduced motion
Every option here can respect prefers-reduced-motion, but in most of them that is your job: you read the media query and pause, seek or replace the animation in your code. Spline's viewer documentation covers lazy loading, a loading spinner and an interaction hint, and does not mention reduced motion (viewer docs), so plan to handle it in your page.
Linejig figures handle it themselves. With reduced motion on, a figure skips its intro and shows its finished state, the view stops springing back, and hover and click still work. Whatever you choose, a canvas is a picture to a screen reader: give it a text label, and keep the words that matter in the page, not in the drawing.
Slow connections and fallbacks
A canvas that takes seconds to appear is worse than a still image. Spline's viewer lazy-loads a scene when it comes on screen and can show a spinner; a still poster for slow connections is something you add, as it is with three.js, react-three-fiber and Rive.
Linejig ships the still. Every figure has an SVG poster of its finished state, in light and dark, framed exactly like the live plate. The docs show the pattern the site itself uses: show the poster, check navigator.connection for save-data or a slow connection, and bring in the live figure only when the connection can carry it.
Many live 3D embeds on one page is a problem for every option, because each iframe gets its own WebGL context and browsers cap those. Spline's guide advises no more than three embeds per page. Linejig's docs put the comfortable number at three or four frames, and offer a shared stage that draws a whole grid of figures with one context.
Side by side
| Spline | three.js | react-three-fiber | Lottie or Rive | Ready figures (Linejig) | |
|---|---|---|---|---|---|
| What it is | Visual 3D editor with web export | 3D library | React renderer for three.js | 2D animation players | A library of interactive 3D illustrations |
| Weight | Varies by scene; measure it | About 165 KB gzipped, plus your code | three.js, r3f and your code | Lottie player about 45 to 75 KB; Rive's WebAssembly about 370 KB; plus files | Engine about 40 KB plus 4 to 7 KB a figure, on three.js |
| Effort | Design time in the editor | Highest | High, less glue in React | Motion design, then a player | Minutes per figure |
| Control | High, within the editor | Total | Total | High, in 2D | Settings only: style, colour, theme, intro |
| Reduced motion | Yours to handle | Yours | Yours | Yours | Built in |
| Slow-connection fallback | Lazy loading and a spinner; the still is yours | Yours | Yours | Yours | SVG poster for every figure |
| Suits | Designer-led hero scenes and product renders | Teams for whom 3D is the product | React apps where 3D shares state | 2D motion: icons, characters, UI | One object for a feature, empty state, 404 or loader |
Who each suits
Spline suits a team with a designer who wants to own a full scene: a product render, a hero with several objects, lighting and materials. Check the plan you need: at the time of writing, Spline's pricing page lists web exports on the free plan with a watermark, watermark-free web exports from Hobby, and code export from Pro.
three.js and react-three-fiber suit a page where the 3D is the main event and someone enjoys owning a render loop. Lottie or Rive suit motion that is flat by nature; Rive's state machines are made for animation that reacts to input.
Ready figures suit the most common landing-page need: one object beside one idea, a lock for security, a telescope for discovery, gears for a loader. Linejig's limits are worth stating plainly. It shows the objects in its library, not your product model. It embeds by iframe or a plain JavaScript module, and no React component is documented. When the library has no object for your moment, the free Line art skill for Claude Code draws a new figure on the same engine, in the same Line art style.
Next step
Open the library and turn a few figures, or start with the free ones. The docs have the embed code, the poster pattern and the shared stage for many figures on one page.
Published 21 November 2026.