Product facts · Explainer
What Does WP Super Cache Do? Features Explained Simply
Short answer
WP Super Cache is a free WordPress plugin by Automattic that saves each page as a static HTML file, so your web server can serve it without running PHP or the database. It offers three modes, Expert, Simple, and WP-Cache, plus preload, garbage collection, CDN support, and compression. Most visitors get the static file, which cuts server load and keeps pages fast.
Key takeaways
- WP Super Cache saves WordPress pages as static HTML files so the server skips PHP and database work for most visitors.
- Version 3.1.5, released 2 November 2026, runs on more than 1 million WordPress sites.
- Simple mode serves cached files through PHP and is the recommended setup; Expert mode uses Apache mod_rewrite and skips PHP entirely.
- Preload builds cached pages in advance, while garbage collection deletes stale files on a schedule.
- Use the built-in Cache Tester or check the page source timestamp to confirm caching works.
What does WP Super Cache do?
WP Super Cache turns your WordPress pages into static HTML files so your web server can serve them without running PHP or the database.
The plugin is made by Automattic, the company behind WordPress.com, and it is listed on WordPress.org. Version 3.1.5 was released on 2 November 2026, and WordPress.org lists more than 1 million active installs (checked November 2026).
It needs WordPress 6.8 or newer and PHP 7.4 or newer, and it is tested up to WordPress 7.1.5. The plugin has been listed on WordPress.org since 5 November 2007, and it holds a 4.3 out of 5 rating from 1,346 reviews (checked November 2026).
WordPress.org's plugin page says 99% of visitors will be served static HTML files, because most visitors are logged out and have not left a comment. One cached file can be served thousands of times, so repeat visits cost your server almost nothing.
How does WP Super Cache work?
When a visitor opens a page for the first time, WordPress builds it with PHP and the database, then WP Super Cache saves the finished HTML as a file.
Later visitors get that saved file straight from the web server, which skips the PHP and database work. The plugin stores cached files under wp-content/cache/supercache/, in folders named after your domain, as WordPress.org's plugin page explains.
Cached files go only to anonymous visitors: people who are not logged in, have not left a comment, and have not viewed a password-protected post. Logged-in visitors and commenters get their own cached copy with their details shown.
Caching is one of the simplest ways to speed up WordPress, because it removes repeated work from every page view.
What are the three caching modes?
WP Super Cache offers three delivery modes, ranked by speed: Expert, Simple, and WP-Cache.
Expert mode uses Apache mod_rewrite to serve supercached files and skips PHP completely, so it is the fastest option. It edits your .htaccess file, and WordPress.org's plugin page warns that a wrong edit can take your site down, so back the file up first.
Simple mode uses PHP to serve the supercached file and is the method WordPress.org's plugin page recommends for most sites. It needs a custom permalink structure, needs no .htaccess change, and still lets parts of a page stay dynamic.
WP-Cache mode handles known users, URLs with parameters, and feeds, and it is the most flexible of the three modes. It is always on, and you can turn off supercaching alone by setting the DISABLE_SUPERCACHE constant to 1 in wp-config.php.
What features does WP Super Cache include?
WP Super Cache includes caching modes, preload, garbage collection, CDN support, compression, cache rebuild, and a REST API.
| Feature | What it does | Where to find it |
|---|---|---|
| Preload | Builds cached files for posts, categories, and tags before visitors arrive | Preload tab |
| Garbage collection | Deletes stale cache files on a schedule | Advanced tab |
| CDN support | Rewrites asset URLs to point at your CDN hostname | CDN tab |
| Compression | Stores pages as smaller gzip files | Advanced tab |
| Cache rebuild | Serves the old page while a new one is built | Advanced tab |
| REST API | Lets admin users read and change settings through endpoints | Rest directory in the code |
Preload visits each page like a visitor and saves a cached copy, so the first real visitor gets a fast page. WordPress.org's plugin page suggests a preload interval of 2,880 minutes (2 days) if you do not need sidebar widgets to refresh often (checked November 2026).
Garbage collection clears out-of-date cache files, and the plugin page suggests 1,800 seconds as a starting point for the cache timeout. For a site with regular updates or comments, it suggests a 1,800-second timeout with garbage collection every 600 seconds.
The CDN feature rewrites URLs for files in wp-content and wp-includes, except PHP files, so they point at a different hostname. Configure it on the CDN tab, then clear the cache, as WordPress.org's plugin page instructs.
The plugin is open source, and active development happens in the Automattic/wp-super-cache repository on GitHub.
Why does caching matter for your site?
Caching matters because it cuts the work your server repeats on every page view, which keeps pages fast when traffic rises.
A cached page needs no database queries and no PHP processing, so your server can handle more visitors at once. WordPress.org's plugin page says a site hit by a surge of traffic is more likely to cope when pages are served as static files.
WP Super Cache will not fix a slow theme or a weak host, but it removes the repeated page-building work that hits every visitor. For the search side of speed, see our guide on whether page speed affects SEO.
Is WP Super Cache free?
Yes, WP Super Cache is free, with no paid version and no premium upgrade sold by Automattic.
The plugin is listed free on WordPress.org, and its code is released under the GPLv2 licence, as the GitHub repository states.
Every feature on the settings pages is available after install, because there is no paid tier. Our guide on whether WP Super Cache is free covers what the free version includes.
For a closer look at the cost question, see how much WP Super Cache costs.
If you want to judge it on value rather than price, see whether WP Super Cache is worth it.
How do you check that WP Super Cache is working?
Use the built-in Cache Tester on the plugin's Easy settings page, which requests your front page twice and compares the timestamps.
- Go to “Settings → WP Super Cache” in your WordPress admin.
- Find the “Cache Tester” form on the Easy tab and click “Test Cache”.
- The plugin loads your front page twice and checks that the timestamps match.
You can also view the source of any page and look for the line “Cached page generated by WP-Super-Cache on” followed by a date and time, as WordPress.org's plugin page explains. On reload, a cached page shows the same timestamp.
Response headers give a third check: PHP-served supercache files carry the header “WP-Super-Cache: Served supercache file from PHP”, while WP-Cache files carry “WP-Super-Cache: Served WPCache cache file”.
What are common myths about WP Super Cache?
The most common myth is that installing a cache plugin alone makes a site fast, when caching only removes repeated page-building work.
- Myth: caching works the same for logged-in users. Logged-in visitors, commenters, and people viewing password-protected posts are treated as known users and do not get the plain static file. Developers can register extra cookies with the wpsc_add_cookie action, as Jetpack's developer docs explain.
- Myth: cached pages never go stale. Cached files are deleted when you edit a post or a comment is made, and garbage collection removes old files on a schedule.
- Myth: WP Super Cache works with any permalink setup. Simple and Expert modes need a custom permalink structure, and URLs with tracking parameters such as utm_source are not supercached.
What mistakes should you avoid?
The biggest mistake is turning on Expert mode without a backup of your .htaccess file, because a bad rewrite rule can take your site down.
- Do not put important files in wp-content/cache/, because garbage collection can delete anything the plugin can write to.
- Do not enable compression twice: if your server already compresses pages, turn off the plugin's compression or browsers may show garbage.
- Do not expect search engine bots to be cached by default; the plugin skips them unless you clear the “Rejected User Agents” box.
- Do not forget to clear the cache after changing CDN settings, as the plugin page instructs.
Frequently asked questions
Does WP Super Cache work on Nginx?
Yes, but Expert mode needs Apache mod_rewrite, so on Nginx you should use Simple mode, which serves supercached files through PHP. Simple mode needs no .htaccess change and is the setup WordPress.org recommends for servers without mod_rewrite.
Can WP Super Cache cache pages for logged-in users?
Yes, through WP-Cache caching, which stores custom cached files for known users such as logged-in visitors and commenters. Supercached static files are only for anonymous visitors, so logged-in users never see another person's page.
How often should cache files be cleared?
WP Super Cache clears the right files on its own when you publish, edit, or receive a comment, so manual clearing is rarely needed. Garbage collection also removes stale files on a schedule, with 1,800 seconds as a suggested starting timeout.
What happens if I uninstall WP Super Cache?
Deactivating the plugin cleans up most files it created, but it does not remove the mod_rewrite rules from .htaccess. You must delete those rules, remove the WP_CACHE line from wp-config.php, and delete wp-content/advanced-cache.php, wp-content/wp-cache-config.php, and wp-content/cache/.
Does WP Super Cache slow down the WordPress admin?
No. The plugin only caches public pages, and logged-in users are treated as known users, so admin screens are not served from the static cache. Your dashboard keeps working as normal while visitors get cached pages.
Is WP Super Cache still maintained?
Yes. Version 3.1.5 was released on 2 November 2026, and the previous release, 3.1.4, came out on 30 September 2026. Active development happens on GitHub, and the plugin is tested with recent WordPress versions.
Sources
- WP Super Cache WordPress.org
- WP Super Cache Jetpack
- Automattic/wp-super-cache GitHub
- Add or Removing Cookies Jetpack Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
