How to Clear Expired Cache Data from Joomla

Joomla can remove cache data that has expired while leaving cache entries that are still current. This is different from deleting all cached data and is useful when you want routine cleanup without forcing every valid cache entry to be rebuilt.

Joomla can remove cache entries that have expired while leaving still-current cache data in place. This is useful for routine maintenance because it cleans obsolete cached data without forcing every valid cache entry to be rebuilt. It is different from deleting all cache data, and it will not clear independent caches maintained by a CDN, host, browser, reverse proxy, or third-party service.

Choose expired-cache cleanup when you want targeted maintenance

Use Clear Expired Cache when the goal is to remove entries whose cache lifetime has elapsed. If you are troubleshooting content that must disappear immediately but is still inside its valid cache lifetime, you may instead need to delete the relevant current cache group.

Clearing all current cache is more disruptive because Joomla or its extensions may need to rebuild those entries on subsequent requests.

Clear expired cache data from Administrator

  1. Sign in to Joomla Administrator.
  2. Go to System → Clear Cache in the Maintenance area.
  3. Use the toolbar action for Clear Expired Cache.
  4. Allow the operation to finish before launching it again.

On a site with a large cache, expired-cache cleanup can require noticeable server work because Joomla must identify entries that are no longer current.

Verify the cleanup and the page you were troubleshooting

  1. Reload the cache maintenance screen and confirm Administrator remains responsive.
  2. Retest the frontend or Administrator page involved in the original issue.
  3. If stale output remains, determine whether the relevant cache entry is still current rather than expired.
  4. If necessary, clear only the applicable current cache group and test again.

Do not assume every stale page is caused by Joomla's core cache. Identify the cache layer serving the response before repeatedly deleting data.

If expired-cache cleanup is slow or times out

Large cache volumes, slow storage, PHP execution limits, or constrained hosting can make maintenance requests expensive. If the request times out, check Joomla/PHP logs and server resource limits before assuming the cache files are corrupt.

  • Retry during a lower-traffic period when appropriate.
  • Avoid launching multiple cleanup requests in parallel.
  • Do not manually delete arbitrary directories unless you understand the configured cache handler and what else the directory contains.

Clear other cache layers separately when needed

Joomla's expired-cache action does not purge a hosting cache, CDN, reverse proxy, browser cache, PHP opcode cache, or an extension's independent remote cache. If Joomla's cache is clean but visitors still receive old output, inspect response headers and the site's infrastructure to determine which layer is serving it, then use that system's supported purge process.

Use cache clearing as maintenance, not as the permanent fix

If stale or broken cached output returns repeatedly, investigate the underlying cause: cache lifetime settings, an extension that does not invalidate its cache correctly, deployment/CDN behavior, or a server-level caching rule. Routine cleanup is useful, but repeated manual clearing should not be required for normal content updates.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket