Compatibility and limitations
Understand format, player, permission, and synchronization boundaries in Webflow.
Insertion paths
| Source or feature | Published Webflow runtime | Notes |
| Ordinary Lottie JSON | Native Webflow Lottie | File is copied into Webflow Assets |
| dotLottie without runtime-only features | Native Webflow Lottie when convertible | Selected animation and theme can be applied to JSON |
| dotLottie v2 | Advanced <dotlottie-wc> player | Uses page custom code and a canvas thumbnail |
| Multi-animation dotLottie | Native selected child or advanced player | Result depends on format version and active features |
| Runtime themes | Advanced player | Native insertion receives a fixed themed JSON result |
| State machines | Advanced player | Requires a compatible source, container, page custom code, and published runtime |
Renderer boundary
SVG Player is appropriate for ordinary Lottie playback. ThorVG Player is required to preview multiple animations, themes, and state machines. Switching an advanced file to SVG Player can remove or ignore those features.
Webflow permissions
The app needs authorization for the current site. The user must be able to edit the page, select a valid element, manage the resulting structure, and publish to the intended environment. Advanced insertion also needs the app's page custom-code capability.
Source and synchronization
Standard insertion creates a Webflow Asset copy. Advanced insertion stores the selected source and feature IDs in the generated element. Neither path is a live Workspace synchronization connection. Reinsert and republish after a source update.
Testing boundary
The design canvas can show a thumbnail for advanced players. Always use Preview and the staging URL to test actual playback, themes, and state machines.