# Rollback to the version you published before

Every upload is kept as its own version. If the new one is wrong, put the previous one back on the same address in one step, with no re-upload.

## Plan availability

Rolling back to an earlier version starts on Pro, which keeps 10 of them.

- **Free:** not included
- **Starter:** not included
- **Pro:** included
- **Business:** included
- **Enterprise:** included

## Publishing is additive, so undo is cheap

A new upload does not overwrite the old one. It becomes a new version, and the address is pointed at it.

Every time you publish, the files are extracted into their own immutable folder and the live address is switched to point there. The previous folder is still on disk, untouched. Rolling back is that switch running in the other direction: the address moves back to the earlier version and the site is correct again in seconds, without you finding the old ZIP, without a re-upload, and without the address changing at any point.

How far back you can go depends on the plan, because keeping versions costs storage; Pro keeps 10. Older versions fall off the end as new ones arrive, so the list is a recent history rather than an archive, and it is measured in publishes rather than in days: a site you update twice a year keeps a much longer stretch of calendar time than one you update twice a week.

This is the feature that makes it reasonable to publish a change you are not certain about, which is most of them. It pairs naturally with a preview link for the changes you would rather not publish at all until somebody has looked, and it is the reason the same-URL rule works in practice: re-publishing at will is only comfortable if getting back is trivial. It also changes what a bad deploy costs. Without it, the honest answer to "the new version is broken" is to fix it under pressure, because there is nothing to go back to; with it, the answer is to restore, then fix it properly, which is a different afternoon.

## How to use it

1. **Publish as usual.** Each upload becomes a version automatically. There is nothing to enable and no commit message to write.
2. **Open the version list.** The site's history shows every kept version with when it was published and which one is live.
3. **Restore one.** Pick a version and put it back. The address does not change, so links you already sent keep working.

## When people reach for this

- **A build that broke something after it went out.** A missing asset or a wrong path is obvious only once it is live. Rolling back buys the time to fix it properly instead of fixing it in a hurry.
- **A client who preferred the previous version.** This happens, and re-uploading last week's export is a bad way to answer it. See static hosting for freelancers for the surrounding workflow.
- **A price list or menu that changed too early.** Content that goes out on a schedule sometimes goes out a day early. Rolling back is faster than editing it back.

## Doing this without us

Without kept versions, undo means finding the old files and uploading them again.

- **Finding the previous build.** Droply: It is in the site's version list. Re-uploading an older export: Wherever you happened to save it, if you did.
- **How long it takes.** Droply: A pointer switch, in seconds. Re-uploading an older export: A rebuild, or a re-upload, or both.
- **Whether the address changes.** Droply: It does not. Re-uploading an older export: It should not, but only if you overwrite in place correctly.
- **How far back you can go.** Droply: 10 versions on Pro. Re-uploading an older export: As far as your own backups reach.

Compared against keeping your own copies of each build, which is what a static site without version history requires. Checked September 2026.

## When this is not the right tool

This is undo for what you published. It is not source control and it is not a backup service.

- It keeps published output, not your project source. Your repository is still where the source belongs.
- There are no branches, no diffs between versions and no merge. It is a list of what was live, in order.
- History depth is limited per plan, so a very old version eventually falls off the end.
- Free plans keep the current version only, which means the previous one is not there to restore.

## Frequently asked questions

### Which plan includes rollback?

Restoring an earlier version starts on Pro, which keeps 10 versions. Plans below it publish normally; what they do not get is the list to restore from.

### Does the URL change when I roll back?

No. The address belongs to the site rather than to a version, so rolling back is invisible to anyone holding a link.

### How long does it take?

Seconds. The files for the older version are already on disk, so restoring is a pointer switch rather than an upload.

### How many versions are kept?

It depends on the plan, because each kept version uses storage. Pro keeps 10, and higher tiers keep more.

### Can I roll back after connecting a custom domain?

Yes. A custom domain points at the site, not at a version, so it follows the rollback like any other address.

### Is this a backup of my project?

No. It stores what you published, which is your built output. Keep your source in version control the way you would anyway.

## Related features

- [Expiring links](https://droply.host/features/expiring-links)
- [Site import](https://droply.host/features/site-import)
- [Password protection](https://droply.host/features/password-protection)