Free WordPress Caching Plugins in 2026: Which Ones Actually Cache

Updated October 2026

SiteGround Optimizer has 1,000,000+ active installs according to a direct wordpress.org Plugin API query on 2 October 2026, and its own readme states that dynamic caching is “available exclusively for SiteGround servers.” Autoptimize has 800,000+ installs, and its readme tells you to install a page caching plugin alongside it. Both figures were re-queried on 2 October 2026 and both held. The comparison people expect here is a feature grid of free tiers. The more useful comparison is three questions: does the free tier write a page cache at all, does it do so on the server you are actually running, and can you prove it worked from outside the site. This article puts twelve free tiers through those three questions, with every install figure, price and quotation re-queried on 2 October 2026.

Quick Summary: Which Free Cache Plugin Fits Your Situation

”Free Caching Plugin” Hides Three Different Products

The phrase covers three categories that behave nothing alike once installed. The first writes HTML files and serves them on any standard PHP host. The second writes a page cache only when the site sits on one company’s servers, and does little otherwise. The third never page-caches at all and optimizes CSS, JavaScript and images instead, which is useful and is not the same job.

Add up the second and third categories from the Plugin API figures, re-pulled on 2 October 2026, and you get at least 8.8 million active installs where the free page cache either depends on the host or does not exist. That is not a criticism of those plugins. Each is honest about it in its own documentation. It is a criticism of every roundup listing them side by side in one “free caching plugins” table.

The Three Questions, Before Any Product Is Named

These are the criteria the rest of the article scores against, chosen before any plugin was looked at.

• 🧱 Does the free tier write a page cache? Not minification, not lazy loading, not a database cleaner. A stored HTML response a later visitor receives without WordPress rebuilding it.
• 🖥️ Does it work on your server? Apache, nginx and LiteSpeed behave differently, and two plugins here cache only inside one hosting company’s environment.
• 🧾 Can you prove it from outside? If the only evidence of a hit is an HTML comment buried in the page source, then curl -I, a monitoring tool, WordPress Site Health and an AI agent reading headers all fail to see it.

The third question is the one nobody scores and the one that separates this field most sharply. It gets its own section below.

Group One: Free Tiers That Page-Cache on Any Standard Host

Nine plugins write a page cache in their free version and do not care who your host is.

All figures from a direct wordpress.org Plugin API query on 2 October 2026. Ratings are reported by the API on a 100-point scale and converted to stars here. Breeze was renamed Breeze Cache in the directory between the two queries.

Two details that matter more than the feature counts

Both are documented by the vendors themselves, and neither is visible from the plugin list.

WP Super Cache ships two delivery modes and the faster one is not the default. Per its own readme: “The fastest method is by using Apache mod_rewrite … to serve supercached static html files. This completely bypasses PHP and is extremely quick.” The readme then recommends the other: “Supercached static files can be served by PHP and this is the recommended way of using the plugin … It’s easier to configure as the .htaccess file doesn’t need to be changed.” A site on the recommended setting still boots PHP on every hit. That is the vendor’s considered tradeoff, and it is invisible from the plugin list.

Serving a cached file without PHP is an Apache trick unless someone edits the server config. WP Fastest Cache states in its own FAQ that on nginx “you need to enable the Gzip compression and Browser Caching features manually.” W3 Total Cache’s FAQ says it is “aware of no incompatibilities with apache 1.3+, nginx 0.7+, IIS 5+ or litespeed 4.0.2+,” which is a compatibility statement rather than a claim that the static path configures itself. Our plugin is in the same position and our readme says so: GZIP auto-configures on Apache and LiteSpeed, and nginx and IIS get “a ready-to-paste config snippet.” Anyone claiming their free plugin bypasses PHP on nginx without a server-block edit is describing a manual step they chose not to mention.

Group Two: Free Tiers That Cache Only Where You Host

This is the group that breaks the roundups, and it is 8,000,000+ installs.

LiteSpeed Cache, still at 7,000,000+ active installs on 2 October 2026, splits its own feature list in two. The readme is explicit: “General Features may be used by anyone with any web server (LiteSpeed, Apache, NGINX, etc.)” while “LiteSpeed Exclusive Features require one of the following: OpenLiteSpeed, commercial LiteSpeed products, LiteSpeed-powered hosting, or QUIC.cloud CDN.” Page caching sits in the Exclusive column. On Apache or nginx the plugin is a very capable asset optimizer with the cache switched off by design, and connecting the free tier of QUIC.cloud restores it. We took this apart in detail in what LiteSpeed Cache actually gives you on Nginx or Apache, including how to read your own server header first.

