Troubleshooting
WP Super Cache Not Working: Causes and How to Fix It

Short answer
WP Super Cache usually seems broken because caching is off, you are testing while logged in, or the WP_CACHE constant is missing. Turn caching on under Settings, test in a private window, check the page source for the cache comment, and remove any second caching plugin.
Key takeaways
- Caching is off until you turn it on in the Easy tab.
- Logged-in users are not served cached pages by default.
- WP_CACHE must be true in wp-config for caching to run.
- The wp-content cache folder must be writable.
- Only run one page caching plugin at a time.
- The Debug tab log shows why pages are skipped.
Why is WP Super Cache not working?
WP Super Cache usually fails because caching is switched off, you are testing while logged in, the WP_CACHE constant or advanced-cache file is missing, or another cache layer is interfering.
The plugin saves a static copy of each page. Later visitors get that copy instead of WordPress building the page again, which saves server time.
When it is not working, pages load no faster, the cache folder stays empty, or the plugin shows warnings at the top of its settings screen.
The good news is that WP Super Cache gives clear clues. Most problems are solved within the first three checks below.
If you want a refresher on how the plugin works, see our explainer on what WP Super Cache does.
What are the most common causes at a glance?
Most WP Super Cache problems come from a handful of causes, and each one has a quick first check you can run.
| Symptom | Likely cause | First check |
|---|---|---|
| No cache comment in page source | Caching off or testing while logged in | Turn caching on, test logged out |
| Warning about WP_CACHE | Constant missing from wp-config | Add the constant or fix permissions |
| Cache folder stays empty | Folder not writable | Check wp-content permissions |
| Pages cached but site still slow | Large images, scripts or slow host | Profile the page |
| Changes not showing | Old cached copy or CDN cache | Delete cache, purge CDN |
| Two cache plugins active | Conflict | Keep only one page cache |
Match your symptom to the table, then read the section for that cause.
Is caching actually switched on?
Open Settings, then WP Super Cache, and on the Easy tab make sure caching is set to on, then save and use the built-in cache tester.
After installing, the plugin does nothing until you turn caching on. It is easy to install it, activate it and assume the job is done.
On the Easy tab, select the option to turn caching on and click the update button. The tab also includes a Test Cache button that requests your home page twice and compares timestamps.
If the test reports matching timestamps, caching works for the front page. If they differ, keep reading.
Our guide to WP Super Cache settings explains each tab in detail.
Are you testing while logged in?
By default WP Super Cache does not serve cached pages to logged-in users, so you must test in a private window or a different browser to see cached results.
This is the single most common reason people think the plugin is broken. Admins see fresh pages on every load because caching for known users is disabled.
That default is sensible. Logged-in users see admin bars, edit links and personal content that should never be cached and shown to someone else.
To test properly:
- Open a private or incognito window.
- Visit a normal page on your site, not an admin page.
- Reload once so the cache file is created.
- View the page source and scroll to the very bottom.
You should see an HTML comment from WP Super Cache saying the page was cached and when. If you only see a comment about a dynamic page, it was not served from cache.
Is the WP_CACHE constant set in wp-config?
WP Super Cache needs the WP_CACHE constant set to true in wp-config and an advanced-cache file in wp-content, and the plugin warns you when either is missing.
When you turn on caching, the plugin tries to add this line to your wp-config file and create the advanced-cache file. If file permissions block it, the plugin shows a warning.
You can add the line yourself. Open wp-config and, above the line that says to stop editing, add:
define( 'WP_CACHE', true );
The WordPress wp-config documentation explains where constants should go in the file. If you cannot find the file, our guide on where to find wp-config helps.
Also check that another caching plugin has not replaced the advanced-cache file with its own. Only one plugin can own that file at a time.
Can WP Super Cache write to its cache folder?
The plugin stores cached pages inside wp-content/cache, so if WordPress cannot write to that folder, no cache files are ever created.
Connect with your host's file manager or FTP and look for a cache folder inside wp-content. After a few logged-out visits, it should contain subfolders for your pages.
If the folder is missing or empty, check permissions. Folders are normally set to 755 and files to 644 on most hosts.
Do not set folders to 777 as a shortcut. It is a security risk and many hosts block it anyway.
If you are unsure how to connect, our guide on how to get FTP access to WordPress walks through it.
Is another caching plugin or host cache interfering?
Running two page caching systems at once often causes conflicts, so keep WP Super Cache as the only page cache plugin and check what your host already provides.
Plugins such as W3 Total Cache, WP Rocket, LiteSpeed Cache and WP Fastest Cache all try to control the same files. Having two active can break caching or produce odd results.
Many managed hosts also run server-level caching. In that case WP Super Cache may add little, and the host may even advise against it.
Check these points:
- Deactivate any other page caching plugin.
- Ask your host whether they run server or edge caching.
- If you use Cloudflare or another CDN, purge it after changes.
Our comparison of page cache vs object cache explains which layers can safely run together.
Which cache delivery method should you use?
The Simple delivery method works on almost every host, while Expert uses rewrite rules for speed but can fail if those rules are missing or your server ignores them.
On the Advanced tab you can choose how cached files are served. Simple uses PHP to serve the file. Expert uses server rewrite rules so PHP is not loaded at all.
Expert mode needs mod_rewrite rules in your htaccess file on Apache servers. On Nginx, those rules do nothing unless added to the server config by hand.
If caching worked and then stopped after switching to Expert, switch back to Simple. For most sites the speed difference is small.
The plugin's WordPress.org page describes the delivery modes and their trade-offs.
Why are pages cached but changes not showing?
If your edits do not appear, an old cached copy is still being served, so delete the cache from the plugin and purge any CDN or browser cache.
WP Super Cache normally clears related pages when you update a post. Some changes, such as widget edits, menu changes or theme options, do not always trigger that.
Use the Delete Cache button on the Easy tab, or the link in the admin bar. Then purge your CDN if you use one.
Browsers keep their own copies too. MDN's guide to HTTP caching explains how browser and proxy caches decide when to reuse a page.
Check the cache timeout setting on the Advanced tab. A very long expiry means stale pages stay longer if automatic clearing misses them.
Our guide on how to clear cache in WordPress covers every cache layer in order.
Why are some pages never cached?
Pages are skipped when they match rejected URLs, contain query strings, set certain cookies, or come from POST requests, which the plugin treats as dynamic.
Look at the Advanced tab for the list of rejected URL strings and user agents. Make sure nothing there matches pages you expect to be cached.
Pages with query strings, such as tracking parameters, are often not cached by default. Ecommerce carts, checkouts and account pages should also stay uncached.
Some plugins set cookies on every visitor. If a cookie tells WP Super Cache the visitor is special, it may serve a dynamic page instead.
How do you use the debug log to find the cause?
Turn on debugging on the Debug tab, load a few logged-out pages, then read the log to see exactly why each request was cached or skipped.
The log records each request and the reason for the decision. Lines often say a page was not cached because of a cookie, query string or rejected URL.
Jetpack, which now maintains the plugin, has a guide to enabling WP Super Cache debug mode. Its advanced troubleshooting checklist covers rarer problems step by step.
Turn debugging off when you are done. The log can grow large and may expose request details if left public.
What if caching works but the site is still slow?
If cached pages load but the site still feels slow, the bottleneck is probably images, scripts, fonts or the server itself rather than page generation.
Page caching cuts the time to build the HTML. It does not shrink a five megabyte hero image or stop slow third-party scripts.
Measure a cached page with a speed testing tool and look at what takes the longest. Large images and render-blocking scripts are common culprits.
If time to first byte is still high even on cached pages, the hosting may be overloaded. Your host's support team is a good next step.
Consider switching plugins only after confirming the basics, because WP Super Cache works well on most hosts once it is on, writable and free of conflicts.
If your host runs LiteSpeed, its own LiteSpeed Cache plugin usually performs better. Managed WordPress hosts often have built-in caching that makes extra plugins unnecessary.
For everyone else, WP Super Cache remains a simple, free, low-maintenance choice. Our review of whether WP Super Cache is worth it compares it with the alternatives.
Before switching, deactivate WP Super Cache from its own settings first, then deactivate the plugin. That lets it clean up its wp-config line and advanced-cache file properly.
Frequently asked questions
How do I know if WP Super Cache is working?
Open a page in a private window, reload once, then view the page source and scroll to the bottom. A comment saying the page was cached by WP Super Cache, with a timestamp, means it is working. A comment about a dynamic page means it was not cached.
Why do I not see cached pages when logged in?
WP Super Cache does not serve cached pages to logged-in users by default, because those pages contain the admin bar and personal content. Always test caching while logged out, in a private window or a separate browser.
Can I use WP Super Cache with Cloudflare?
Yes. The two work at different layers. Remember to purge Cloudflare after major changes, and avoid caching full HTML at the edge unless you understand how it interacts with logged-in users and dynamic pages.
Should I use Simple or Expert delivery mode?
Simple mode works on almost every host and is the safer choice. Expert mode can be a little faster on Apache with working rewrite rules, but it fails silently on servers that ignore htaccess, such as Nginx without custom configuration.
Why does WP Super Cache say it cannot write to wp-config?
The file permissions on your server stop the plugin from editing wp-config. Add the WP_CACHE line yourself through FTP or your host's file manager, placing it above the line that says to stop editing, then reload the plugin settings.
Sources
- WP Super Cache WordPress.org
- WP Super Cache advanced troubleshooting checklist Jetpack
- Enable WP Cache debugging Jetpack
- wp-config.php WordPress 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.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


