The TYPO3 Recycle Bin: Restoring Deleted Pages and Content

Accidentally deleted a page? Removed a content element and only later realized it was still needed after all? In TYPO3, that's often not a big problem. Because deleted content isn't always gone for good right away.

TYPO3 has a kind of recycle bin called the Recycler. It lets you search for and restore deleted pages, text, images, and other records.

What happens when I delete something in TYPO3?

Anyone who has deleted a file on a computer knows the recycle-bin principle: the file first disappears from its original folder but can be restored if needed.

TYPO3 works a bit differently, though the result is similar.

If, for example, a content element is deleted, TYPO3 often doesn't remove the corresponding record from the database right away. Instead, it's marked as deleted.

For the editor and for website visitors, the content has disappeared. Technically, however, it's still in the database.

This approach is also known as a soft delete.

This has a decisive advantage: if content was deleted by accident, there's a good chance it can be restored.

Where is the TYPO3 recycle bin?

The recycle-bin feature is officially called the Recycler in TYPO3.

Depending on the TYPO3 version and the permissions of the logged-in user, the corresponding Recycler module is available in the backend.

There, deleted records can be searched for and displayed.

You can, for example, filter by specific record types. This allows you to search specifically for deleted pages or content elements.

Search depth matters too. If, for example, a deleted page needs to be found, it may be necessary to also search for deleted records below the currently selected page.

Restoring a deleted page

A typical case from everyday editorial work:

An editor wants to remove a single content element but accidentally deletes the entire page.

At first, it looks as though all of the page's content has been lost too.

However, the deleted page can be searched for via the Recycler. If found there, it can be restored. Related or subordinate records can also be taken into account during restoration.

This means even larger accidental deletions can often be undone.

Are restored items immediately visible again?

Some caution is warranted here.

Restoring a record generally restores its previous state. If content was published and visible before it was deleted, it can also reappear on the website after being restored.

After a restoration, you should therefore check whether the page or content element should actually be publicly visible again right away.

Recycler or page history?

TYPO3 offers another way to restore earlier states of content: the change history.

The Recycler and the history serve different purposes, though.

The Recycler is primarily useful when something has been deleted:

"I deleted a page and want it back."

The history, on the other hand, helps especially when content has been changed:

"I changed a text and want the previous version back."

The history also lets you trace when changes were made and which backend user made them.

For editors, both the history and the Recycler are therefore important safety mechanisms in the TYPO3 backend.

Can content also be permanently deleted?

Yes. Given the appropriate permissions, records can also be permanently removed via the Recycler.

That should be done carefully, though.

As long as a record is merely marked as deleted, it can be restored via the Recycler. Once it's permanently deleted, that's no longer possible this way.

Which users may restore or permanently delete content can be controlled via TYPO3's user permissions.

Especially on websites with multiple editors, it's worth assigning these permissions deliberately.

Not every deleted item can be restored

The TYPO3 Recycler is not a substitute for a backup.

Whether a deleted record can be restored depends, among other things, on what type of record it is and how TYPO3 or an extension in use manages that record.

Content that has already been permanently removed from the database also can't simply be retrieved via the Recycler.

A professional TYPO3 installation should therefore be backed up regularly, independently of the Recycler. The Recycler helps with typical everyday editorial mistakes – a backup, on the other hand, also protects against larger technical problems or data loss.

Good to know: the former "Recycler" page type

Anyone who has worked with TYPO3 for a long time may still remember a page type called "Recycler."

This was an older concept where, for example, no-longer-needed records could be placed on dedicated Recycler pages.

This page type was removed in TYPO3 v13.

The Recycler module is still available for restoring deleted records.

Conclusion

An accidental click on "Delete" doesn't automatically mean content is lost for good in TYPO3.

TYPO3 initially marks many deleted records as merely deleted. They can then be searched for and restored via the Recycler – TYPO3's recycle bin.

Especially for websites maintained by multiple editors, this is an important safety feature. Together with the change history and regular backups, the Recycler helps ensure that many everyday content mistakes can be quickly corrected.