Speed & performance · Info
WP Super Cache Settings Explained: What to Turn On and Why

Short answer
WP Super Cache settings live under Settings > WP Super Cache. For most sites, turn caching on, use the Simple delivery method, enable compression, do not cache pages for known users, and turn on cache rebuild. Then set a sensible expiry time, consider preloading, and add a CDN only if you use one.
Key takeaways
- Settings are under Settings > WP Super Cache, mostly on the Advanced tab.
- Simple delivery is safest; Expert is faster but edits .htaccess.
- Do not cache pages for logged-in users or commenters.
- Expiry time and garbage collection control how long cached pages live.
- Preload mode builds the cache ahead of visitors on stable sites.
Where are the WP Super Cache settings?
After installing the plugin, go to Settings > WP Super Cache; the Easy tab turns caching on, and the Advanced, Preload, CDN, Contents and Debug tabs hold the detailed options.
WP Super Cache is a free page caching plugin from Automattic. It turns dynamic WordPress pages into static HTML files that load much faster.
If you want to know what the plugin does before configuring it, our explainer on what WP Super Cache does covers the basics.
The official WP Super Cache plugin page lists its recommended settings, which this guide follows.
What do the Easy tab settings do?
The Easy tab has a simple Caching On or Off switch and a Test Cache button, which fetches your home page twice to confirm cached copies are being served.
Turn caching on, then click Test Cache. If the timestamps match, caching works.
For many small sites, turning caching on is enough. The Advanced tab adds control for busier or more complex sites.
The Easy tab also has a button to delete the cache, which you can use after design changes.
Which settings are recommended?
The plugin's own documentation recommends Simple caching, compressing pages, not caching pages for known users, cache rebuild and CDN support where you use a CDN.
| Setting | Recommended | Why |
|---|---|---|
| Caching | On | Turns the plugin on |
| Cache Delivery Method | Simple | Safe on all servers |
| Don't cache pages for known users | On | Logged-in users see live pages |
| Compress pages | On | Smaller files, faster delivery |
| Cache rebuild | On | Visitors get a cached page while a new one builds |
| Don't cache pages with GET parameters | Usually on | Avoids caching unique URLs |
| CDN support | Only with a CDN | Serves static files from a CDN |
Save changes with the Update Status button at the bottom of the section.
Test the site logged out after every change.
Simple or Expert delivery method?
Simple uses PHP to serve cached files and works everywhere; Expert uses web server rewrite rules in .htaccess to serve static files without PHP, which is faster but needs Apache-style rewrites.
The WP Super Cache setup guide on Jetpack.com recommends the Simple method if your site uses Cloudflare.
If your server runs Nginx, Simple is the practical choice because .htaccess rules do not apply there.
Expert relies on the Apache mod_rewrite module. Our explainer on what .htaccess is in WordPress shows where those rules live.
Only choose Expert if you are comfortable restoring the .htaccess file when something goes wrong.
What does Don't cache pages for known users do?
It stops cached pages being shown to logged-in users and recent commenters, so they always see the live site, including admin bars and personal details.
Keep this on for nearly every site. It prevents private or out-of-date content from reaching the wrong person.
Membership and store sites depend on it. Logged-in customers need to see their own accounts and carts.
What do compression and cache rebuild do?
Compression stores cached pages in a compressed format so browsers download less, while cache rebuild keeps serving the old cached page while a fresh one is being generated.
If your host already compresses pages, the plugin's compression adds little. Turn it off if you see garbled pages.
Cache rebuild prevents slow pages during busy moments, because visitors are not left waiting for a new page to build.
The web.dev guide to reducing network payloads explains why compression speeds up pages.
How do expiry time and garbage collection work?
Expiry time sets how long cached files stay fresh, and garbage collection is the scheduled clean-up that deletes stale files; both are in the Expiry Time and Garbage Collection section of the Advanced tab.
Shorter expiry keeps pages fresher but rebuilds them more often. Longer expiry is faster but can show older widgets or counts.
Sites with mostly static content can use longer expiry times. News sites usually need shorter ones.
Click Change Expiration to save these settings, which sit apart from the main Update Status button.
Can you exclude pages from the cache?
Yes. The Accepted Filenames and Rejected URIs section lets you list pages that must never be cached, such as carts, checkouts, account pages or pages with live data.
Add one URL fragment per line. Test each excluded page logged out to confirm it is no longer cached.
What does the Preload tab do?
Preload builds cached copies of posts and pages ahead of visitors, on a schedule you set, so even rarely visited pages load fast the first time.
When Preload Mode is on, normal garbage collection of old files is turned off, and the preload refresh replaces them instead.
Preloading uses server resources. On cheap shared hosting, preload a limited number of posts or schedule it for quiet hours.
Editing posts and new comments still clear the affected cached pages, even with preload on.
How do you set up the CDN tab?
The CDN tab rewrites the URLs of static files such as images, CSS and JavaScript to a CDN address, so a content delivery network serves them instead of your server.
Only use it if you have a pull CDN with its own URL. Proxy CDNs such as Cloudflare work at DNS level and do not need this tab.
Our guide on setting up Cloudflare for WordPress covers the DNS-based approach.
After enabling the CDN tab, check that images and styles still load on every page.
How do you clear the WP Super Cache?
Use Delete Cache on the Easy tab or the admin bar link, and the Contents tab to delete cached or expired pages, after changing themes, menus, widgets or plugin settings.
Also clear any CDN or host cache. Our guide on clearing cache in WordPress lists every layer.
Publishing or updating a post clears the related cached pages automatically.
When should you not use WP Super Cache?
Skip it if your host already provides server-level page caching, if you run another caching plugin, or if you are on LiteSpeed hosting, where LiteSpeed Cache is usually better.
Never run two page caching plugins together. Our explainer on W3 Total Cache covers a more complex alternative if you need more control.
Check your host's documentation first. Some managed hosts block caching plugins.
What problems can wrong settings cause?
Common problems are logged-in content shown to visitors, stale pages after edits, broken carts on stores, and blank pages after a bad Expert mode rule.
If the site breaks, switch caching off on the Easy tab and test again.
If you cannot reach the dashboard, rename the plugin folder by SFTP and remove the WP_CACHE line from wp-config.php if needed.
The Debug tab can log cache activity. Turn it on only while investigating, then switch it off.
Frequently asked questions
What are the best WP Super Cache settings?
Turn caching on, use Simple delivery, compress pages, do not cache pages for known users, enable cache rebuild and set a sensible expiry time. Add CDN settings only if you use a CDN.
Should I use Simple or Expert mode in WP Super Cache?
Simple is safest and works on every server. Expert is slightly faster but needs Apache rewrite rules in .htaccess and is not recommended with Cloudflare.
Does WP Super Cache work with WooCommerce?
Yes, if cart, checkout and account pages are not cached and logged-in users are excluded. Test a full order with caching on.
How do I clear WP Super Cache?
Use the Delete Cache button on the Easy tab or the admin bar link. The Contents tab also lets you delete cached or expired pages.
What is preload mode in WP Super Cache?
Preload mode builds cached copies of posts and pages ahead of visitors on a schedule, and turns off normal garbage collection while it runs.
Sources
- WP Super Cache WordPress.org Plugins
- Initial WP Super Cache Setup and Configuration Jetpack Support
- mod_rewrite Apache HTTP Server Documentation
- Reduce network payloads using text compression web.dev
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.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


