Affiliate disclosure: Some of the links in this article are affiliate links that may provide us with a small commission at no cost to you. This is helping us to create free content to help you and manage the running cost of this blog. Thank you for your support.

LiteSpeed Cache already handles page caching on LiteSpeed servers. Turning on Redis adds a second layer: object caching, which stores the results of database queries in memory so WordPress doesn’t repeat them on every uncached request.

You’ll feel it most in places page caching can’t help: the admin dashboard, WooCommerce carts and checkout, logged-in members, and search. A plain blog with mostly cached pages will see a smaller difference.

If you run a store, pair this with good WooCommerce hosting. Let us learn how to enable Redis in LiteSpeed Cache plugin.

What You Need Before Starting

1. LiteSpeed Cache plugin installed and active.
2. A Redis server running on your hosting account or server.
3. The PHP Redis extension (redis, also called phpredis) enabled for your PHP version.

On shared hosting, Redis is often a one-click option in cPanel or the host’s own panel (some hosts call it “Redis Object Cache” or include it on higher plans). On a VPS, you or your control panel installs it.

If you’re not sure, ask your host: “Is Redis available on my plan, and what host/port or socket should I use?”

How to Enable Redis in LiteSpeed Cache

Step 1: Check if Redis is available

In WordPress, go to LiteSpeed Cache > Cache > Object tab. Look at the status box at the top:

• Redis Extension: Enabled > PHP can talk to Redis.
• Redis Extension: Disabled > enable the redis PHP extension in your hosting panel (PHP Selector / Select PHP Version > Extensions) or ask your host.

Bench note: Only one object cache should run at a time. If you used the Redis Object Cache plugin before, or your host ships its own object cache drop-in, disable it before you switch this on.

Step 2: Turn on Redis in LiteSpeed Cache

Still on Cache > Object:

1. Object Cache: ON
2. Method: Redis
3. Host: usually localhost or 127.0.0.1. If your host gives you a Unix socket path (for example /home/username/.redis/redis.sock), enter the full socket path here instead.
4. Port: 6379 for a standard TCP connection. If you’re using a socket, set the port to 0.
5. Default Object Lifetime: 360 seconds is the plugin default and a sensible start.
6. Username / Password: leave blank unless your host has set Redis authentication.
7. Redis Database ID: 0 by default. If several sites share one Redis instance, give each site a different ID (0, 1, 2…) to avoid collisions.
8. Click Save Changes.

Step 3: Test the connection

After saving, the status box should show Connection Test: Passed. If it says Failed, jump to the troubleshooting section below.

Recommended settings

Setting	Recommendation	Why
Global Groups	Keep defaults	Needed for multisite consistency
Do Not Cache Groups	Keep defaults	Prevents caching volatile data like counts and plugin data
Persistent Connection	ON	Reuses the connection, slightly faster
Cache WP-Admin	ON for most sites	Speeds up the dashboard; turn off if admin screens show stale data
Store Transients	ON	Keeps transients in Redis instead of the database

Step 4: Confirm it’s working

• Query Monitor plugin: check the number of database queries on an admin page before and after. You should see fewer queries and an “Object cache: Redis” note.
• Site Health: Tools > Site Health may stop recommending a persistent object cache.
• Redis CLI (VPS): run redis-cli monitor briefly and load a page; you should see activity.

Troubleshooting

Connection Test: Failed

• Wrong host or port. Try 127.0.0.1 instead of localhost, or use the socket path your host gave you with port 0.
• Redis isn’t running. Restart it from your panel or ask your host.
• Password required. Add it in the Password field.

Redis Extension: Disabled

• Enable redis in your PHP extensions. Make sure it’s for the same PHP version your site uses.

Admin shows old data/settings won’t save

• Turn off Cache WP-Admin and test again.
• Purge the object cache (LiteSpeed Cache > Toolbox > Purge All).

Conflicts with another object cache plugin

• Only one object cache can be active. If you previously used Redis Object Cache (by Till Krüss) or W3 Total Cache’s object cache, disable it and delete the wp-content/object-cache.php drop-in it left behind before enabling LiteSpeed’s.

Site broke after enabling

• Turn Object Cache OFF in LiteSpeed Cache. If you can’t reach the admin, delete wp-content/object-cache.php via FTP or the file manager.

Redis vs Memcached in LiteSpeed Cache

LiteSpeed Cache supports both. Redis is the more common choice today, supports persistence and more data types, and most hosts offer it.

Use Memcached only if that’s what your host provides.

Is Redis worth it for your site?

Site type	Benefit
Static blog with full-page caching	Small (mainly faster admin)
WooCommerce store	High
Membership/LMS with logged-in users	High
Busy forum or community	High
News site with frequent publishing	Medium

If your site is growing past what shared hosting handles, see WordPress hosting for high traffic.

For the full caching stack, read my WordPress caching plugins guide and pair it with a CDN.

FAQs related to How to Enable Redis in LiteSpeed Cache

Conclusion

Redis is one of the cheapest speed wins on LiteSpeed hosting, as long as your host supports it.

It will not change much on a blog where every page is already cached, but it makes the dashboard snappier and helps stores and membership sites where page caching cannot.

Set it up, confirm the connection test passes, and leave it alone. If you are still deciding on the cache plugin itself, read WP Rocket vs LiteSpeed Cache first.