Deleting Blocks & Trash

Moving a block to trash is reversible. Its content and connections are retained, while normal views hide it. Restoring the block makes those connections available again.

Emptying trash permanently deletes the selected content. Cleanup removes its stored content, history and references from surviving documents. Physical file cleanup runs separately and retries failures. Files still used by another block, including a block in trash, are preserved.

Deleting Blocks

Single Block

Select the block you want to delete
In the action sidebar, click Move to Trash
Confirm the deletion in the confirmation dialog

Multiple Blocks

Select multiple blocks (Ctrl/Cmd+Click or Shift+Click)
In the action sidebar, click Move to Trash
Confirm to delete all selected blocks

What Happens When You Delete

When a block is moved to trash:

The block is marked as deleted (soft delete)
Its content remains recoverable until permanent deletion; local cached files may be downloaded again when needed
It's removed from all views, the sidebar, and search results
Its relations (tags, mentions) are disabled
This syncs across devices

Recovering Deleted Blocks

In the left sidebar, you can open the trash with a toggle and select Restore on any entry that you'd like to recover. This will restore all connections, metadata, and file, as these were just disabled while it was in the trash. This will sync to all devices.

Permanent Deletion

Open Trash in the left sidebar and select Empty Trash. Confirm the action after reviewing the affected items. This cannot be undone.

The server confirms which blocks were permanently deleted before the app removes them from the trash view. Reference cleanup uses the same document operations as cloud account deletion and does not require opening each surviving note. A pending-cleanup message means deletion was recorded but some local storage work still needs to finish.

Minimal deletion records remain so an offline device cannot recreate the deleted block. Backups follow the separate Privacy Policy; independent exports and copies on other servers are not erased.