# Table tabs, rename, and deletion

Select a table in the App's Tables list to open it in a grid tab. Select another table to compare their contents by switching tabs. Selecting a table already open focuses its existing tab rather than creating a duplicate.

## Close and reopen

Closing a tab removes it from the current browsing workspace. The table remains in the server-backed Tables list. Reopen it to load a fresh window of its saved rows.

The tab strip is in-memory state and can disappear after a browser reload. Saved tables and their rows persist. A missing tab after reload is not evidence that the table was deleted.

## Read paged rows

Table rows load in windows. The footer can show how many rows are loaded relative to the table count. Continue loading to inspect the full table. “Loaded 0 of 0” is a valid state for a newly created empty table, not a generation success or failure by itself.

## Rename

Use the table's management menu to rename it. Review the prefilled name, save, and verify the updated list. Renaming helps navigation; it does not define a new extraction schema or move the table into another App.

## Delete

Use the table management delete action and confirm the intended table. Deleting the table is separate from closing its tab. It removes the saved table and its rows from the App's table list.

Before deleting, check whether App workflows or other components expect that table. Replaying an earlier draft's acceptance receipt does not promise to recreate a later-deleted table. Generate or create a new table deliberately if that is the intended next step.

For provider database tables, see [connection tables and vectors](/docs/connections/tables-and-vectors).