SiteGround Optimizer, at 1,000,000+ installs, says it even more directly. From its readme, on Dynamic Caching: “This default feature is available exclusively for SiteGround servers.” On Memcached: “This powerful feature is exclusively available in the SiteGround environment.” Its changelog records “Added alert and check if you’re running SiteGround Optimizer on a host different than SiteGround,” which tells you how often this happens.

Neither plugin is doing anything wrong. Both are the correct answer on their own platform, and on LiteSpeed hosting a server-level cache beats a PHP-level one on architecture alone. The problem is a listicle ranking them against host-agnostic plugins without mentioning the condition.

Group Three: The Free Tier That Does Not Page-Cache

Autoptimize has 800,000+ active installs and is frequently installed as a caching plugin. It is not one, and its readme is unusually clear: “If you think performance indeed is important, you should at least consider one of the many free page caching plugins (e.g. Speed Booster pack or KeyCDN’s Cache Enabler) to complement Autoptimize.” Page caching is a feature of the paid Autoptimize Pro, sold off-directory, whose price we could not verify on a public page, so none is quoted.

One more situation is worth a line. Comet Cache has 20,000+ installs and its last release, version 170220, is still dated 2 July 2025 according to the Plugin API on 2 October 2026. A cache plugin sits between every visitor and your site. Fifteen months without a release is a reason to look elsewhere.

The Receipt Test: Can You Prove the Cache Is Working?

Here is the framework, and as far as we can tell nobody else publishes it. Install a free cache plugin, then try to prove from outside that a page was served from cache. What each plugin leaves behind is not the same kind of evidence, and the difference is decisive.

Some plugins answer in a response header. Some answer in an HTML comment near the foot of the page source. The two look equivalent in a feature grid and are not. A header survives curl -I, appears in monitoring tools, is what WordPress core’s Site Health check reads, and is what an AI agent sees. A comment requires downloading the full body, and it does not always survive the trip.

WP-Optimize documents the failure case in its own FAQ, and the sentence is worth quoting in full: “Cloudflare will strip out the special HTML comment at the bottom of the source of a page that is helpful to confirm that page caching is working, so, don’t be confused by that.” A working cache, correctly configured, with its only evidence removed in transit.

W3 Total Cache is the one row this audit could not settle. Its page-cache code exposes a w3tc_header filter, and the only HTML comments in PgCache_ContentGrabber.php are mfunc and mclude markers for dynamic fragments, which are not evidence of a hit. Rather than guess, the row stays open. Check your own response.

Three consequences follow from that table.

• 🔧 Practical. Pair a comment-only plugin with Cloudflare or any proxy and your quickest verification method is gone while the plugin still works fine. Our guide to checking whether WordPress caching is actually working covers what to do instead, including which of the fourteen headers WordPress core accepts as proof are not proof of a hit.
• 🤖 Machine-readable. AI assistants, uptime monitors and rank trackers read headers. A cache that only writes a comment is invisible to all of them, and more of your site’s assessment is done by software every year.
• 🐛 Debugging. When a purge appears to do nothing, a header names in one request which layer served the stale copy. Without one you are guessing, which is what to do when purging the cache changes nothing.

What Moved in 23 Days, and What It Tells You About Picking on a Snapshot

Every figure here was first read on 9 September 2026 and re-queried on 2 October. Running the same query twice is the one thing a single-snapshot roundup cannot do.

Eight of eleven shipped a release in 23 days. Two shipped nothing, and one has shipped nothing since July 2025, which is the row that should change a decision.

The limitation of this table, stated plainly: a release is not an improvement, and cadence is not quality. Install buckets moved for exactly one plugin, ours, and that is a property of the bucket widths rather than of the field: a plugin going from 1,000,000 to 1,400,000 would show no movement here at all.

How This Was Verified, and What It Cannot Tell You

Every figure above came from one of three places, first on 9 September 2026 and re-queried on 2 October: a direct wordpress.org Plugin API query, the plugin’s own readme.txt, or its own source code, both from the plugin repository. Where a claim is about behaviour rather than a number, the evidence is the vendor describing their own product. A competitor stating their own limitation is stronger evidence than any criticism we could write, and you can check it in a minute.

Four limitations, because a framework that does not name its own gaps is not one.

• 🔢 Install counts are buckets, not measurements. The Plugin API reports “1,000,000+” for four plugins here. One could have twice another’s installs invisibly. Never treat two plugins in the same bucket as equally popular, and never compute a percentage from them.
• 🧪 This is a documentation and source audit, not a benchmark. Nothing here measures speed on a live site. Your host, theme and plugin load matter far more than which of two competent page caches you picked, and a benchmark on our hardware would tell you about our hardware.
• 🔍 The receipt table records default behaviour we could find evidence for. Debug modes, filters and settings change what a plugin emits; w3tc_header is one such filter. Check your own response rather than trusting this table.
• 📅 Free tiers move. Features cross the free-to-paid line in both directions. Every claim above carries the date it was checked for that reason.

