WP

WP Super Cache

by Automattic

A long-standing static page cache from Automattic that serves cached HTML files to logged-out visitors.

4.31,346 WordPress.org reviewsPerformanceFree

This link may earn us a commission. It never changes our rating.

What WP Super Cache does

A long-standing static page cache from Automattic that serves cached HTML files to logged-out visitors.

It sits in the performance part of a WordPress stack and is sold by Automattic on a free basis. We recommend it in our performance guides because it does that one job well without asking you to rebuild the rest of the site around it.

Every plugin adds work to a page request, so treat this as a decision with a cost. Record a speed test before you install it and run the same test afterwards, on the same page, so you know exactly what it charged you.

Real user ratings

Score

4.3/5

Reviews

1,346

Active installs

1,000,000+

Downloads

65.5M

Latest version

3.1.3

Last updated

2026-08-26

These figures come straight from the public WordPress.org plugin directory API for version 3.1.3, not from us. Check them yourself on the WordPress.org listing. Our own editorial score is 4.3/5.

Where WP Super Cache ranks elsewhere

PublisherListPosition
WPBeginnerBest WordPress Caching Plugins#2 of 5
TechRadarThe best WordPress plugins#2 of 20

Positions are read from the published articles themselves, so they reflect that publisher's order rather than ours. Lists get re-ordered over time, so follow the link if you want the current version.

What changed in the latest version

v3.1.3Latest release2026-08-26
  • Fix: a direct page path ending in a backslash no longer breaks the cache config file.
  • Fix: sanitise the CDN URL and CNAME settings so a value containing a quote or an angle bracket can no longer break the asset URLs they are substituted into.
  • Fix: escape string settings written to the cache config file, so a value containing a quote or a backslash no longer corrupts it.
  • Fix: a cookie named "0" could make a logged-in visitor look anonymous to the cache, so their page was served to everyone.
v3.1.22026-08-19
  • Fix: stop the error log filling with path length warnings when a request URL is too long to build a cache directory from.
  • Fix: clear the cache for category, tag and archive pages whose slug contains non-ASCII characters. The delete cache button could not clear those pages either, and now can.
  • Fix: clear the cache correctly when saving a post whose slug contains non-ASCII characters.
  • Removed the Bad Behavior plugin integration. The upstream plugin is no longer maintained and a long-standing inverted guard meant the integration never actually ran.
  • Fix: ignore a post ID of 0 when clearing the cache after a post edit, which could delete the front page cache unexpectedly.
  • Split wp-cache.php into per-responsibility inc/ files (#1061) (#1065)
  • Fix: cache modern security headers, including Permissions-Policy, the Cross-Origin-Opener/Embedder/Resource-Policy family and the remaining CORS headers, so they are sent on cached responses.
  • Fix: honour quality values in the Accept header, so monitoring tools and browsers that list JSON below HTML are served the cached page instead of rebuilding it on every request.
v3.1.12026-05-27
  • Security: harden supercache filename generation so request-derived data cannot escape the cache directory.
  • Fix: avoid a fatal error on PHP 8+ when closing an unopened file handle in supercache-only mode.
  • Fix: cast the blog ID in wp_cache_clear_cache() so non-integer callers no longer trigger a multisite-only function on single-site installs.
  • Fix: no longer append HTML debug comments to REST API, Ajax, JSON, WooCommerce API, and XML-RPC responses.
  • Fix: avoid a PHP warning when a comment has already been deleted before the cache-clear routine runs.

Release notes are the developer's own words, published on WordPress.org. Read the full changelog

Pros and cons

  • Simple, dependable static caching with no licence
  • Free with no licence to renew
  • Actively maintained and used on production sites we test
  • Fewer optimisation extras than modern caching plugins
  • Support is community-led rather than guaranteed

How to use it

  1. 1Record a baseline with our speed test before you change anything.
  2. 2Activate the plugin with its default settings and clear every cache layer.
  3. 3Re-run the test on the same page and template to see the real delta.
  4. 4Turn on one optimisation group at a time, testing after each change.
  5. 5Add exclusions for cart, checkout and logged-in pages.

How it compares

Other performance plugins we recommend, with their rating and pricing model.

PluginOur ratingWordPress.orgPricingBest for
WP Super Cache4.34.3 (1,346)FreeSimple, dependable static caching with no licence
AMP3.93.8 (367)FreeVery fast mobile pages by construction
Autoptimize4.74.7 (1,428)FreeFree asset optimisation that pairs with any cache
Breeze3.63.6 (126)FreeWorks well on Cloudways servers with Varnish
Hummingbird4.74.7 (1,487)FreemiumThe scan explains each fix in plain language
Jetpack3.73.7 (2,407)FreemiumOne plugin replaces several smaller ones