Managing your applications effectively is key to maintaining an organized workspace. Baserow provides high-level configuration options directly from your dashboard, allowing you to create safe testing environments, maintain backups, and organize your projects without affecting your live data.
This guide covers how to control the lifecycle of your Baserow applications: rename, duplicate, back up, and delete.

These configuration options are performed at the Workspace level, rather than inside the Application Builder.
You can update your application’s name at any time. This name is used for internal reference within your Baserow dashboard and workspace sidebar.
Changing the name does not affect the published URL or the title displayed to public users.
⋮ icon next to the application.
Duplicating an application creates an exact, independent copy of the application in its current state. This is useful for testing new features without breaking your live production app.
⋮ icon.You can monitor the progress in the sidebar. The copy will appear in the same workspace.
Snapshots allow you to save the state of your application at a specific point in time. Unlike a duplicate, a snapshot is not an active application but a restore point.
To create a snapshot:
⋮ icon next to the application.To restore a snapshot:
| Feature | Duplicate | Snapshot |
|---|---|---|
| Primary use | Testing, Development, Branching | Backup, Version History |
| Editable? | Yes, immediately editable. | No, must be restored first. |
| Storage | Counts as an active application. | stored as a backup file. |
| Retention | Indefinite (until deleted). | 1 Year. |
Deleting an application removes it from your workspace view. However, Baserow includes a safety net for accidental deletions.
⋮ icon next to the application.Recovery: Deleted applications are moved to the Trash. You can typically restore them within a specific grace period before they are permanently purged. Read more about data recovery.
No. The application name is for your internal dashboard organization only. The public URL is determined by the domain settings, not the application name.
Snapshots are tied to the application. If you need to move data, it is best to restore the snapshot as a new application, and then export/import the workspace.
The application and its pages are moved to the trash. The underlying Database is separate; if your application was connected to a database, deleting the application does not delete the database tables.
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions; we’re ready to assist you.