Delete Expired Transients

plugin banner

delete old, expired transients from WordPress wp_options table

Author:WebAware (profile at wordpress.org)
WordPress version required:3.7
WordPress version tested:6.5
Plugin version:2.0.7
Added to WordPress repository:27-07-2013
Last updated:17-03-2024
Rating, %:100
Rated by:13
Plugin URI:https://shop.webaware.com.au/downloads/delete...
Total downloads:88 816
Active installs:6 000+
plugin download
Click to start download

Delete old, expired transients from the WordPress options table (wp_options), to prevent them from bloating your database and even slowing down your website.

Unless you are using an object cache (like memcached), WordPress stores transient records in the options table. Many transients are given an expiration time, so in theory they should disappear after some time. In practise, because old transients are only deleted when requested again after they’ve expired, many transients stay in the database. After a while, there can be thousands or even millions of expired transients needlessly taking up space in your options table, depending on what your plugins are doing.

Delete Expired Transients schedules a daily task to delete any expired transients from the options table. It performs this operation with a single SQL query, and then runs a second query to find any orphaned expiration records and deletes them too.

There are a few other plugins around that clean up expired transients. This one is written for fast performance, set-and-forget scheduled housekeeping, and maximum compatibility. It uses the PHP time to determine whether transients are expired, not the database time (which can be different). It does only one job, and it does it well with the minimum of resources.

Now optimised for WordPress Multisite.

Translations

Many thanks to the generous efforts of our translators:

If you’d like to help out by translating this plugin, please sign up for an account and dig in.

Contributions

Privacy

Delete Expired Transients does not collect any personally identifying information, and does not set any cookies. It removes some old information from the database, potentially reducing a website’s exposure to leakage of personally identifying information.


Screenshots
FAQ
ChangeLog