The General tab in the LiteSpeed Cache plugin controls the master switches for caching on your WordPress site. On Flashcloud, this plugin ships pre-installed and pre-configured on WordPress hosting, so in most cases you don't need to touch this tab at all. The one setting worth knowing is Enable Cache, which should stay ON. If a specific page or feature seems to be showing stale content, this tab is where you check that caching hasn't been accidentally disabled.
Everything here is the WordPress-side control panel for the same LSCache engine running at the server level. For the full picture of how the two layers work together, see the cache stack we ship with every WordPress install.
Where to find it
Log into wp-admin, then go to LiteSpeed Cache → Cache → General. This is the first tab you land on when opening the plugin's Cache settings page.
Enable Cache
This is the master toggle. When it's ON, LSCache serves full-page cached copies of your site to logged-out visitors straight from the server, skipping PHP and the database entirely for those requests. When it's OFF, every visitor triggers a full WordPress page load, and your site will feel noticeably slower under any real traffic.
There's no reason to turn this off permanently. If you're actively debugging a plugin conflict or a visual bug and want to rule out caching as the cause, it's fine to disable it temporarily, but turn it back on when you're done.
Cache Logged-in Users
By default, visitors who are logged into WordPress (subscribers, customers with accounts, etc.) don't get cached pages, since their view of a page can differ from a logged-out visitor's. If your site has a large base of logged-in users who all see the same content (a membership site with no personalization, for example), enabling this can extend caching's benefit to them too. If pages show one user's data to another user after enabling this, turn it back off. That's a sign the page has per-user content that shouldn't be cached.
Cache Commenters and Cache REST API
These are narrower toggles for specific request types. Cache Commenters affects visitors who've left a comment (WordPress sets a cookie so they see their pending comment immediately). Cache REST API affects caching of wp-json endpoint responses. Leave both at their defaults unless you have a specific reason to change them. If a headless frontend or a JS-driven feature on your site depends on always-fresh REST API responses, that's when you'd turn Cache REST API off.
Private Cache and TTL settings
Further down the General tab you'll find TTL (time-to-live) fields for public pages, private cache, and front page. These control how long a cached copy is served before LSCache checks for a fresh version. The defaults are sane for most sites. Shortening these makes your cache less effective (more requests hit PHP); lengthening them means content updates can take longer to appear for visitors who already have a cached copy.
When to leave this tab alone
If your site feels fast and pages update correctly after you publish or edit them, there's nothing to configure here. The defaults we ship are tuned to work well on most hosting accounts. Chasing marginal TTL adjustments rarely moves the needle compared to what the server-level stack already provides; see how we make your site fast for the bigger picture of what's happening between LiteSpeed and Cloudflare on every request.
When to contact support
If you've enabled or disabled settings on this tab and your site now shows outdated content, mixed-up user data, or broken behavior that doesn't resolve after a manual purge, open a ticket from the portal's Support section. We'll look at your specific configuration.