Speed & performance · Guide
How to Remove LiteSpeed Cache Completely (Step by Step)

Short answer
Purge all caches, restore original images if you used image optimization, then deactivate and delete LiteSpeed Cache from the Plugins screen. Finish by removing leftover LSCACHE rules in the htaccess file, cache drop-in files in wp-content, and any litespeed tables or options in the database.
Key takeaways
- Back up files and the database before removing the plugin.
- Restore original images first if you used image optimization.
- Delete the plugin from the dashboard so its uninstall routine runs.
- Remove LSCACHE blocks from .htaccess but keep the WordPress block.
- Check wp-content for drop-ins and the litespeed folder.
- Take your domain off QUIC.cloud CDN if you used it.
How do you remove LiteSpeed Cache completely?
Purge the cache, undo image optimization if you used it, deactivate and delete the plugin, then check for leftover files, .htaccess rules, wp-config.php lines and database tables.
Deleting LiteSpeed Cache from the Plugins screen removes most of it. A few pieces can stay behind, especially on sites that used image optimization, object caching or QUIC.cloud.
Leftovers rarely break a site, but they can confuse a new cache plugin or keep serving old optimized files. This guide removes everything in a safe order.
If you are removing it because something broke, read fixing LiteSpeed Cache breaking your site first. A settings change may be all you need.
What should you do before removing LiteSpeed Cache?
Take a full backup, note your current settings, and decide what will replace the plugin so your site does not go uncached.
Prepare these items:
- A full backup. Files and database. Our guide to restoring from a backup shows why a tested backup matters.
- An export of settings. Go to LiteSpeed Cache > Toolbox > Import / Export and export the settings file in case you change your mind.
- A replacement plan. If your host runs LiteSpeed Web Server, LiteSpeed Cache is often the best fit. See does a cache plugin help on LiteSpeed hosting before switching.
- FTP or file manager access. You will need it to check leftover files.
Plan the removal for a quiet time of day. The site will be slower for a short while until another cache is in place.
Step 1: How do you purge the cache?
Go to LiteSpeed Cache > Toolbox > Purge and click Purge All, so no cached pages or optimized files remain in use.
You can also use the LiteSpeed icon in the admin bar and choose Purge All. This clears the page cache, CSS and JS optimization files and, where enabled, the object cache.
If you use QUIC.cloud CDN, purge it as well. The purge buttons in the plugin can include CDN purges when the domain is linked.
Our full guide on how to purge LiteSpeed Cache covers every purge option.
Step 2: What about image optimization?
If you optimized images through LiteSpeed Cache, switch back to the original files and remove the optimization data before you delete the plugin.
Image optimization can replace your images with compressed versions and create WebP copies. Once the plugin is gone, you lose the buttons that undo this.
Go to LiteSpeed Cache > Image Optimization and look at the summary area. Recent versions include:
- A control to switch between optimized and original files.
- A button to remove original image backups. Do not press this if you want the originals back.
- A button to destroy all optimization data.
Switch to the original files first, then remove the optimization data if you want a clean slate. Labels can vary by version, so read each button carefully. The LiteSpeed documentation describes the Image Optimization screens.
If you never used image optimization, skip this step.
Step 3: How do you turn off object cache and other features?
Disable object cache, the crawler and the CDN settings inside LiteSpeed Cache before deactivating, so it can clean up the files it created for them.
Check these areas:
- Cache > Object. Turn off Object Cache and save. This removes the
object-cache.phpdrop-in in most cases. - Crawler. Turn off the crawler so it stops queuing pages.
- CDN. Turn off QUIC.cloud CDN or other CDN settings if enabled.
If you use Redis or Memcached through your host, the server service will keep running. That is fine.
It simply stops being used by WordPress once the drop-in is gone. Read page cache vs object cache if you plan to keep object caching with another plugin.
Step 4: How do you deactivate and delete the plugin?
Go to Plugins > Installed Plugins, click Deactivate under LiteSpeed Cache, then click Delete and confirm.
Deactivation removes the LiteSpeed rules the plugin added to .htaccess. Deleting from the Plugins screen also runs the plugin's uninstall routine, which removes much of its data.
Always delete through the dashboard rather than by removing the folder over FTP. Removing the folder skips the uninstall routine, so more leftovers stay behind.
If the plugin is crashing the admin area, rename wp-content/plugins/litespeed-cache over FTP to disable it, log in, then rename it back and delete it from the dashboard. Our guide to uninstalling broken plugins explains this method.
Step 5: How do you check .htaccess for leftover rules?
Open .htaccess in your site root and remove any block between # BEGIN LSCACHE and # END LSCACHE, plus any NON_LSCACHE block.
The blocks look like this:
# BEGIN LSCACHE
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
...
# END LSCACHE
# BEGIN NON_LSCACHE
...
# END NON_LSCACHE
Delete both blocks entirely, including the BEGIN and END lines. Leave the # BEGIN WordPress block alone, because it controls your permalinks.
You may also find backup files such as .htaccess_lscachebak_orig or numbered .htaccess_lscachebak copies. These are old backups made by the plugin. You can delete them once your site works.
If you are not sure how to edit the file safely, see how to edit the .htaccess file. After saving, go to Settings > Permalinks and click Save to rebuild the WordPress rules.
Step 6: Which leftover files should you delete?
Check wp-content for advanced-cache.php, object-cache.php, the litespeed folder and old config files, and delete any that belong to LiteSpeed Cache.
| Item | Location | What it is |
|---|---|---|
| advanced-cache.php | wp-content | Page cache drop-in |
| object-cache.php | wp-content | Object cache drop-in |
| litespeed folder | wp-content | Optimized CSS, JS and other generated files |
| .litespeed_conf.dat | wp-content | Config file used by some versions |
| .htaccess_lscachebak files | Site root | Backups of .htaccess |
| WP_CACHE line | wp-config.php | Turns on the cache drop-in |
Open each drop-in before deleting it. If advanced-cache.php or object-cache.php mentions another plugin, such as a Redis plugin, leave it alone.
Next, open wp-config.php and look for:
define( 'WP_CACHE', true );
Remove it only if you will not install another page cache plugin. Most cache plugins add it back themselves. WordPress explains the constant in the wp-config.php documentation.
Step 7: How do you clean the database?
Look for tables whose names start with your table prefix plus litespeed, and options whose names start with litespeed, then delete them after a database backup.
Most installs will have few or none left after a dashboard delete. Older versions and sites that used image optimization or the crawler may still have some.
In phpMyAdmin or Adminer:
- Back up the database first. See how to back up a WordPress database.
- Search the table list for
litespeed. Tables used for URLs, image optimization, avatars and the crawler may appear. - Drop only tables with
litespeedin the name. - In the options table, search for option names starting with
litespeedand delete them. - In the postmeta table, search meta keys containing
litespeedif you used image optimization.
You can run a search like this to list the options first:
SELECT option_name FROM wp_options WHERE option_name LIKE 'litespeed%';
Change wp_ if your table prefix is different. Run a SELECT before any DELETE so you can see exactly what will go.
Step 8: What about server cache and QUIC.cloud?
If you used QUIC.cloud CDN, change your DNS back to your host or remove the domain from your QUIC.cloud dashboard, or traffic may still flow through it.
The CDN works at DNS level, so deleting the plugin does not take your domain off it. Log in to your QUIC.cloud account and check the domain settings. Our QUIC.cloud setup guide shows where those settings live.
On LiteSpeed hosting, the server's cache engine stays installed. Without the plugin's .htaccess rules it does not cache your pages, so it will not interfere with another plugin.
Some hosts also have a cache toggle in the control panel. Check your host's dashboard if pages still look cached.
The LiteSpeed Cache plugin page on WordPress.org lists the features that may have left settings behind.
How do you confirm LiteSpeed Cache is fully gone?
Check the response headers and page source of a few pages, and confirm that no LiteSpeed headers or optimized file paths remain.
Open your browser's developer tools, go to the Network tab, and reload a page. Look at the response headers for x-litespeed-cache. If it still appears, a rule or server setting is still active.
Also view the page source. Links to files in /wp-content/litespeed/ mean a cached page or a leftover folder is still in use.
Then install your new cache plugin, configure it, and test the site's speed. Run through clearing cache in WordPress once more to be sure every layer is fresh.
Frequently asked questions
Does deleting LiteSpeed Cache remove its .htaccess rules?
Deactivation normally removes the LSCACHE block from the .htaccess file. If the file was not writable, or the plugin crashed, the rules can stay. Open the file after deletion and remove any LSCACHE or NON_LSCACHE blocks by hand, then resave permalinks.
Will removing LiteSpeed Cache slow down my site?
Pages will be generated fresh on every visit until you set up another cache, so the site may feel slower. Install and configure a replacement cache plugin soon after removal, or use your host's built-in caching if it offers one.
Will my images break after removing LiteSpeed Cache?
Usually not, but you should switch back to the original images before deleting the plugin if you used image optimization. If you removed original backups earlier, the compressed versions stay in place, which still display normally.
Can I reinstall LiteSpeed Cache later?
Yes. Install it again from the plugin directory and import the settings file you exported before removal. You will need to reconnect QUIC.cloud services and run image optimization again if you want those features.
Is it safe to delete the WP_CACHE line?
Yes, if no other cache plugin needs it. The line only tells WordPress to load the advanced-cache drop-in. If you install a new cache plugin, it will usually add the line back itself during setup.
Sources
- LiteSpeed Cache WordPress.org
- LiteSpeed Cache for WordPress documentation LiteSpeed Technologies
- LSCWP admin and toolbox LiteSpeed Technologies
- wp-config.php WordPress Developer Resources
- Managing plugins WordPress.org Documentation
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


