The Cache tab in the LiteSpeed Cache plugin controls page-level caching for your WordPress site. On Flashcloud, this plugin is pre-installed and pre-configured on every WordPress install, working with LiteSpeed Web Server's built-in LSCache engine. For most sites the defaults are correct and you don't need to touch this tab at all. You only need it when you're troubleshooting stale content, excluding a specific page from caching, or tuning TTLs for a site with unusual traffic patterns.
LSCache is a full-page cache: the first visitor to a page triggers LiteSpeed to generate and store a static copy of the HTML, and every visitor after that gets served the cached copy directly by the web server, before PHP or WordPress ever loads. That's why it's faster than most caching plugins that run in PHP, since PHP execution is the expensive part of a page load.
Where the Cache tab lives
In WP Admin, go to LiteSpeed Cache → Cache. The tab is split into sub-sections: Cache, Purge, Excludes, ESI (Edge Side Includes), Object, and Browser. The main Cache sub-tab has one setting that matters most: Enable Cache. It should be ON. If a site is behaving oddly after a migration or a manual install, check this first, since caching can end up disabled if the plugin was reset.
Below that sit toggles for what gets cached: logged-in users, commenters, REST API calls, login page, favicon.ico, and PHP resources. Leave logged-in user caching off unless you specifically need it, since caching per-user pages multiplies your cache storage and can leak one visitor's session data into another's view if misconfigured.
TTL settings
Further down, you'll find time-to-live values for different content types: public pages, private (logged-in) pages, the front page, feeds, and REST calls. These are in seconds. The default public TTL is generally fine for most sites. If you run a news or deals site where content changes constantly, lowering the front-page TTL to a few minutes keeps things fresher without disabling caching entirely. If you run a mostly-static brochure site, you can raise it.
There's also a separate 404 and 403 TTL. Caching error pages for a short window stops a flood of bad requests (broken links, scanners probing for old plugin paths) from hammering PHP on every hit.
Purge options
The Purge sub-tab controls what triggers an automatic cache clear. By default, publishing or editing a post purges that post plus related pages (the front page, category and tag archives, feeds). This is what you want in almost all cases, since it means the cache updates itself as content changes.
If you need to force a clear right now, for example after a theme change or a plugin update that isn't showing up, use the Purge All button under LiteSpeed Cache's admin bar menu, or the Purge All option in this tab. On Flashcloud you can also clear caching layers from outside WordPress: the Cloudflare CDN "Purge cache" control clears the edge cache if the domain is proxied, which is a separate layer from LSCache. If a change still isn't showing after purging both, check your browser cache too.
Excluding pages from cache
The Excludes sub-tab lets you keep specific URLs, query strings, cookies, or user agents out of the cache entirely. This matters for pages that must always render fresh: a cart or checkout page, a logged-in dashboard, or any page that shows per-visitor content but isn't already covered by the logged-in/commenter toggles. Add the path under Do Not Cache URIs, one per line, using the format the tab documents (it accepts partial matches and regex).
Common exclusion candidates are WooCommerce cart/checkout/my-account pages and any page built with a personalization plugin. Most WooCommerce and membership plugins that are LiteSpeed-aware add their own exclusions automatically, so check what's already listed before adding duplicates.
How this fits with object caching
The Cache tab handles full-page HTML caching. Separately, WordPress installs on Flashcloud also get Redis object caching, which speeds up database queries rather than whole-page renders. Object cache settings live under the plugin's Object tab or Redis-specific menu depending on the plugin version installed. Page cache and object cache are independent layers: clearing one doesn't clear the other, and a stale-content problem can come from either.
When to contact support
If cache settings look correct but pages still serve stale content after a full purge (LSCache, Cloudflare, and browser), or if Enable Cache won't stay on after saving, open a ticket from the portal under Support. That's usually a server-side LiteSpeed configuration issue rather than something fixable from the plugin UI, and a real person can check the server-level cache state directly.