None of these gaps affects the three-question framework, which is about what a plugin does rather than how fast. They do make this a starting shortlist rather than a verdict.

What the Upgrade Costs If You Outgrow the Free Tier

Four of these plugins have no paid tier, so the free tier is the whole product and will not be narrowed later to sell you something. That belongs in the decision.

One row could not be re-checked, and it is named rather than quietly restated. WP Fastest Cache’s premium page renders its prices in the browser rather than in the HTML the server sends, so those four figures are the 9 September reading carried forward. They are not a 2 October measurement. Every other price was re-read from the vendor’s own page today: W3 Total Cache Pro is unchanged at $99, $350 and $500 a year for 1, 5 and 10 sites, and WP-Optimize Premium at $49, $99 and $194.

Two patterns are worth naming. WP Fastest Cache is the only one selling a one-time licence in a conventionally annual field, and its own page describes the package as carrying a “1 year license transfer right,” so read that before treating it as permanent. Three billing shapes are in play on the paid side, which is why per-site cost is worth working out on your own site count. We ran that arithmetic against a metered competitor in the NitroPack alternatives comparison.

Choosing for Twenty Sites Is a Different Decision

Everything above is a single-site decision. At twenty sites the constraint stops being which plugin is best and becomes how many plugins you are willing to know well.

A mixed fleet can end up with LiteSpeed Cache on the LiteSpeed boxes, SiteGround Optimizer on the SiteGround ones, and something host-agnostic everywhere else. Three dashboards, three purge behaviours, three sets of exclusions, and no single answer to “is the cache on across the fleet.”

One answer across three server types

This is the problem we built xSpeed Cache to solve, and it is ours: xSpeed Cache, xSpeed Scan and xSpeed Hub are WPDeveloper products, and WPDeveloper is a Startise company. The free tier writes a static-file path on Apache, nginx and LiteSpeed, emits X-XSpeed-Cache so one request checks any site in a fleet, and imports exclusions and settings from LiteSpeed Cache, WP Rocket and W3 Total Cache rather than making you rebuild them. Object caching, CDN URL rewriting and database cleanup sit in the free tier too, as does the Cloudflare integration: zone connection, API token, auto-purge and development mode, read from our Free vs Pro breakdown on 2 October 2026, with only Cloudflare APO, cache level and browser-cache TTL behind Pro. On a LiteSpeed server the plugin tells LSCache to stand down and takes ownership, so the hit is tagged consistently across every host.

Free scan of any URL, no account needed: xspeedcache.com/scan/

Where that argument is weak

Four honest counts against us, and they are the reason this article does not rank us first.

• 📉 9,000+ active installs against LiteSpeed Cache’s 7,000,000+, WP Fastest Cache’s 1,000,000+ and W3 Total Cache’s 900,000+, all from the same API query on the same day. We were in the 2,000+ bucket on 9 September 2026, so the gap has closed four and a half times over and is still three orders of magnitude. Years of field exposure across millions of sites is evidence we do not have yet.
• 🧩 On nginx our static path needs a pasted server-block snippet. Our readme says a “ready-to-paste config snippet is provided for nginx and IIS.” That is the same manual step WP Fastest Cache and WP Super Cache’s expert mode require, so we do not get to claim it away.
• 🏢 On LiteSpeed hosting, LSCache is the better architecture and it is free. A cache inside the web server beats one in PHP. Ours tells it to stand down for fleet consistency, and on a single LiteSpeed site leaving LSCache in charge is a defensible choice. The same holds on SiteGround.
• 💸 We sell a Pro tier and four plugins here do not. WP Super Cache, Cache Enabler, Breeze Cache and Surge have no paid version at all. If never being upsold is the point, those four beat us outright.

Common Mistakes People Make Choosing a Free Cache Plugin

• ⚠️ Installing two page caches. WP-Optimize’s FAQ explains why this fails: both need the same advanced-cache.php drop-in, so the second to write it wins and the first silently stops. Migrate rather than stack, using our guide to moving between cache plugins.
• ⚠️ Assuming a green dashboard means a cache hit. The plugin is reporting on its own intent. Read the response, not the settings screen.
• ⚠️ Judging it by a PageSpeed score. Our 958-site study found caching cut median TTFB by 73% and did not move LCP. A page cache fixes server response time. Asset weight is a different job.
• ⚠️ Picking on install count alone. Two of the three most-installed plugins in this field are conditional on hosting, which the install count does not tell you.
• ⚠️ Forgetting the cart. Caching a WooCommerce cart or checkout shows one customer another shopper’s basket. Check the exclusion defaults first on a store, starting with the WooCommerce use case.

Frequently Asked Questions

I installed a free caching plugin and my PageSpeed score did not change. What went wrong?

