Allows you to retain any recently staged or published changes you want to keep, eliminating the need to rebuild or redo that work.
Eliminates risk of broken API connections, comparative to restoring a backup.
Cons:
Relies on you to remember which exact elements and pages need to be reverted and manually replaced; runs the risk of missing certain changes.
Pasting elements will result in duplicated classes (e.g., “Navbar 2”), even if they have the exact same name and styles. Duplicate classes must be manually replaced with the original class (e.g., “Navbar”) in the Style Panel.
Replacing elements in your primary locale will also replace it (and any localized changes to it) in all supported locales. Any localization work (such as translation) will need to be redone in each supported locale.
Restore a site backup
Pros:
Allows you to revert the entire site to a known previous state.
Reduces need to manually comb through elements and pages to identify specific changes to revert or retain.
Cons:
No ability to retain specific changes (that you want to keep) that occurred past the restore point, especially across all locales. That work will need to be redone in the main site and each supported locale.
Restoring a backup changes the IDs for CMS Collections and items. If you have any API integrations relying on these IDs, they must be reconfigured with the new CMS IDs to continue working as expected.
Keep the early published changes
Pros:
Reduces need to manually comb through elements and pages to identify specific changes to revert or retain.
Reduces need to redo any prior work, comparative to alternate options.
Eliminates risk of broken API connections, comparative to restoring a backup.
Cons:
Runs risk of unintended user experience or user journey on site (e.g., broken navigation links, inconsistent design elements, etc.).
Related resources
Image resets in Webflow
Adding explicit width and height values to avoid performance issues related to images