RunCache supports several page cache types, depending on your server environment.

This guide explains how the available cache types differ, which options RunCache may offer on your server, and how to choose and switch between them.

For instructions on accessing and configuring Full Page Cache in RunCache, see Full Page Cache.

How the Cache Types Differ

Without page caching, WordPress generates the page for each request.

A page cache stores the generated HTML so later requests can reuse it. The cache type determines where the cached page is stored and which part of the server stack serves it.

  • PHP Cache stores cached pages as files on disk and serves them through PHP. It does not require web server configuration and is the default RunCache cache type.
  • NGINX Page Cache and Apache Page Cache store cached pages as files on disk and serve them directly through the web server. PHP creates the cached file, but later cached requests can be served without starting PHP.
  • NGINX FastCGI Cache stores responses in NGINX’s FastCGI cache and can serve cached requests without starting PHP or WordPress. It typically requires more server configuration than NGINX Page Cache.
  • Redis Page Cache stores cached pages in Redis and serves them through PHP. It requires a working Redis server and the PHP Redis extension.
  • LiteSpeed Page Cache uses the LiteSpeed server’s page-cache system to serve cached responses at the server level. It is available on LiteSpeed and OpenLiteSpeed servers.

RunCache displays the cache types available for the detected server environment.

Cloudflare edge caching is configured separately under CDN Edge Cache. It is not one of the local page-cache types listed above. For more information, see Assets CDN vs. CDN Edge Cache: What’s the Difference?

Why Available Cache Types Vary by Server

RunCache detects the server environment and displays only the cache types supported by that server.

For more information about server detection, see RunCache and RunCloud.

The server detection notice identifies the detected server type. The cache cards below it show the available cache options.

Cache Types by Server Environment

Detected serverCache types offered
NGINXNginx Page Cache, Nginx FastCGI Cache, Redis Page Cache
RunCloud server with connected web applicationRunCloud NGINX FastCGI Cache, RunCloud NGINX SrcCache Cache, Redis Page Cache
RunCloud server without a connected web applicationNGINX Page Cache, NGINX FastCGI Cache, Redis Page Cache
ApacheApache Page Cache, Redis Page Cache
LiteSpeed or OpenLiteSpeedLiteSpeed Page Cache, Redis Page Cache
Not detectedRedis Page Cache

Redis Page Cache can be available across different server types because it does not depend on web server configuration.

If the PHP Redis extension is missing, RunCache disables the option and prompts you to install it.

PHP Cache as the Default Option

PHP Cache is the default RunCache cache type and does not appear as a separate option card.

If you disable an active server-level cache type, RunCache falls back to PHP Cache rather than disabling page caching completely.

RunCache Recommendations by Server Type

Each detected server gets one notice above the grid. Read it before you choose:

  • NGINX: RunCache recommends NGINX FastCGI Cache when you are comfortable with the additional server configuration. NGINX Page Cache requires less setup.
  • Apache: RunCache recommends Apache Page Cache.
  • LiteSpeed: RunCache recommends LiteSpeed Page Cache.
  • RunCloud server without a connected web application: configure the supported server-level cache through the RunCloud Dashboard when available. For more information, see the RunCloud-specific cache setup documentation.

Choose a Cache Type

  1. If you do not want to edit web server configuration, use PHP Cache or Redis Page Cache if Redis is available.
  2. On NGINX, choose between:
    • NGINX Page Cache for a simpler configuration.
    • NGINX FastCGI Cache if you want to use NGINX’s FastCGI cache and are comfortable with the additional setup.
  3. On Apache or LiteSpeed, use the corresponding server-level cache type supported by your server. See the Apache Page Cache or LiteSpeed Page Cache setup guides for configuration details.

Switching Cache Types

When you switch cache types, RunCache disables the previous cache provider, enables the new provider, and verifies the new configuration.

The dashboard may briefly display a Checking configuration status while verification runs.

Switch Cache Types with WP-CLI

Before switching to a server-level cache type with WP-CLI, make sure the required server configuration is already in place.

Then run the appropriate wp runcache enable command from your WordPress installation.

wp runcache enable nginx

If verification fails after switching to a server-level cache type, confirm that the required server configuration has been added and the web server has been reloaded.

Then verify the cache again.

For a complete list of available commands, see the WP-CLI command reference.

After switching cache types, verify the result using the Verifying the cache is working guide.

You can confirm the active cache type from the X-RunCache-Type response header.

If you have any other questions or need help, please feel free to get in touch with our 24/7 support team. We’re here to help!