
The best free WordPress caching plugin depends on your web server. If your host runs LiteSpeed, use LiteSpeed Cache. On Apache or Nginx, WP Super Cache is the simplest safe choice, WP Fastest Cache has a short settings page, and W3 Total Cache gives you the most control. Install only one of them.
Page caching is the cheapest speed upgrade a WordPress site can get. Instead of running PHP and database queries for every visit, the site serves a saved copy of the page. The hard part is not the idea, it is choosing a plugin without ending up with two of them fighting each other.
This guide compares four free options that all list support for the current WordPress release on their WordPress.org pages: LiteSpeed Cache, WP Super Cache, W3 Total Cache and WP Fastest Cache. We looked at what each plugin page says it includes for free, what is locked behind a paid plan, and which hosting setups suit each one. If you are picking the best free WordPress caching plugin for a client site or your own, the table below is the fastest way to narrow it down.
We did not run speed benchmarks. Results vary too much by host, theme and plugins to publish one number that means anything, so this is a comparison of features, requirements and risks, not a speed test.
Free WordPress caching plugins at a glance
| Plugin | Best for | Active installs (WordPress.org) | Main catch |
|---|---|---|---|
| LiteSpeed Cache | Hosts running LiteSpeed or OpenLiteSpeed | 7+ million | Server-level page caching only works on LiteSpeed |
| WP Super Cache | Beginners on any host | 1+ million | Few optimisation extras |
| W3 Total Cache | Developers who want Redis, Memcached or CDN control | 900,000+ | Many settings, some features are Pro only |
| WP Fastest Cache | Quick setup on Apache | 1+ million | Image optimisation, Delay JS and more are premium |
The install counts come from each plugin’s WordPress.org page when we checked in October 2026. A big number tells you a plugin is well tested, not that it is right for your server.
LiteSpeed Cache: the pick if your host runs LiteSpeed
LiteSpeed Cache is the most installed of the four, with more than 7 million active installs. Its WordPress.org page says the general features work on any web server, including Apache and Nginx. That covers minifying and combining CSS, JS and HTML, lazy loading images, critical CSS, deferring or delaying JavaScript, object cache support and database cleanup.
The part that makes it special is server-level page caching, private caching for logged-in users and the preload crawler. Those need OpenLiteSpeed, a commercial LiteSpeed server, LiteSpeed-powered hosting or the QUIC.cloud CDN. On a plain Apache or Nginx host you do not get the fast page cache, so the plugin is mostly an optimisation toolkit there.
Some services, including CDN, image optimisation and critical CSS, run through QUIC.cloud and can cost money above certain usage levels. The plugin page does not list the free limits, so check them in your QUIC.cloud dashboard before relying on them for a busy store.
Not sure what your host runs? Ask support a plain question: “Is this account on LiteSpeed?” The answer decides whether LiteSpeed Cache’s page cache will work for you.
WP Super Cache: the safe default for beginners
WP Super Cache has more than 1 million active installs and works on any host. It has three modes, and the choice matters:
- Simple: PHP serves the static files. The plugin’s documentation recommends this mode. It needs no .htaccess changes, but it does need custom permalinks.
- Expert: Apache mod_rewrite serves the files without loading PHP. It is the fastest option, but it means editing .htaccess, and a mistake there can take the site down.
- WP-Cache: The most flexible mode. It covers logged-in users, commenters, URLs with parameters and feeds, and it is slightly slower.
It also offers preloading, scheduled garbage collection, background cache rebuilds and CDN URL rewriting for files in wp-content and wp-includes. Its page does not list CSS, JavaScript or image optimisation, so you may pair it with a separate tool for that.
W3 Total Cache: the most control, with a catch
W3 Total Cache supports disk, Redis and Memcached caching, plus several others, and integrates with CDNs including Cloudflare, Bunny CDN and Amazon S3 and CloudFront. It covers page, minify, database, object and browser caching, and lazy loading of images.
That range is useful if you run a WooCommerce or membership site with a Redis server. It is also why it is easy to misconfigure. Its WordPress.org page lists several features as Pro only, including REST API caching, Delay Scripts, Eliminate Render-Blocking CSS and Fragment Cache. If you read a tutorial that mentions one of those and cannot find the setting, that is why.
WP Fastest Cache: quick setup, many extras behind a paywall
WP Fastest Cache also has more than 1 million installs. The free version covers page caching with mod_rewrite, cache timeouts, page and user-agent exclusions, preloading, Gzip compression, browser caching, CSS and JS combining, and CDN and Cloudflare support. Minify HTML and Minify CSS are free, but Minify JavaScript is not.
The premium list is long: image optimisation, WebP conversion, database cleanup, Delay JS, Defer JavaScript, lazy load and the Widget Cache. If your aim is only a fast page cache, the free version is enough. If you want an all-in-one speed tool, you will be buying the premium plan or adding other plugins.
Which one should you install?
| Your situation | Use this |
|---|---|
| Host runs LiteSpeed | LiteSpeed Cache |
| Apache or Nginx, first caching plugin, want low risk | WP Super Cache in Simple mode |
| Apache, want a short settings page | WP Fastest Cache |
| Need Redis or Memcached and CDN options | W3 Total Cache |
| Host already caches pages at server level | Often no plugin, or only the host’s own plugin |
Never run two page caching plugins at once. Deactivate and delete the old one first, then clear the cache folder it leaves behind. Two caches fighting over the same pages is a common cause of stale content and broken layouts.
Some managed hosts ship their own cache and ask you not to install another. Check your host’s documentation before adding any of these.
How caching plugins work with Cloudflare
If your site sits behind Cloudflare, the plugin and Cloudflare are two separate layers. Cloudflare’s documentation says its CDN does not cache HTML or JSON by default, and that it caches by file extension, covering images, CSS, JS and fonts. So your caching plugin still handles the HTML, and Cloudflare handles static files. To cache HTML at Cloudflare as well, you would create a Cache Rule.
That second layer is where stale content often comes from. If a change does not appear, our guide to clearing Elementor and other caches in the right order shows how to work through each layer. API responses can also get stuck, and we cover that in fixing a WordPress REST API that returns old data. For the free tier’s limits, read what the Cloudflare free plan really includes.
Set it up safely
- Take a backup, or at least note your current plugin list.
- Deactivate and delete any other caching or optimisation plugin you no longer need.
- Install your chosen plugin from Plugins > Add New and activate it.
- Turn on page caching only. Leave minify, combine and delay JavaScript off for now.
- Open your home page in a private window, and check the page still looks right and forms still work.
- If a checkout, cart or account page is involved, confirm the plugin excludes it from the cache.
- Enable one extra option at a time, testing after each, so you know what breaks a layout.
Common mistakes to avoid
Combining and delaying JavaScript is the setting that most often breaks sliders, menus and forms, so switch it on last. Caching WooCommerce cart, checkout and account pages can show customers the wrong basket, so confirm those are excluded. Forgetting to clear the cache after changing a theme or plugin makes a working fix look broken. And test in a private window as well as while logged in, because a logged-in view can behave differently from what visitors get.
Choose by server, not by popularity. LiteSpeed Cache for LiteSpeed hosts, WP Super Cache for a simple and safe start elsewhere, WP Fastest Cache for a short settings page, and W3 Total Cache when you need Redis or CDN control. Run one plugin, test after each setting, and remember Cloudflare does not cache your HTML unless you tell it to.
Frequently asked questions
Which is the best free caching plugin for WordPress?
There is no single winner. LiteSpeed Cache is the best choice on LiteSpeed hosting, and WP Super Cache is the safest general option on Apache or Nginx.
Can I use two caching plugins together?
No. Two page caches on one site conflict and cause stale pages or layout errors. Use one caching plugin, plus your host’s or Cloudflare’s separate layers if they exist.
Does LiteSpeed Cache work on non-LiteSpeed hosting?
Partly. Its general features such as minification, lazy loading and database cleanup work on any server, but the server-level page cache needs LiteSpeed or the QUIC.cloud CDN.
Do I still need a caching plugin if I use Cloudflare?
Usually yes. Cloudflare does not cache HTML by default, so a plugin still saves PHP and database work on your server.
Will a caching plugin affect WooCommerce?
It can. Cart, checkout and account pages must be excluded from page caching. Check this after installing any plugin.
Sources: LiteSpeed Cache on WordPress.org; WP Super Cache on WordPress.org; W3 Total Cache on WordPress.org; WP Fastest Cache on WordPress.org; Cloudflare default cache behavior. Checked October 2026.


