Restoring a previous version of a HubSpot theme is simple: everything happens in the Design Manager, via the View revisions menu. HubSpot automatically saves every change made to theme files (templates, modules, CSS, JS), allowing you to roll back in just a few clicks. The only rule to remember: restore the correct version, then publish the changes to apply them to the site. For pages, the history is accessible directly from the editor.
In short: if an update breaks your theme, you can revert to a stable version in under a minute.
Discover our best HubSpot Agency tips!
HubSpot automatically keeps a history of most elements you modify. Concretely, you can restore:
All pages (website pages, landing pages, blog posts) have a history accessible from the editor. Each unpublished save creates a restorable version.
In the Design Manager, each template, module, HTML/HubL file, CSS, or JS file has its own history. This is where you restore a broken theme or module version.
An email that has already been sent cannot be restored.
A deleted page cannot be recovered via history: only HubSpot Support can restore it.
In summary: almost everything is versioned in HubSpot, except content that has already been sent or permanently deleted.
To roll back a theme file, module, or any coded file, everything happens in the Design Manager, where HubSpot stores the complete history of each element.
In your HubSpot account, go to: Content → Design Manager. Then select the relevant file (template, module, CSS, JS…).
Click Actions → View revisions. HubSpot displays all previous saves: who modified what and when.
Select the version that worked, click Restore, then Publish changes.
Without publishing, the restoration will not be applied to the site pages. This is the most reliable method to fix a broken theme or module: three clicks and everything is back in order.
For a website page, landing page, or blog post, HubSpot automatically saves all unpublished versions. Restoration is done directly from the editor.
From the relevant page → View → Version history (You can also access it via the “Saved” status in the top right.)
Click a version to preview it, then click Restore. HubSpot creates a new draft based on this version: you can visually check it, then publish to make the restoration live.
Simple, fast, no technical handling required.
Even though HubSpot makes restoration easy, a few simple habits help prevent 90% of issues.
Most important: never modify a theme’s source directly.
This is the cleanest method: changes are isolated, easy to undo, and have no impact on the original theme.
Before editing a global module, CSS/JS file, or template, create a copy. In case of a bug → instant rollback.
Whether it’s a file, module, or template: a restoration only becomes effective after clicking Publish changes.
→ You probably forgot to publish. Restoring alone does nothing on the front end.
→ Often caused by a missing module in the older version.
Solution: restore only the impacted file, not the entire theme.
→ The file or page has never been published, so no version exists yet.
Theme file restoration is done in the Design Manager. Path: Content → Design Manager → relevant file → Actions → View revisions.
Then simply select the desired version, click Restore, and Publish changes to apply the rollback across your HubSpot site.
Because a restoration is only active after publishing. Even if the version is restored in the Design Manager, it remains in “draft” state until you click Publish changes.
Once published, it propagates to all pages using that file.
No, not directly from your account. The history disappears when a page is deleted.
The only solution is to contact HubSpot Support, who can sometimes restore the page from their system backups.
Yes, but only for:
draft emails,
automated emails.
However:
an email that has already been sent cannot be restored,
its history is no longer accessible.
In case of an error, you can duplicate the email to fix it.
This often happens when you restore a theme version in which certain modules did not yet exist. As a result, some pages lose blocks or display incorrectly.
Recommended solutions:
restore only the impacted file rather than the entire theme;
check the module’s history in the Design Manager;
use a child theme to isolate changes and avoid incompatibilities.
A few best practices significantly reduce risk:
always work in a child theme,
clone the theme before major changes,
keep a code change log,
test changes on a draft page before publishing,
use HubSpot CLI + GitHub for proper version control if doing advanced development.
These measures make restorations simpler—and, above all, much less frequent.
Photo by Steve Johnson