# Disable LSCache
Source: https://docs.webgee.com/en/hosting/wordpress/litespeed-how-do-i-disable-lscache



Turns off LSCache for a WordPress installation that currently has it. Applies to
all shared and reseller hosting.

To stop WebGee installing it in the first place, see
[Prevent LSCache from auto-installing](/en/hosting/wordpress/litespeed-prevent-lscache-from-auto-installing)
instead — that is a different action, and doing this one alone will not stop it
returning.

## Disable it [#disable-it]

1. Log in to cPanel and open **LiteSpeed Web Cache Manager**.
2. Select **WordPress Cache**.
3. Select **Scan** to find the WordPress installations on the account.
4. Select **Disable** beside the installation.

## Before you do [#before-you-do]

<Callout type="warn">
  Disabling the page cache means every request is generated by PHP. On a busy
  site that is a large increase in load, and it counts against your account's
  resource limits. Expect slower pages and, on shared hosting, a higher chance
  of hitting entry-process limits.
</Callout>

Most reasons for disabling LSCache are better solved another way:

* **A page shows stale content** — exclude that URL in the plugin's settings
  rather than disabling the cache for the whole site.
* **A cart or checkout misbehaves** — LSCache excludes WooCommerce cart pages
  by default. If it is not doing so, the plugin's preset is wrong; see
  [LiteSpeed Cache presets](/en/hosting/wordpress/litespeed-cache-presets-for-wordpress).
* **You want to use a different cache plugin** — then disabling is correct.
  Running two page caches at once causes problems.

## It will come back [#it-will-come-back]

WebGee runs an automated process that enables LSCache across WordPress
installations on the server. Disabling it here does not opt out of that process,
so the cache can be re-enabled later.

To opt out permanently, flag the installation as well — see
[Prevent LSCache from auto-installing](/en/hosting/wordpress/litespeed-prevent-lscache-from-auto-installing).

## Verify [#verify]

Load the site in a private window and confirm the `x-litespeed-cache` response
header is gone. See
[Check whether LiteSpeed Cache is working](/en/hosting/wordpress/how-do-i-check-if-litespeed-cache-is-working-on-my-site).

## Related [#related]

* [Prevent LSCache from auto-installing](/en/hosting/wordpress/litespeed-prevent-lscache-from-auto-installing)
* [Check whether LiteSpeed Cache is working](/en/hosting/wordpress/how-do-i-check-if-litespeed-cache-is-working-on-my-site)