If you downgrade your Webflow plan, there may be changes to your custom code features depending on the plan.
1. Impact on Custom Code
- Custom Code: Webflow allows custom code in projects starting from the "Lite" plan for Account Plans and "Basic" plan for Site Plans. If you downgrade to a plan that does not support custom code, the existing custom code will become inactive.
- Activation: Custom code is stored but not executed when downgraded to a plan that doesn't support it. It remains in your project, but its effects are not visible.
2. Reviewing Plan Features
- Webflow Plans: Check the features of each Webflow plan. Higher-tier plans will support custom code, while some lower-tier plans may not.
- Plan Adjustment: Consider how a downgrade impacts your project needs, including any custom features relying heavily on code.
3. Testing Downgrades
- Sandbox Testing: Before downgrading, test how your site functions without the custom code by temporarily removing it to preview changes.
- Simulated Changes: Use Webflow’s staging environment if available under your current plan to simulate how downgrading might affect your site.
4. Custom Code Storage
- Retention: Your custom code is saved even if not executed due to plan limitations.
- Future Upgrades: If you upgrade again in the future to a plan supporting custom code, it will automatically reactivate without needing reentry.
Summary
Downgrading your Webflow plan can deactivate custom code if the new plan doesn't support it, though your code is retained for future use. Evaluate the feature requirements of your site alongside different plans to ensure your needs are met.