If you’re experiencing issues exporting an animation to JSON using the Bodymovin extension after an After Effects update, follow these steps to resolve compatibility problems.
1. Check for Bodymovin Updates
- Open After Effects and go to Window > Extensions > Bodymovin.
- Click on Settings and check for any available updates.
- If an update is available, install it and restart After Effects.
2. Reinstall Bodymovin
- If updating doesn’t work, try uninstalling and reinstalling the Bodymovin extension.
- Open Adobe Creative Cloud and go to Plugins > Manage Plugins.
- Remove Bodymovin, restart After Effects, then reinstall it from the Adobe Exchange or from AEScripts.
3. Verify After Effects Scripting Is Enabled
- Open After Effects Preferences > Scripting & Expressions.
- Ensure that Allow Scripts to Write Files and Access Network is enabled.
- Restart After Effects and try exporting again.
4. Export with Legacy Settings
- Some After Effects updates introduce changes that break older Bodymovin functionality.
- Open Bodymovin and try the Legacy Render option if available.
- Export the animation again and try importing it into Webflow.
5. Downgrade After Effects (If Necessary)
- If export issues persist, consider downgrading to a previous stable version of After Effects.
- In Adobe Creative Cloud, go to Apps > After Effects > More options > Other versions.
- Install a prior version that worked with Bodymovin.
6. Test with a Simple Animation
- Create a basic shape animation (e.g., a circle moving left to right) and try exporting it.
- If the simple animation works but your original file doesn’t, check for effects or expressions that may not be Bodymovin-compatible.
Summary
Ensure Bodymovin is up to date, reinstall if needed, check scripting permissions, and try legacy settings. If the problem continues, downgrade After Effects or test with a simpler animation before troubleshooting your main project.