Appearance
Version History
Track, label, and restore previous versions of your database schema.
WARNING
Version History is available on Pro and Team plans.
Overview
Every time you save your project, ERDHub captures a snapshot of your schema. The Version History panel gives you a timeline of all snapshots so you can review past states, compare changes, and restore previous versions when needed.
Accessing Version History
Open the History panel from within the editor. The panel displays a chronological list of all snapshots for the current project, with the most recent at the top.
Each snapshot shows:
- Timestamp — when the snapshot was created
- Creator — who made the change (useful in collaborative projects)
- Label (if assigned) — a custom name for the snapshot
Labeling Snapshots
Add custom labels to important snapshots so you can find them quickly later.
Examples of useful labels:
- "Before adding payments tables"
- "v2 schema — approved by team"
- "Pre-migration baseline"
Labels are especially valuable in long-running projects where the history grows large. Instead of scanning timestamps, you can look for your labeled milestones.
Restoring a Version
To restore your project to a previous snapshot:
- Open the History panel
- Find the snapshot you want to restore
- Click Restore
- Confirm in the dialog that appears
TIP
ERDHub automatically creates a safety snapshot of your current state before performing the restore. This means you can always get back to where you were — restoring is never destructive.
After restoring, your DSL editor, canvas, and schema panel all update to reflect the restored version.
Copying a Version
Instead of restoring (which replaces your current schema), you can copy any historical version into a brand-new project. This is useful when you want to:
- Branch off from an earlier design without affecting the current project
- Create an alternative schema based on a past snapshot
- Archive a point-in-time version as a separate project
Auto-Save and History
ERDHub auto-saves your work as you edit. Each auto-save can create a history entry, but to avoid flooding your timeline with minor edits, auto-save entries are throttled with a minimum 5-minute gap between them.
Manual saves always create a history entry regardless of the throttle.
Retention
Snapshots are retained for 90 days. After 90 days, older snapshots are automatically removed.
TIP
If you have a critical milestone you want to preserve beyond the retention window, use Copy version to create a separate project from that snapshot.
Navigating Large Histories
For projects with many snapshots, the History panel uses cursor-based pagination. Scroll to the bottom of the list to load older entries automatically. Combined with snapshot labels, this makes it easy to navigate even months of history.
Best Practices
- Label before major changes — Before a big refactor or migration, label your current snapshot so you can get back to it easily.
- Use copy for experiments — When exploring a new schema direction, copy the current version to a new project instead of modifying in place.
- Review before restoring — Check the timestamp and label carefully to make sure you are restoring the right version. The confirmation dialog is there for a reason.
Next Steps
- Editor Overview — learn about the full editor interface
- Import & Export — bring in SQL or export your diagram
- Collaboration — real-time editing features