Recraft vs LottieFiles
Side-by-side trajectory, velocity, and editorial themes.
Recraft is becoming a multi-model creative studio that lives inside designers' existing tools.
Recraft is shipping on three concurrent fronts: its own image model (V4.1 just released), an expanding catalogue of third-party image and video generators (GPT Image 2, Seedance 2.0, PixVerse, Wan, Veo 3.1 Lite, Qwen, Flux Schnell, Grok), and embedded surfaces in Figma, Framer, and Chrome. Video generation, added in late March, has moved from a single capability into a substantive model menu. Node-based Workflows in beta push the product toward repeatable production pipelines.
Recraft is hedging the model-supremacy question by aggregating the best third-party generators while continuing to invest in its own V-series for a coherent aesthetic. The plugin distribution into design tools and the Workflows beta show the product strategy shifting from generator-as-destination to creative substrate that plugs into existing pipelines. The bet is that creative professionals will pay for curation, workflow, and aesthetic consistency on top of commodity model access.
Expect Workflows to graduate out of beta with stronger templating and team-sharing primitives, plus continued addition of video models as that frontier moves fast. Look for either an Adobe-side integration or a stronger Figma-native presence next, mirroring the Framer and Chrome moves.
LottieFiles ships an MCP server alongside generative tooling — Lottie Creator is becoming AI-native.
LottieFiles is shipping aggressively across three threads: AI authoring (Prompt to Vector 2.0, AI-driven scene generation), agentic integration (Lottie Creator now connects to Claude, Cursor, and any MCP client), and creator-tool depth (curved-path animation, freehand vector drawing, version history, intelligent keyframe simplification). The .lottie file format gained multi-animation support, and a Figma plugin now translates Figma prototype interactions into production animations.
LottieFiles is positioning Creator as the canvas where motion design and AI tooling meet — both as a generation source (text-to-vector, scene generation) and as a target other AI assistants can manipulate via MCP. The Figma interaction-to-animation feature suggests a deliberate strategy of importing intent from upstream design tools rather than asking designers to redesign in Lottie Creator. File format work (multi-animation .lottie, smaller files at same fidelity) keeps Lottie viable as the underlying motion-graphics format on the web.
Expect deeper MCP-driven workflows — agents that take a brief and produce a finished Lottie file inside Creator without human authoring — and additional importers from After Effects, Rive, or Spline. The Figma interaction bridge is likely to be replicated for other prototyping tools (Framer, ProtoPie). Generative motion is a strong candidate for next major surface.
See more alternatives to Recraft →
See more alternatives to LottieFiles →