If I downgrade my Webflow plan after adding custom code, will the features implemented using the code still be accessible? Or will the code revert to its previous state before the site plan?

When you downgrade your Webflow plan, the accessibility and functionality of custom code on your site can be affected.

​

1. Impact on Custom Code

• Custom Code Access: Custom code functionality is contingent upon the feature availability in your current plan. If the new plan doesn't support custom code, it may become inaccessible or disabled.
• Code Availability: The custom code is stored with the project, so downgrading doesn't revert the code to a previous state. However, execution of the code depends on the plan's capabilities.

​

2. Plan Limitations

• Check Plan Features: Before downgrading, review the features of the new plan to ensure that it supports custom code, especially if your site relies heavily on it.
• Hosting and Functionalities: If the downgraded plan lacks certain functionalities, not only custom code, but other advanced features may also not work as intended.

​

3. Testing After Downgrade

• Verify Post-Change: After downgrading, test the site's functionality. Ensure that key features implemented through custom code are still operational.
• Review Errors or Alerts: Look for notifications or errors on the Webflow dashboard that indicate any issues related to custom code execution.

​

Summary

Downgrading your Webflow plan could affect the accessibility and functioning of custom code if the new plan does not support that feature. It's crucial to check the supported features of the downgraded plan before making changes to ensure essential scripts remain operational.