How backups work
Automatic backups run weekly and are kept 30 days. The first runs within seven days of the site going live.
Three other things trigger one without being asked:
- Before every WordPress core update.
- Before a staging push overwrites live. If that backup fails, the push is abandoned.
- Whenever you press Back up now, capped at one an hour.
Restores are free and unlimited
There is no per-restore charge and no allowance. A restore never touches your domain or DNS — the content goes back, the address does not move, and nothing needs reconnecting.
A backup restores whole: files and database together. There is no file-level or table-level restore.
See taking a backup and restoring one.
Your own copy
Download a copy gives you a .tar.gz of files and database
— the format every other WordPress host accepts. It is your site as it is
right now, not one of the restore points.
What this can’t do
You cannot change the schedule or the retention. Weekly for 30 days is fixed on every plan.
What to do: take manual backups before anything risky, and download a copy for anything you want kept beyond 30 days. For a stricter schedule, a WordPress backup plugin writing to your own storage runs alongside ours.
Individual backups can't be deleted. They age out after 30 days on their own, and they don't count against your storage, so there is nothing to tidy.
An entry taken seconds after another may not restore.
What to do: use the next one down, and tell us the date if you needed that exact point.
Staging copies are not backed up.
What to do: back up live before a big staging change. A sync rebuilds staging in minutes anyway.
MiniPressy has no backups at all.
What to do: install a WordPress backup plugin and send the files somewhere you control, before you build anything you would mind losing.
Didn’t solve it?
Write to us with your Pressy’s address and what you were doing when it went wrong. Answered by the people who built it.
Last updated