# Super Cache by Cloudflare

> What Super Cache does, what you need, and what is never cached. Start here before connecting Cloudflare. (Pro)

Source: https://arraystory.com/docs/ajaxpress/cloudflare-super-cache/

Super Cache by Cloudflare stores your pages on Cloudflare's network and serves them from the location nearest each visitor. A cached page is answered by Cloudflare without touching your server, so it arrives fast wherever your visitors are, and your server has far less work to do.

It needs [AjaxPress Pro](https://arraystory.com/docs/ajaxpress/ajaxpress-pro/), and lives on **Settings → AjaxPress → Cache**.

## Not another caching plugin

Your caching plugin (WP Rocket, LiteSpeed Cache, W3 Total Cache and the like) stores pages on your server, so every visit still travels to it. Super Cache stores them at Cloudflare's edge, in hundreds of cities. It runs alongside your caching plugin; there's nothing to turn off.

## What you need

- **AjaxPress Pro** with an active license.
- **Your domain on Cloudflare**, with the site's DNS record **proxied** (the orange cloud in Cloudflare's DNS settings).
- **A Cloudflare account that can run Workers.** The free plan works. It includes a daily allowance of Worker requests (100,000 a day at the time of writing). Every request to your site counts, images and scripts included, so busy sites may need Cloudflare's paid Workers plan. See [Super Cache problems](https://arraystory.com/docs/ajaxpress/super-cache-problems/#over-the-daily-worker-allowance).

## How it works

1. You [connect your Cloudflare account](https://arraystory.com/docs/ajaxpress/connect-cloudflare/), and AjaxPress installs a small Cloudflare Worker on your domain.
2. The Worker answers each page request from the cache when it can, and from your server when it can't. The page it gets from your server is stored for next time.
3. When you publish or update content, AjaxPress clears the affected pages, so visitors never see stale ones for long.

Where available, a second, globally replicated copy of your pages (the **Global layer**) makes even first visits in a new region fast.

## What is never cached

Pages that differ from visitor to visitor are always served fresh by your server. You don't need to set anything up for:

- **Logged-in users and commenters.** Anyone with a WordPress login or comment cookie bypasses the cache.
- **WooCommerce and Easy Digital Downloads shoppers** with a cart or session.
- **Cart, checkout and account pages**, and `/wp-admin`, `/wp-login.php` and `/wp-json`.
- **Add-to-cart links** and any address carrying a security token (nonce).
- **Any response that sets a cookie**, because a cookie means the page was made for one visitor.

Anything else that's personal (a members area, a personalised dashboard), [keep out of the cache](https://arraystory.com/docs/ajaxpress/exclude-pages-from-the-cache/).

## Step by step

1. [Connect Cloudflare and deploy the cache](https://arraystory.com/docs/ajaxpress/connect-cloudflare/)
2. [Keep pages out of the cache](https://arraystory.com/docs/ajaxpress/exclude-pages-from-the-cache/)
3. [Cache all pages in advance](https://arraystory.com/docs/ajaxpress/cache-all-pages/) (optional)
4. [Check cache health](https://arraystory.com/docs/ajaxpress/cache-status-and-health/)

Day to day: [purge the cache](https://arraystory.com/docs/ajaxpress/purge-the-cache/) when you need to, and [pause or disconnect](https://arraystory.com/docs/ajaxpress/disconnect-super-cache/) it if you ever stop using it.

> [!WARNING]
> Before you deactivate or delete AjaxPress or AjaxPress Pro, [disconnect Super Cache](https://arraystory.com/docs/ajaxpress/disconnect-super-cache/). Deactivating doesn't remove the Worker from Cloudflare.