Troubleshooting
Diagnose common Webflow app, insertion, preview, and publishing problems.
Start by locating the boundary: source file, app preview, selected Webflow element, generated runtime, staging site, or production site.
| Symptom | Check |
| Workspace is empty | Confirm the LottieFiles account, active workspace, and project permissions |
| Insert animation asks for a selection | Select a page element and retry without leaving the prepared preview |
| Selected element cannot contain the player | Use a Div block or another container that accepts children |
| Native animation is missing | Check Webflow Assets and the new Lottie element in the Navigator |
| Advanced player shows only a still image on canvas | This is the canvas thumbnail; test the real component in Preview and staging |
| Preview is blank | Use Automatic or ThorVG Player for advanced files and confirm page custom code is present |
| Theme does not change | Determine whether insertion was native fixed-theme JSON or an advanced runtime theme |
| State machine does not respond | Confirm the intended state-machine ID, a valid container, and testing in Preview or on a published URL |
| Staging works but production is old | Publish to the production domain and confirm the correct domain was selected |
| Workspace update is missing | Reinsert or replace the Webflow element; updates are not synchronized automatically |
Isolate an advanced-feature problem
Keep the existing page or element as a fallback.
Insert a simple free single-animation file with default settings.
If it works, reintroduce dotLottie v2, themes, multiple animations, or a state machine one at a time.
Publish to the
webflow.iostaging domain after each meaningful change.
Get help
Use the app account menu and LottieFiles support resources to report a bug. Include the Webflow site context, source format, insertion path, selected element type, and whether the problem appears in Preview, staging, or production.
Related
Last updated: July 24, 2026 at 2:45 AMEdit this page