WP Redis

What is WP Redis?

WP Redis is a dedicated object cache plugin that connects WordPress directly to a Redis server. It replaces the default database-driven object cache with a high-speed, in-memory data store. The plugin is developed by Pantheon Systems, a major WordPress hosting platform, and has been actively maintained for 12 years. As of its latest update on Dec 11, 2025, it runs version 1.4.7 and holds 9K+ active installations.

The plugin enjoys a strong 4.7/5 rating from 20 reviews, with 85% of users giving it five stars. Only 5% of ratings are one-star, indicating consistent performance for its target audience. It is built for sites that need a persistent object cache that scales across multiple application instances, making it a practical choice for high-traffic environments.

Key Features of WP Redis

• Persistent Object Cache: Replaces WordPress’s default runtime cache with Redis, keeping data in memory across page loads and server instances.
• WP-CLI Integration: Offers five dedicated commands under the wp redis namespace for enabling, debugging, and inspecting the cache directly from the command line.
• Debugging Tools: The wp redis debug command provides hit/miss ratios for any page URL, helping you identify cache performance issues.
• Scalable Architecture: Designed for multi-server setups, allowing the object cache to be shared across all web nodes without data duplication.
• Non-Persistent Group Support: Lets developers exclude specific plugin cache groups from Redis via wp_cache_add_non_persistent_groups(), preventing problematic plugins from flooding the cache.
• PhpRedis & Predis Compatibility: Works with the required PhpRedis extension, and also supports the Predis library via humanmade/wp-redis-predis-client for flexible deployment.
• Symlink-Based Installation: Provides a clean method to drop object-cache.php into wp-content/ using a symlink, keeping the plugin directory separate.

Who Should Use WP Redis?

This plugin is for site owners who understand the difference between page caching and object caching. It is not a page cache plugin like WP Super Cache or W3 Total Cache. WP Redis targets developers and technical site managers running sites with high traffic, dynamic content for logged-in users, or heavy database loads. It requires a working Redis server and the PhpRedis PHP extension, so it suits users comfortable with server-level configuration.

With 9K+ active installs, the user base skews toward managed hosting environments—particularly Pantheon customers—but the plugin works on any self-hosted WordPress site with Redis. The developer’s documentation explicitly warns that a page load with 2,000 Redis calls can add 2 full seconds of transaction time, so the ideal user is someone who monitors cache keys and avoids storing excessive data per key. This is a tool for optimization, not a set-and-forget solution.

Installation & Setup

Install WP Redis from the WordPress plugin directory or GitHub, then activate it. The critical step requires placing object-cache.php into wp-content/ via a symlink or direct copy. This is not a beginner-friendly process—it assumes you have a working Redis server and the PhpRedis extension loaded in your PHP environment. For Pantheon users, the setup is handled automatically by the platform.

Support & Community

Support data for the two months leading up to Dec 11, 2025 shows 0 open support threads and 0 resolved threads, yielding a 0% resolution rate. This figure suggests either that users are not encountering issues requiring forum support, or that they rely on Pantheon’s direct support channels. The rating breakdown—85% 5% one-star from 20 total ratings—tells a positive story despite the forum silence. The plugin’s 12-year development history indicates a mature codebase that rarely requires hands-on support for its defined use case.

The plugin’s wiki on GitHub provides code snippets and tips for managing cache groups and avoiding race conditions with the WordPress alloptions cache. For contributors, the repository includes a CONTRIBUTING.md file. Given the low support thread volume, most users likely configure this plugin once and leave it running without further interaction.