Lesson 15 · Save, publish and launchBack up and recover your data
Project History keeps your files. Your database has its own backups.
Project History brings back your site’s files, and your data has a safety net of its own. Learn how 3Edit backs up your database before the agent changes it, how long those backups are kept, and how to restore just the tables you need.
About 6 minutes to readLast updated
On this page
Your files and your data
A web app has two kinds of things to keep safe. Your files are the site itself: its pages, design and code. Your data is what the site collects as people use it: accounts, bookings, orders and messages, kept in your database.
Project History, from Versions, backups and GitHub, looks after your files: a restore brings back your site’s files, and your database contents stay just as they are. Your data has its own backups, separate from Project History.
| Project History | Database backups | |
|---|---|---|
| Keeps | Your site’s files | Your database’s data |
| Saved | Before and after a normal completed edit | Before the agent changes your database |
| Kept | The last 25 versions | About 30 days, and the newest verified backup is always kept |
| To restore | Press Restore beside a version | Ask the chat |
A backup before each database change
When the agent is about to change your database, for example to add a table or change an access rule, 3Edit normally saves an encrypted backup on your computer first. The chat tells you when it has, with a line that begins “Saved a database backup before this change. Kept on this computer until”, followed by the date.
Backups are kept for about 30 days, and the newest verified backup is always kept, so your latest good copy is never cleared away.
Recover your data
Restoring data is a short conversation with the chat, one step at a time.
- List your backupsAsk the chat to list your database backups.
- Choose onePick the backup from before the change you want to undo.
- Name the tablesAsk the chat to restore only the tables you name, such as bookings, from that backup.
- A backup comes firstBefore it restores anything, 3Edit backs up your current database, so today’s data is kept too.
Restore only what you need
A backup holds your data as it was when it was saved. Anything added since, such as a booking a customer made this morning, isn’t in it. Naming only the tables you need keeps everything else just as it is.
Not sure which tables a change touched? Ask the chat to explain what restoring would change before it restores anything.
Good habits for your data
- Look for the backup line: when the chat says it saved a database backup, you know there is a way back from that change.
- Plan big database changes: ask the AI to explain which tables will change before it builds, as Writing prompts that build what you mean shows.
- Try new features with practice data: test bookings or orders first, before real customers use the feature.
- Moving to a new computer? Your database stays in your own Supabase. Move your project to another computer shows how to reconnect it.
Try it in 3Edit.
Practise on a project with your Supabase connected, such as the booking request site from Does my website need a database?, with two or three test booking requests saved first. Use practice details, never real customers’ details.
The businesses in these prompts are fictional practice examples. When you build for a real business, only ever show real reviews from real customers: invented reviews mislead customers and are against UK consumer law.
- 1Explain the safety nets
Explain, in plain words, the difference between Project History and my database backups for this project: what each one keeps, and what each one brings back. Don’t change anything.
- 2A database change
Add a private note to each booking request, so I can write something like “Bring extra cloths”. Only I can see or change these notes. Before you change the database, tell me which table will change.
Look for the line in the chat that says a database backup was saved before this change.
- 3List your backups
List my database backups for this project. Don’t restore anything.
- 4Restore one table
From the newest backup in that list, explain what restoring only the booking requests table would change, and wait for me to say yes before you restore it. Leave every other table as it is.
Read each answer before you reply. On a live site, restore only after you’ve checked what will change, because anything saved since the backup isn’t in it.
Do it step by step.
This lesson explains the what, the why and the when. These guides and pages show every click.
- Connect Supabase to 3EditYour data lives in your own Supabase: create your free account, then connect it in a few clicks.Read the guide
- Connect GitHub to 3EditKeep your code in a private repository in your own account, updated each time you save.Read the guide
- Security basics for vibe-coded appsAccess rules, secret keys and looking after your users’ data.Read the guide
Next: Move your project to another computer
About the author.
Written by Humayun Rashed, founder of 3Edit. He also runs 3Edit’s free in-person AI website building and vibe coding course in London.
Questions people ask.
No. Project History brings back your site’s files, and your database contents stay just as they are. Your database has its own backups, separate from Project History.
Before the agent changes your database, 3Edit normally saves an encrypted backup on your computer, and the chat tells you it has saved one.
About 30 days, and the newest verified backup is always kept.
Ask the chat to list your database backups, then ask it to restore the tables you name from the backup you choose. 3Edit backs up your current database first.
Yes. Name the tables you want back from the backup you choose, and the rest stay just as they are.
Start vibe coding today.
Download 3Edit for Mac or Windows and build your first professional website in minutes.