← All guides

August 15, 2026 · 6 min read

HubSpot form version history: what exists, what doesn’t, and how to get it

Pages and emails have revision history in HubSpot — forms don’t. What the API actually stores, why the audit log won’t help, and every workaround that exists in 2026.

Edit a landing page in HubSpot and you can roll back to any previous version — revision history is built in. Edit a form — change a field, delete an option, reword the consent checkbox — and there is no history at all. No versions, no “what changed”, no undo. The form is whatever it is right now, and whatever it was yesterday is gone.

Users have been asking HubSpot for form version history since 2018 — the Ideas thread has hundreds of upvotes, and in 2020 HubSpot replied that it wasn’t on the roadmap. As of 2026, nothing has shipped.

What actually exists natively

• updatedAt — the Forms API returns a timestamp of the last modification for each form. It tells you when something changed. Not what, not who, and only the most recent change.
• The centralized audit log (Enterprise) — covers logins, exports, settings and content-object actions, but form field edits are not itemised. There’s a long-standing Ideas thread asking for exactly that.
• Page revision history — restores the page, not the form embedded on it. A form is a separate object; rolling back the page doesn’t touch it.

Why this bites teams

Forms sit at the top of the revenue funnel, and small edits have outsized blast radius: mark one field required and conversion drops by a third; hide the field a workflow filters on and enrollment silently stops; reword a consent checkbox and your legal team loses the evidence trail. The breakage almost always surfaces downstream and later — a list stops filling on Friday evening, and on Monday nobody remembers touching anything.

The workarounds that exist

1. Scheduled JSON exports. The API returns each form’s full definition — fetch every form on a schedule and commit the JSON to git. Diffs become your version history. Works; requires a developer, a place to run it, and someone to keep it alive forever. (Our changelog guide shows the exact loop.)
2. Change-log discipline. A spreadsheet where everyone records form edits by hand. Survives roughly one sprint.
3. Clone-before-editing. Duplicate the form before big edits so the copy acts as a snapshot. Clutters the portal, dies the day someone edits the original directly.

One honest limitation: “who”

The public API does not expose which user changed a form — no external tool can tell you that part, whatever it claims. The what and the when can be reconstructed externally; the who only HubSpot can ship.