Deploy HistoryRestore Any Version in One Click
Every update to a site on Dplooy keeps the version it replaces. Redeploy, push, publish or save, then open Versions to see what changed and put the previous version back. The one you replace is kept too.
A bad update is a two-click fix
Most hosting makes an update final: the old files are gone the moment the new ones land. On Dplooy the old files become a version first. You don't set anything up, and you don't need to have thought about it before the update went wrong.
A restore is just another update, so it keeps the version it replaces too. There is always a way back, in both directions.
- Every version names the files it edited, added or removed
- Files change on restore, settings never do
- Scanned again before it goes live
- 1
Update the site as you always do
Drop a new ZIP or folder on the dashboard, push to GitHub, publish from the Site Builder, deploy through the API, or save in the Code or Visual Editor.
- 2
The version you replaced is kept
Before the new files are written, the current ones are copied into a version. Plus keeps the previous version of each site, Pro keeps the last three. Nothing to switch on.
- 3
Open Versions and read what changed
Open the site and choose Versions under Deploy. Each version says where it came from and names the files it edited, added or removed. Add a note when the reason matters more than the files.
- 4
Restore, and keep the way back
Click Restore, read what will change on the live site, confirm. The version you just replaced is kept too, and the toast has Undo.
Where versions come from
Every way a site changes on Dplooy keeps the version it replaces. Editors ask first, so you decide.
- ZIP or folder redeploy
- Kept before the old files are removed.
- GitHub deploy and Deploy on every push
- Kept before each deploy, with the commit noted on the version.
- API and MCP deploys
- Kept before each deploy. File edits within ten minutes of each other count as one version.
- Site Builder publish
- Kept before the page is republished.
- SEO auto-fix
- Kept before the fix is written to your files.
- Code Editor and Visual Editor
- The first save of a session asks Keep a backup first? Yes keeps one version, no keeps none — so editing can't push out the backup of your last deploy.
- Restore
- Kept and labelled Restored, so a restore is never one-way.
Restore without holding your breath
Everything around a restore is designed so you know what will happen before it does, and can take it back after.
See the change before you make it
The Restore confirm lists the files that will be edited, added or removed on the live site, and says if an older version will be removed to stay within your limit.
Undo
The toast after a restore has Undo. It restores the version the restore just created, so the site is back the way it was in seconds.
Keep
Pin one version per site and it never rotates out, whatever you deploy next. Move the pin whenever you like.
Notes and summaries
Each version gets an automatic one-line summary naming the files that changed. Write your own note when the reason matters more than the files.
Scanned again
Every restore runs the version through the same content scan as a fresh deploy before anything is copied.
Settings stay put
Restore replaces files only. Password, email gate, custom domain, forms, bookings, chatbot, Google Analytics and analytics history are untouched.
Included with Plus and Pro
The limit is per site, so one site's history never competes with another's. Versions don't count toward your storage.
| Feature | Free$0 | Plus$4.99/mo | Pro$12.99/mo |
|---|---|---|---|
| Versions kept per site | — | 1 | 3 |
| Restore in one click | |||
| Change preview and Undo | |||
| Keep one version safe | |||
| Notes and file summaries | |||
| Counts toward your storage | — | No | No |
See everything the plans include on the pricing page
Frequently asked questions
What counts as a version?
The state of your site before an update replaced it. A ZIP or folder redeploy, a GitHub deploy or push, an API or MCP deploy, a Site Builder publish, an SEO auto-fix and a restore all keep the version they replace. Editor saves keep one when you answer yes to the backup question at the start of the session.
Which plans include deploy history?
Plus and Pro. Plus keeps the previous version of each site; Pro keeps the last three. The limit is per site, so one site's history never competes with another's. Free sites expire after three days and keep no versions.
Does every save in the Code Editor create a version?
No. The first save of an editing session asks whether to keep a backup first. Yes keeps exactly one version, the site as it was before you started; no keeps none. Later saves in the same session never create versions, so editing can't push the backup of your last deploy out of the list. File edits made through the API within ten minutes of each other are grouped into one version for the same reason.
What exactly does Restore change?
The files, and nothing else. The live site ends up equal to the restored version: files it contains are copied back, and files it doesn't contain are removed. Your password, email gate, custom domain, forms, bookings, chatbot, Google Analytics, 404 page and analytics history are untouched.
Can I undo a restore?
Yes. A restore keeps the version it replaces, exactly like any other update, so the site you had a moment ago is the newest row in the list. The confirmation toast also has an Undo button that restores it in one click.
What happens when I reach the limit?
The oldest version that isn't kept is removed when a new one is created. Before you restore, the confirmation tells you which version will be removed to stay within your plan's limit. Click Keep on a version and it is never removed, whatever you deploy next — one kept version per site, and the pin can be moved.
Do versions count toward my storage?
No. The storage figure in your dashboard is about your live sites. Versions are kept alongside them and bounded by the per-site limit, so they cost you nothing against your quota.
Is a restored version checked before it goes live?
Yes. Every restore runs the version's HTML, CSS and JavaScript through the same content scan as a fresh deploy before anything is copied. A version that no longer passes cannot be restored.
What happens to my versions if I downgrade or delete the site?
A downgrade keeps your existing versions; the new limit applies the next time that site is updated. On the Free plan the versions stay listed but cannot be restored. Deleting a site deletes its versions with it.
Which projects get versions?
Every website: a single HTML page, a folder or ZIP upload, a GitHub deploy, a Site Builder site or anything deployed through the API or MCP. A file share — a PDF or image on its own link — isn't a website and doesn't get versions.
Related
- ZIP deployUpload a ZIP and the whole site goes live — the version it replaces is kept.
- GitHub deployDeploy on every push, with the commit noted on each version.
- Plans and pricingWhat Free, Plus and Pro each include, and what changes when you upgrade.
- DocumentationEvery deploy method, feature and plan limit in one place.
Update your site without the “what if”
Deploy the change. If it's wrong, the version before it is one click away, and the one you replace is kept too.