Probably nothing. A page cache reduces time to first byte. PageSpeed’s mobile score is dominated by the CSS, JavaScript and image weight that arrives afterwards, and our 958-site scan study measured exactly that split. Check your TTFB before and after, and treat the score as a separate project.

I turned on caching but curl -I shows no cache header. Is it broken?

Not necessarily. Four plugins above leave an HTML comment rather than a header, so a HEAD request shows nothing even on a perfect hit. Fetch the full page and search for the footer comment, or switch to a plugin that emits a header.

My cache worked until I put Cloudflare in front of the site, and now I cannot tell. Why?

WP-Optimize’s own FAQ names this: Cloudflare strips the HTML comment that confirms the cache is working. The cache is very likely fine and your evidence was removed in transit. It is the strongest practical argument for a plugin that emits a header.

Is LiteSpeed Cache free on any server?

The plugin is free everywhere and always has been. Its page caching requires OpenLiteSpeed, a commercial LiteSpeed product, LiteSpeed-powered hosting or QUIC.cloud CDN, per its own readme. QUIC.cloud has free levels, so restoring the cache on Apache or nginx without paying is possible.

I moved my site off SiteGround and everything got slower. Did I break something?

Very likely you left SiteGround Optimizer’s dynamic cache behind, which its readme states is “available exclusively for SiteGround servers.” The plugin keeps running and keeps optimizing assets. The page cache is gone. Install a host-agnostic one from group one.

Does Autoptimize cache my pages?

No. Its readme recommends adding a free page caching plugin alongside it and names two. Page caching is a feature of the paid Autoptimize Pro. Autoptimize is a good asset optimizer and is not a cache.

Can I run Autoptimize with a caching plugin at the same time?

Yes, and that is the intended arrangement. Its readme warns against running two minification plugins at once, so if your cache plugin also minifies, switch minification off in one of them.

Which free plugin is fastest?

On LiteSpeed hosting, a server-level cache is the fastest architecture available, which means LiteSpeed Cache. Elsewhere, any plugin serving a static file through a rewrite rule without booting PHP lands in a similar range, and the gap between them is usually smaller than the gap your host makes. Measure your own site.

I have five sites on three different hosts. Should I standardise on one plugin?

Standardising reduces what you have to remember and loses a little peak performance on hosts with a server-level cache. If the LiteSpeed and SiteGround sites are a minority, standardise. If they are most of the fleet, keep the native cache there and standardise on the rest.

Do I need to remove the old plugin before installing a new one?

Yes, and deactivating is not always enough. A cache plugin leaves an advanced-cache.php drop-in, and WordPress core treats that file merely existing as evidence of a working page cache. Delete the plugin properly and check the drop-in is gone.

Is a free plugin enough, or do I eventually have to pay?

For a content site on decent hosting, a free page cache plus sensible exclusions is often the end of it. Paid tiers mostly buy asset-level work: critical CSS, delayed JavaScript, image conversion, support. Reach for one when your measurements say assets are the problem.

Which free plugin should an agency pick?

The one that answers the same way on every host you manage: a host-agnostic page cache with a header you can check across the fleet in one pass. Ours is one option in that shape, with the install-base caveat above. WP Fastest Cache and W3 Total Cache are the two most-installed alternatives with the same property.

Conclusion: Your 2026 Free Caching Shortlist

The three-question framework does most of the work. At least 8.8 million installs sit on free tiers that either page-cache only on one company’s servers or do not page-cache at all, and the directory flags neither condition. Separate those out and the remaining decision is mostly about evidence: whether the plugin can prove it is working in a way a machine can read.

What to do this week:

1. Run curl -I https://yourdomain.com/ and look for a cache header. If there is none, fetch the full page and search the source for a footer comment.
2. Check your server. If the header says LiteSpeed, install LiteSpeed Cache and stop reading. If your host is SiteGround, install SiteGround Optimizer and stop reading.
3. If neither applies and you want a free page cache with nothing held back, install WP Super Cache, Cache Enabler or Surge. All three have no paid tier.
4. If you manage several sites across different hosts and want one answer everywhere, try the free tier of xSpeed Cache, which we build. It imports your existing exclusions and emits X-XSpeed-Cache, so one request verifies each site. Paid plans start at $29/yr with a 14-day money-back guarantee, and the 80-capability comparison shows what each tier includes.
5. Whichever you choose, verify from outside rather than from the dashboard. The free xSpeed Scan reads the response for you and needs no account.

If you run one site on LiteSpeed or SiteGround hosting, your host already ships a free cache that is hard to beat, and you should use it. If you run a mixed fleet, or a site on Apache or nginx where no server-level cache exists, that gap is what we built xSpeed Cache for: one free page cache that behaves the same on every host and says so in a header you can read. The tie-breaker does not change. Pick the one that can prove it is working.