Every WordPress site makes database queries. Some are fast — fetching a single post by ID. Others are slow — complex WP_Query calls with multiple meta conditions, or fetching data from external APIs. The Transients API lets you cache these expensive operations so they only run occasionally, dramatically improving page load times.
This guide covers how to use the WordPress Transients API to cache database queries, API responses, and expensive computations.
What Are Transients?
Transients are temporarly cached data stored in the WordPress database or object cache with an expiration time. Unlike the Options API, which stores permanent data, transients are designed for data that becomes stale after a specific period. They’re perfect for caching the results of expensive operations that don’t need to be fresh on every page load.
Transients automatically expire after their set time period, and they can be preemptively deleted when you update the underlying data. If your site uses an object cache like Redis, transients are stored in memory, making them even faster.
Basic Transient Operations
Set a transient with set_transient(), passing a unique key, the data to store, and the expiration time in seconds. Retrieve it with get_transient(), which returns false if the transient has expired or doesn’t exist. Delete it with delete_transient() when you need to clear the cache.
The standard pattern is to check for an existing transient, use it if it exists, and regenerate it if it doesn’t. This pattern keeps your code efficient without manual cache management.
Caching Expensive Queries
The most common use case for transients is caching complex WP_Query results. If your plugin displays a list of related posts, recent comments, or popular products, wrap the query in a transient. Set a reasonable expiration time based on how frequently the data changes — hourly for frequently updated sites, daily for static content.
Delete the relevant transients when the underlying data changes. For example, when a new post is published, delete the “recent posts” transient so the next page load shows the updated list.
Caching External API Responses
External API calls are slow and unreliable. If your plugin fetches data from a third-party API — weather data, stock prices, social media counts — cache the response with a transient. This protects your site from API downtime and dramatically improves page load times for users.
Set a longer expiration time for data that changes slowly. Set a shorter time for real-time data. Always handle the case where the API is unavailable and the transient has expired — fall back to stale cached data rather than showing an error.
Transient vs Other Caching Methods
Transients are one of several caching tools in WordPress. Page caching serves entire HTML pages to anonymous visitors. Object caching stores database query results. Transients are best for caching the output of specific, expensive PHP operations that aren’t covered by page or object caching.
Use transients when you need to cache the result of a specific function or query that takes more than 100ms to execute. Use the Options API for data that should persist indefinitely. Use the object cache directly only when you need more control than transients provide.
The Bottom Line
The Transients API is one of the most effective performance tools for WordPress developers. It lets you cache expensive operations with minimal code, automatically handling expiration and cleanup. Identify the slowest parts of your plugin — complex queries, API calls, heavy computations — and wrap them in transients. The performance improvement is often dramatic.