Compatibility and limitations
Understand format, renderer, feature, and synchronization boundaries in Framer.
Formats and renderers
| Source or feature | Recommended renderer | Notes |
| Ordinary Lottie JSON | Automatic or SVG Player | Suitable for standard timeline playback |
| dotLottie | Automatic or ThorVG Player | Preserves dotLottie packaging and advanced features |
| Multi-animation dotLottie | ThorVG Player | The plugin extracts the selected child for insertion |
| Themes | ThorVG Player | Supports default and Framer light/dark mappings |
| State machines | ThorVG Player | Requires a compatible dotLottie file and player component |
Switching an advanced file to SVG Player can remove or ignore multiple animations, themes, and state machines. The plugin shows a warning when it detects this risk.
Source availability
The inserted component needs a source that the published Framer site can retrieve. Do not use a temporary or locally accessible URL as a production source.
Workspace synchronization
Workspace identifies the approved source and version. It is not a live data connection to the Framer component. Reinsert and republish after a source update.
Canvas and runtime
The component is inserted into a selected Frame when possible, otherwise at the canvas root.
Framer owns responsive constraints, page visibility, and clipping.
The plugin preview does not replace Framer Preview or live-browser testing.
Advanced feature availability can depend on the current plugin release, file, account, and feature rollout.
For supported Framer browsers, see Framer requirements and browser support.