by
mandaffaaord
0 (0 reviews)
CacheArmor
Disk cache for expensive WP REST API responses, with stale-while-revalidate and stampede protection. Full route picker, no paid tier.
CacheArmor ranks #72,121 among WordPress.org plugins with 0+ active installations, is #1,311 of 1,658 in the Performance category, and was last updated Sep 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.4.0
Current Version v1.4.0
Updated 1 month ago
Last Update on 29 Sep, 2026
Refreshed 2 days ago
Last Refreshed on
#1,311 of 1,658 in Performance
Rank
#72,121
—
No change
Active Installs
0+
-100%
KW Avg Position
N/A
—
No change
Downloads
169
+2 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
44,553
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#72,121
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.4.0
- Last Updated
- Sep 29, 2026
- Requires WP
- 5.6+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- mandaffaaord
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
WP Super Cache
1M+ installs
#36
Speed Optimizer – The All-In-One Performance-Boosting Plugin
1M+ installs
#44
WP Fastest Cache – WordPress Cache Plugin
1M+ installs
#47
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
1M+ installs
#52
Maintenance
1M+ installs
#59
Frequently Asked Questions
Common questions about CacheArmor
By design. Caching the wrong endpoint can serve one visitor's data to another, so you must choose which routes are safe to cache under Settings > CacheArmor.
Yes. The settings screen lists all registered REST routes, including those added by other plugins and your own code, so custom endpoints appear alongside the core ones. Routes with placeholders, such as a single post by ID, cannot be selected there yet; add those with the cachearmor_rules filter.
A route with a permission check may give different responses to different visitors, so cache it only if you are certain every anonymous visitor receives the same response. "Public" means anyone may call the route. It does not guarantee that every visitor gets the same response: a route can still vary by cookie, session or location. The same care applies.
Responses carry an X-CacheArmor header with a value of HIT, STALE or MISS, plus X-CacheArmor-Age in seconds.
Turn on Pause caching on the Settings tab under Settings > CacheArmor. To pause it from code instead, add define( 'CACHEARMOR_DISABLE', true ); to wp-config.php.
Click Clear cache now on the settings screen, or Clear REST cache in the admin bar. Developers can call CacheArmor::purge_all(). The cache is also cleared automatically when content visitors can see is published, updated, unpublished or deleted, and when a category, tag or other public term changes. Drafts and internal post types do not trigger it. Narrow it further with the cachearmor_should_purge filter. The settings screen shows when the cache was last cleared and why.
In a cachearmor folder inside your uploads directory, usually wp-content/uploads/cachearmor/, resolved at runtime with wp_upload_dir(). On multisite, each site's lives in that site's own uploads directory. The folder is protected from direct access and removed when you delete the plugin. Entries are plain JSON data; the plugin never writes files containing code.
Logged-in requests, anything other than GET, non-200 responses, routes with no matching rule, blocked routes, requests carrying a shopping session, and payloads larger than max_bytes (8 MB by default). Add your own exclusions with the cachearmor_blocked_routes and cachearmor_bypass_request filters.
New responses are simply not stored until the cache is next cleared; existing entries keep being served and refreshed. The settings screen tells you when this happens. Narrowing your query filters is usually the fix, or raise the limits as below.
Yes, with the cachearmor_config filter. Options are ttl, grace, lock_ttl, cold_wait, max_bytes, max_entries, max_total_bytes, send_headers, and dir to store the cache somewhere other than the uploads directory.
