If Joomla still serves the same HTML after System → Maintenance → Clear Cache, you did not fail to click the button. The File folders are not writable, the Cache Handler is Redis, Memcached, or APCu (so emptying cache/ does nothing), or the System – Page Cache plugin (and anything in front of it) is still holding a copy. Clear Cache and Clear Expired Cache are different jobs. This article is the broom. If the broom works but guests still see yesterday for 15 minutes, that is Cache Time and extra layers: Joomla cache showing old content.
On Joomla 4, 5, and 6 the UI is System → Maintenance → Clear Cache and Clear Expired Cache. Both are com_cache. Settings are System → Global Configuration → System → Cache Settings: System Cache (OFF / Conservative / Progressive), Cache Handler, Cache Time, optional Path to Cache Folder. Official overview: Cache. Programmer notes: caching views and modules. File storage default: cache/ and administrator/cache/ (the programmer manual also notes administrator/cache as a default location in that document; Global Configuration Path to Cache Folder overrides when set).
CLI (same component, no browser): php cli/joomla.php cache:clean and php cli/joomla.php cache:clean expired. Official examples: Using the CLI and Purge Expired Cache.
Take a backup before you chmod a live cache/ tree or switch handlers. Try handler changes on staging.

Delete All on File cache cannot empty Redis. A still-enabled Page Cache plugin will refill guest HTML on the next hit.
What you will learn
- Clear Cache vs Clear Expired Cache vs turning the plugin off
- Why
cache/permissions block both write and delete - What happens when Cache Handler is Redis or Memcached
- Why Page Cache “comes back” after a successful clear
- How to confirm which handler Joomla is actually using
- When FTP-deleting files is safe (File handler only)
Clear vs expired vs plugin vs CDN
| Action | Removes | When it looks like “not clearing” |
|---|---|---|
| Clear Cache → Delete All | All groups in this handler | Handler is Redis but you emptied cache/ in FTP |
| Clear Cache → one group | That group only | You cleared com_content while Page Cache still has the URL |
| Clear Expired Cache | Only items past Cache Time | You expected instant publish. Unexpired items should remain |
| Disable System – Page Cache | Stops new full-page snapshots | You cleared views but the plugin still serves the old page |
| CDN purge | Edge copies | Joomla already cleared, Cloudflare did not |
Expired items are not deleted the instant they expire. They sit until purge, full clear, or overwrite. That is why a huge cache/ folder can coexist with “I already clicked clear expired.”
Step 1: Confirm the Cache Handler in Global Configuration
System → Global Configuration → System → Cache Settings → Cache Handler.
| Handler | Where the copy lives | Clear Cache in admin | Deleting cache/*.php in FTP |
|---|---|---|---|
| File | cache/ and administrator/cache/ (or custom path) |
Yes, if PHP can write those dirs | Same store. Last resort if admin clear fails |
| APCu | PHP shared memory on this node | Yes, if APCu is working | No effect |
| Memcached | Memcached server | Yes, if Joomla can talk to it | No effect |
| Redis | Redis server | Yes, if Joomla can talk to it | No effect |
If the dropdown says Redis and you “cleared” by deleting files, you did not clear Joomla’s cache. You cleared an unused directory. Use the admin button or cache:clean, and confirm Redis is up (PING → PONG on the server if you have CLI). A down Redis can also mean Joomla cannot store or delete.
Memcached in Joomla has historically been labelled experimental in some Global Configuration UIs. If you did not set it up on purpose, do not switch to it on production to “fix” clear. Stay on File unless the host provided Redis/Memcached and you tested on staging.
On a cluster, File and APCu are per node. Clearing node A leaves node B’s copy. Shared Redis or Memcached is the design for that. Official programmer cache docs call this out for File/APCu vs shared handlers.
Step 2: Fix permissions on cache/ (File handler)
PHP must create, overwrite, and delete files in the cache path. If the folder is owned by another user, mode 555, or immutable, Clear Cache appears to run and the next request rebuilds or fails to delete. Symptoms:
- Clear Cache lists groups but sizes never drop
- Site errors about unable to write cache
- FTP shows old files still there after Delete All
Typical approach (host-specific: follow their PHP user, not a random 777 blog post):
- Backup.
- On staging, compare owner of
cache/with owner of a file PHP just wrote (a new article image upload, orconfiguration.phpafter a Global Configuration save). - Restore writable directories (often
755) and files PHP should replace. Do not chmod the whole Joomla root to world-writable. - Click Delete All again. Confirm files disappear.
If Path to Cache Folder is set to a custom path in Global Configuration, you are fixing that path, not necessarily ./cache/.
administrator/cache/ is a second tree. Admin-side cache groups live there. Clear Cache should cover both when the handler is File. If only one tree is writable, you get “half cleared” behaviour.
Step 3: Use Maintenance Clear Cache, not a random extension screen
People click System and miss Maintenance. They empty a template “compile” folder, or a page-builder cache, or Cloudflare, and say “Joomla clear does nothing.”
The Joomla broom is:
- System → Maintenance → Clear Cache → Delete All (or selected groups).
- If you only wanted garbage collection: Clear Expired Cache.
- Confirm Cache Handler again. The Maintenance screen may show a Storage column (File vs the memory handler).
There is no separate “Maintenance cache” vs “System cache” engine. Maintenance is the com_cache UI. Global Configuration is the policy.
CLI from the site root (SSH), after backup, on staging first if you are unsure:
php cli/joomla.php cache:cleanphp cli/joomla.php cache:clean expired
If CLI clears Redis but the web UI does not, the web PHP user cannot reach Redis (socket permissions, wrong host, different configuration.php). Align the handler settings; do not run two configuration.php copies.
Step 4: Page Cache plugin still on (and still winning)
You can Delete All view cache and still lose as a guest because System – Page Cache stores a full HTML page and will recreate it on the next anonymous hit. That is correct plugin behaviour, not a broken delete.

If the old page returns after a clear:
- Confirm you tested logged out. Logged-in users skip Page Cache, so an editor thinks “it cleared” while guests still get the snapshot until you actually deleted the page group and they miss CDN.
- Clear Cache again, then immediately disable System – Page Cache on staging and retest guests. If guests are fresh only when the plugin is off, the plugin was the remaining store (or it refilled from a still-stale inner cache: clear inner first, then plugin).
- Check Use Browser Caching on the plugin. That pushes staleness into the browser. Joomla Clear Cache will not evict Chrome’s disk cache. Hard refresh is required.
If you need Page Cache for speed, leave it on, exclude volatile menu items, and treat Clear Cache as a deploy step. Do not leave it on, refuse to clear it, and call Joomla broken.
Cloudflare in front: Joomla can clear Redis and still lose to the edge. Purge Cloudflare. That is a layer issue, covered in the old content post. Here the tell is: origin curl headers already show new HTML while the browser on the orange-cloud hostname shows old.
Step 5: Prove the next write lands in the same store
After a successful clear:
- File: new files appear under
cache/on the next guest hit (if System Cache or Page Cache is on). Empty forever means nothing is storing (cache OFF, plugin off, or unwritable). - Redis:
cache/may stay empty. That is success. Use Redis CLI or the host panel to see keys if you must. - Progressive vs Conservative does not change whether clear works. It changes what gets stored next. Wrong module after a good clear is Progressive behaviour, not a stuck disk.
If you recently moved hosts, $cache_handler in configuration.php may still say redis while this server has no Redis. Joomla then cannot clear what it cannot connect to. Set Handler back to File on staging, save, clear, retest. Do not edit core to force a handler.

Handler first. Then cache/ permissions. Then Clear vs Expired. Then the Page Cache plugin. Then other nodes and the CDN.
Key takeaways
- Clear Cache deletes the current handler’s groups. FTP on
cache/only matches File. - Clear Expired Cache is supposed to leave unexpired items. That is not a bug.
- Unwritable
cache/oradministrator/cache/makes delete and write fail. Fix ownership, not777on the whole site. - Redis/Memcached/APCu ignore file deletes. Use admin or
cache:clean, and a reachable server. - Clusters: File clear is per node unless you use a shared handler.
- System – Page Cache will refill guest HTML. Disable it on staging to prove the layer. Use Browser Caching is a browser problem.
- Backup first. Switch handlers on staging. Keep old content layers in mind when origin is already new.
Related Joomla troubleshooting
Frequently asked questions
Why is Joomla cache not clearing when I click Delete All?
Either PHP cannot delete in the File path, or Cache Handler is not File (Redis, Memcached, APCu), or you cleared Joomla while Page Cache or Cloudflare still had a copy. Check the handler dropdown before you chmod anything.
What is the difference between Clear Cache and Clear Expired Cache?
Clear Cache removes groups now (fresh and expired). Clear Expired Cache removes only items past Cache Time. Use Clear Cache when you need the new article immediately.
Can I delete the cache folder in FTP?
If Handler is File, deleting the contents of cache/ and administrator/cache/ is the same class of action as Delete All (do not delete the folders if Joomla expects them). If Handler is Redis, FTP does nothing useful. Backup first. Prefer the Maintenance screen.
Does Redis need a separate clear in Joomla?
Joomla Clear Cache should flush through the Redis handler when PHP can connect. If the web UI cannot reach Redis, files will not help. Fix host, port, socket, and the Cache Handler fields. Test on staging.
Why does old HTML return right after a successful clear?
The next guest request rebuilds Page Cache from still-stale inner data, or the plugin served a copy you did not drop, or the CDN never purged. Disable Page Cache on staging to isolate. Then see the old-content article for guest vs login.
Where are Joomla 4, 5, and 6 cache settings?
System → Global Configuration → System → Cache Settings. The broom is System → Maintenance → Clear Cache. The plugin is System → Manage → Plugins → System – Page Cache.
Is 777 on cache/ the fix?
No. Match the PHP user the host documents. World-writable cache is a security hole. Staging first if you are changing modes at all.
Conclusion
When Clear Cache “does nothing,” believe the handler and the filesystem before you believe Joomla is haunted. File needs a writable cache/. Redis needs a live Redis. Page Cache and Cloudflare are allowed to look like a failed clear if you only emptied the wrong store. Once the broom works, put Conservative cache and Page Cache back on using speed up Joomla, and purge layers on publish.
If permissions and Redis are a mess on production, Joomla support and maintenance is cheaper than chmod roulette.






















