Skip to main content
LiteSpeed Web Cache Manager is a one-page UI for managing the LiteSpeed Cache for WordPress plugin across every WP install in your account. Detect installs, enable LSCache on all of them, flush them all in one click.
LiteSpeed Web Cache Manager with WordPress install list

​
What you get

The page scans your account for WordPress installs and lists them. For each site you can:
  • Enable LSCache: installs and activates the LiteSpeed Cache plugin on that site.
  • Disable: deactivates the plugin (without deleting it).
  • Flush: clears the page cache for that one site.
Top of the page also has Mass Enable and Mass Flush All buttons that act on every WP install at once.
This tool only manages the page cache. For object caching (Redis), see LiteSpeed Redis Cache Manager. Most WP sites benefit from running both.

​
When to use it

The plugin can be installed by hand from wp-admin → Plugins → Add New → LiteSpeed Cache. Use this UI when:
  • You manage many WordPress sites in one cPanel account and don’t want to log in to each /wp-admin to install the plugin.
  • You need to flush all sites at once after a global change (CSS update, deploy, etc.).
  • You’re auditing which sites have LSCache active.
For a single site, installing from wp-admin is faster.

​
Mass enable

1

Click Scan

The page rescans the account and refreshes the list of WordPress installs. Run this if you’ve installed a new WP site since you last opened the page.
2

Click Enable in the column header

The Enable column flips to “On” for every detected install. Each site now has LSCache plugin installed and activated, with safe default settings.
3

Verify on one site

Visit wp-admin → LiteSpeed Cache → Dashboard. The dashboard should load and show the standard plugin UI. From there, follow the LSCache rollout guide to tune settings per site.

​
Flush all

The Flush All button at the top wipes page caches across every WP install in this account. Reach for it after:
  • A global asset change (CSS or JS file replaced server-side).
  • A deploy that touched template files outside wp-admin.
  • A confusing bug where you suspect cache is involved.
Flushing is fast and safe. The next request to each site rebuilds its cache.

​
Common questions

Two usual reasons. First, the cache hasn’t been warmed yet: the very first request to each page generates and stores the cached version, and only subsequent requests are served from cache. Hit a few key pages or run a crawler. Second, you have a plugin (often a security plugin or a session-heavy plugin) that emits Cache-Control: no-cache on every response. Check the response headers in browser dev tools; if X-LiteSpeed-Cache: hit appears, caching is working.
Defaults are conservative and usually fine. To customize, go to wp-admin → LiteSpeed Cache for that site. The plugin has its own dashboard with cache rules, image optimization, CSS/JS minification, and more. Settings are per-site.
AccelerateWP is a separate WP-Rocket-style plugin from CloudLinux. LSCache is from LiteSpeed. They both do page caching, but they don’t compose: pick one. If you’re already on LSCache, stay on LSCache. AccelerateWP is the better fit only if you need its specific extras (database cleanup, Heartbeat throttling) that LSCache doesn’t bundle.
No. Disable deactivates the plugin in WordPress; the plugin files stay in wp-content/plugins/litespeed-cache/. Re-enabling reactivates it without reinstalling. To fully remove, deactivate here, then delete from wp-admin → Plugins.

​
Need a hand?