Delete a table from your database

Remove tables you no longer need from your database. Understand the trash recovery period, what gets deleted, and when to consider alternatives like archiving or exporting.

Overview

Deleting a table removes it and all its contents from your database, making it inaccessible to everyone with database access. Baserow provides a grace period where deleted tables can be recovered from trash, but after that window closes, deletion becomes permanent and irreversible.

This action affects not just the table itself but also any views, formulas in other tables that reference it, and linked relationships with other tables.

Table deletion is permanent after the grace period. Always export or back up important data before deleting.

Delete table option in sidebar menu

How to delete a table

Deletion works through the table menu in your sidebar, giving you confirmation before the table is removed.

Step-by-step process

  1. Locate the table you want to delete in your database sidebar
  2. Click the ⋮ icon next to the table name
  3. Select Delete from the dropdown menu
  4. Confirm the deletion in the dialog box that appears
  5. Watch for the undo notification at the bottom-right corner (5-second window)

The table disappears immediately from your sidebar and moves to the trash. You have a limited time to recover it from the trash before permanent deletion.

What gets deleted

When you delete a table, Baserow removes comprehensive information beyond just the visible data.

Table contents deleted: All rows and their data values, all fields and their configurations, all views including Grid, Gallery, Kanban, Calendar, and Timeline views, filters, sorts, and grouping configurations, row comments and revision history, and all uploaded files stored in file fields.

Database impacts: Formulas in other tables that reference the deleted table will show errors. Link to table fields in other tables that are connected to the deleted table become broken and show empty values. Lookup and rollup fields that pulled data from the deleted table stop working. Webhooks configured for the deleted table are removed automatically.

What remains: The database structure itself stays intact. Other tables in the same database are unaffected unless they have relationships with the deleted table. Database-level settings, permissions, and configurations persist. The table name becomes available for reuse on new tables.

Recovery options

Baserow provides safety nets against accidental deletion, but they’re time-sensitive.

Immediate undo (within 5 seconds)

Right after deleting a table, a notification appears at the bottom-right corner with an “Undo” button. Click this button within 5 seconds to instantly restore the table as if deletion never happened. This is the fastest recovery method and prevents the table from entering trash entirely. The undo window is brief; watch for the notification immediately after confirming deletion.

Trash recovery

If you miss the 5-second undo window, deleted tables remain in the trash for a limited time. During this grace period, you can restore them with all data, views, and configurations intact.

After the grace period, tables are permanently deleted from trash automatically. No recovery is possible after this point; data is completely erased from Baserow servers.

Learn more: Restore data from trash

Before you delete: Consider alternatives

Deletion is permanent after the grace period, so consider whether other options better serve your needs.

Export then delete

If you might need table data later but want to free up space or reduce clutter, export the table before deleting. This creates an offline backup you can reference or re-import if needed. Export formats include CSV for spreadsheet compatibility, Excel for formatted data, JSON for programmatic use, or XML for technical integrations. Store exports in cloud storage or backup systems for long-term access.

Learn more: Export tables

Duplicate for archival

Create a duplicate of the table with “(Archive)” in the name, then move it to an archive database. This keeps historical data accessible in Baserow without cluttering your active workspace. You can restrict permissions on archived tables to prevent accidental editing while maintaining the ability to reference old information when needed.

Learn more: Duplicate tables

Hide instead of delete

If the table isn’t needed daily but contains reference information, keep it, but reorder it to the bottom of your sidebar. You can also create a separate “Archive” database and move old tables there. This keeps data accessible without permanent deletion while reducing visual clutter in your active workspace.

Clear data, keep structure

If you want to reuse the table structure but start fresh with data, delete all rows instead of the entire table. This preserves your carefully configured fields, views, formulas, and relationships while clearing out old data. Use filters to select all rows, then bulk delete them, leaving an empty table ready for new data.

Delete vs. alternatives decision guide

Choose deletion when: The table was created for testing or experimentation and is no longer needed, data is completely outdated and has no archival value, the table duplicates information better organized elsewhere, or you’re certain no one will need this data again.

Consider alternatives when: Data might be needed for reference or compliance, the table structure took significant time to configure, other tables link to this one, and you’re unsure of the impact, or you’re cleaning up but not certain about permanent removal.

Red flags suggesting alternatives: Other team members might need access, formulas in other tables reference this table, the table contains historical data for reporting or audits, or you haven’t verified whether linked tables will break.

Frequently asked questions

Link to table fields that are connected to the deleted table become empty and show no linked records. Lookup fields that pull data from linked records stop working and display errors. Rollup fields that are calculated across relationships also break. Formulas referencing the deleted table show error messages. These broken references don’t automatically fix themselves; you’ll need to manually update affected tables.

Who can delete tables?

Table deletion requires appropriate permissions. Workspace admins can always delete tables. Users with creator or admin roles at the table level can delete those specific tables. Members and viewers cannot delete tables even if they can access them. Check your role-based permissions if you can’t find the delete option.

Does deleting a table affect my storage quota?

Yes, deleting tables frees up storage space, but the space isn’t released until the table is permanently removed from trash after the grace period. While tables remain in trash during the grace period, they still count toward your storage quota. Once permanently deleted, all associated storage (row data and uploaded files) is freed.

Can I selectively delete data instead of the entire table?

Yes, you can delete individual rows or groups of rows without removing the table. Use filters to select specific rows, then delete them in bulk. You can also delete individual fields (columns) without removing the table. Only use table deletion when you want to remove the entire structure and all its contents permanently.

Related content

Related table operations:

Data management:

Alternatives to deletion:

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.