Hyper Cache

Hyper Cache is a lite, simple to configure and highly performant cache plugin for WordPress.

Hyper Cache is a cache system for WordPress. I wrote it because my hosting provider was very low in resources, particularly on the MySql side. Hyper Cache solved all my performance problems. It probably can solve yours as well!

The aim of Hyper Cache is to be efficient but easy to configure. It has a simple configuration panel with preset values ready for your blog. You can tweak the configuration to improve even more the performances or to address specific needs.

It is bbPress ready: Hyper cache is able to detect new topics and replies and refresh the forum cached pages.

Migration from 2.x to 3.x

Since the option panel has been rewritten, I added an import button to automatically migrates the original 2.x options to the new 3.x options. Migration related issues can be reported on the dedicated forum.


Please use the forum to ask for support, thank you an read the F.A.Q. below.

How to detect if it is working

Use a clean browser (not the one you use to administer your blog or open a new browser window in anonymous mode), and load the same page a couple of times. Look at the page source and at bottom you should see the Hyper Cache signature.

Another way is to use a browser developer tool and look at the network panel: the response header for a cached page should contains the specific “X-Hyper-Cache” header with value “hit” or “hit-mobile”.

Hyper Cache main features

  • easy installation: just activate Hyper Cache and it works with a set of default values
  • easy configuration: you can just ignore the configuration panel (even if enabling the compression is a good idea!)
  • mobile cache: separated cache for mobile devices (when you use mobile oriented themes or plugins)
  • theme switch for mobile devices
  • compression support to optimize your bandwidth usage and the overall page load speed (important with mobile devices)
  • configurable bypass (when the cache should not… cache): by page address, user agent, cookies, feeds and so on
  • 404 caching
  • bbPress ready: can cache and refresh bbPress pages
  • special refresh options
  • configurable caching only of the newest posts

Download and Installation

Download it from the WordPress Plugin Repository or search for “Hyper Cache” in your blog plugin panel. Once activate, go to the configuration panel and follow the instructions.

Usually you need wo add a lince of code in the wp-config.php file just after the define(‘WPLANG’, ‘xx_YY’):

define('WP_CACHE', true);

If that definition is already present in your wp-config.php file, modify it as shown above.

The plugin options are explained inside the configuration panel, here you can find some deeper concept or annotations.


Cached pages will be valid for…

It’s a time in hours used to consider still valid an already cached page. If a page is in cache but older than the specified number of hour, it is not considered and regenerated.

Cache folder

Usually you should leave this option empty to use it’s default value (auto computed by Hyper Cache). The cache folder where cached pages are store is locate at wp-content/cache/hyper-cache. You can specify an absolute path lo move it but pay attention: is you wrongly point the cache folder to an existing folder with files, on cache refresh they can be deleted.


Compression should be enabled for two reason:

  1. save a bit of bandwidth (mostly of the bandwidth is used for images and not for the text part of a page…)
  2. serve the content as quickly as possible to make the user experience better

More, if you have a mainly textual blog, you’ll save traffic on the client side, which is very good for mobile user with expensive data plans.

If you note strange characters instead of the regular page when the compression is enabled, it means your server is already compressing the pages on the fly. Seen that a cached compressed page is much more efficient than compressing the page on the fly, you should configure the server to not compress the html and xml mime types (but let it compress JavaScript and CSS).

Browser caching

When the browser caching is enabled, Hyper Cache tells browsers to keep a copy of the page in their cache and to not request the page again (until it expires).

The expiration time can be set in hours in the option panel or it will be computed as the time remaining for the page in your blog cache. For example, if the page has been cached 1 hour ago and your cache timeout is set to 24 hours, the browser will receive the suggestion to keep the page for 23 hours.

Pay attention: I usually keep this option off because if you change something of important in your blog, regular users will see always the already visited pages and cached in their browser. Only a forced reload will refresh the local user cache but not all web users know about it.


Hyper Cache can be configured to totally ignore some type of pages. For example you may want to not cache the home page to have it always fresh or the feeds to save disk space since they are rarely requested. Remember that WordPress has a feed for each post…

Other bypass are based on matching rules: for example if you have a forum installed which pages live under the URL “/forums” (actually it’s more correct to call the URIs), to never cache such pages add “/forums” to the “starting with URIs to bypass”.

Other bypasses are per user agent, cookie name or exact URI.

URI matching

The URI is the part of a site page address without the domain name. For example this page address is


the URI is “/plugins/hyper-cache” with a starting “/”. So if I want to NOT cache this page I need to specify “/plugins/hyper-cache” as URI to bypass.

If there are more than a URI to exclude just insert one per line. Remember: the URI is the full piece after the domain name. If your blog is installed under a path like:


to exclude that page you must use as URI the value “/blog/plugins/hyper-cache”.

For the “starting with” URI matching the same considerations apply.

The special case of comment authors

When a user leaves a comment in your blog, WordPress uses some cookies to store his data and fill the comment for fields with his name, email and site, The cache must take care of that, to avoid serving a page with those fields filled with another user data.

So, most of the caches simple disable them self when a visitor has those comment cookies. Hyper Cache is able to manage that situation and serve cached pages to comment authors visiting the blog, still pre-filling the comment fields with the visitor’s data.

This is done injecting a little JavaScript on single post. To disable that injection, just disable the serving of cached page to comment authors.


If your blog is serving different content and or a different theme to mobile devices, you must consider to have a double cache, one for the desktop content/theme and one for the mobile content/theme.

Mobile detection must be enabled and the user agents set compatibly to the ones used by other plugin/themes. Hyper Cache must be able to decide to serve the desktop or mobile version on its own, otherwise the cache benefit will be lost.

Hyper Cache can be configure to activate a different theme  when it detect a mobile device: it’s a simple integrated theme switcher.

A use case. I use Header and Footer to inject different ads formats for mobile devices, even if the theme does not change (it’s responsive). I have Header and Footer detecting the mobile devices in the same fashion than Hyper Cache so pages are cache with different ads code for desktop and mobile visitors.

Unluckily there is no a standard in WordPress so a detection system can be used initially and make all the plugin use it…


My cart widget does not work anymore. Do not use the cache or look at a widget configuration which let it to be loaded via AJAX.

My statistic plugin is no more working. Hyper Cache, when possible, serves directly a page without activate WordPress (and hence the installed plugins).

The cache folder is missing. Create it manually wp-content/cache/hyper-cache. For security reason some blogs have a write lock on wp-content folder.

I found no file in the cache folder. Try to set it to 777 permission level: for some reasons and on some providers Hyper Cache cannot write in that directory.

Why have I to use Hyper Cache and not other cache systems? I really cannot answer that question: Hyper Cache is free as for other cache plugin… take the one which gives more performances to your blog!

Where are the cache pages? In to the folder /wp-content/cache/hyper-cache: if you empty that directory the cache starts from zero. Do not delete the directory!

Why there is a JavaScript added at the end of cached pages?

It’s to pre-fill the comment fields even on cached pages. To disable it disable the serving of cached pages to comment authors.


This page, even if not complete, collects come configuration tips for Hyper Cache. If you have questions, please write me at <a href=”mailto:info@satollo.com”>info@satollo.com</a>.
<li><a href=”#expiration-time”>Expiration time</a></li>
<li><a href=”#invalidation-methods”>Invalidation methods</a></li>
<li><a href=”#uri-rejection”>URI rejection</a></li>
<li><a href=”#faq”>Frequently Asked Questions</a></li>
If you choosed to use Hyper Cache and are satisfied do a check of the advantages or the money saving it brings to you and consider to donate something: that will help me to continue the Hyper Cache developement.  <a href=”https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&amp;hosted_button_id=2595746″><img class=”alignnone” title=”Donate” src=”/english/images/paypal.gif” alt=”” width=”92″ height=”26″ /></a> Thank you!  <a name=”expiration-time”></a>
<h2>Expiration time</h2>
<strong>What means “expire a cached page after X minutes” and what’s the best value?</strong> Hyper Cache stores an html page in it’s repository. On each reaquest for a page, Hyper Cache checks how much old that page is. If the cached page is older than the X time (in minutes) specified, that page is not served by Hyper Cache, but “re-created” by WordPress (like if a cache system was not here). Hyper Cache then restores the generated page.  I use 1440 minutes for my pages (one day), but remeber that a page can be cleared on special events (like comment or modification by the blog owner). You can specify a zero value to avoid any kind of cache expiration.  Why it’s better to expire a page (even with a long time)? Because a page is not only the article text, but there are other information, like categories list with posts numbers, latest comment list, latest posts list and so on. With new content, new comments, those lists becomes “old”.  <a name=”invalidation-methods”></a>
<h2>Invalidation methods, what’s the best?</h2>
There is not a best method, it all depends on your needs.  <strong>Method “all”</strong>. If you need a really coherent and updated blog, you can choose the method “all”: each action on posts (eg. edit), new comment submission and so on leads to a complete cache invalidation. But it’s the more expensive (for your blog, not for the cache).  Remember that Hyper Cache (at now) doesn’t intercept the blogroll modification or the theme change. For the latter there are good reasons. So if you plan to make big modification to the blog, manually invalidate the cache.  <strong>Method “single page”</strong>. With this method, Hyper Cache invalidate only the cached page of a post modified (with the editor or when a new comment is added to it). The home page is invalidated too just to keep it coherent. But all the cache will be cleared if a post change it’s status from unpublished to published or from published to unpublished. That behaviour keeps all the blog pages updated (no links to article no more active or missing links to article just published).  <strong>Method “single page strictly”</strong>. I was asked to invalidate only and only tha cache page of a post when it is modified (even for a status change as explained), because there was no interest on having all the page perfectly updated.  <strong>Method “none”</strong>. The cache is never invalidated whatever action will be made (new comments, new posts, editing, and so on). This method can be good if you do very little modification to your blog. Obviously tha cache still respects the expiration time.  <a name=”uri-rejection”></a>
<h2>URI rejection and matching criteria</h2>
There are times when a page or a post has to be served always from WordPress. Given the URI (URI is the right word) of that post, it can be added to the url to reject textarea.  Let’s go with an example. You have a special page that has not to be cache, let it to be under the URI “/special-page”. So, enter that URI in the textarea <strong>without</strong> quotes. The matching criteria is “if the current URI <strong>starts</strong> with one of the specified, just skip the caching system”.  Read the criteria, you can use the partial URI “/special” and the special page will be still rejected.  <strong>What about if I need to reject a page with URI “/special” but cache the page with URI “/special-page”?</strong> Simply write the URI to reject surrounded <strong>with</strong> double quotes: “/special”. Hyper Cache will match exactly that page.  <a name=”faq”></a>
<strong>The options panel is saying my installation has problems!</strong> Deactivate and reactivate the plugin: some files need to be rewritten. Then **re-save** the configuration even if you didn’t make changes.  <strong>Why have I to use Hyper Cache and not other cache systems?</strong> I really cannot answer that question, but I wrote Hyper Cache to have an easly to install and crontrol cache system for WordPress that make me happy with a 4000 page views/day blog and a 12$/year hosting provider. Enough?  <strong>Where are the cache pages?</strong> In to the folder /wp-content/hyper-cache: if you empty that directory the cache starts from zero.  <strong>Why have I to donate? And how?</strong> There is chances that if you are using Hyper Cache you are saving a lot of money keeping you site in a cheap provider. This can be a reason. Or just because you find me a cool programmer and want me to keep in developing Hyper Cache and eating two times a day :-). Or…  <a href=”https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&amp;hosted_button_id=2595746″><img class=”alignnone” title=”Donate” src=”/english/images/paypal.gif” alt=”” width=”92″ height=”26″ /></a> Thank you!

219 thoughts on “Hyper Cache

  1. Should the message go away once I do this?
    You must add to the file wp-config.php (after the define(‘WPLANG’, ”);) the line of code: define(‘WP_CACHE’, true);.

    I updated my wp-config file and still see the message. And I am unable to verify if it’s working on my site.

  2. Hey, is there any way to invalidate a single post if a new comment is added? At the moment, a comment will only shop up once the cached post has expired or if I clean the cache manually

      1. So the problem isn’t with hypercache, it’s with the fact that the site in question uses a pair of load balanced web servers that don’t share storage – ie they each have their own hypercache created wp-content/cache folder.

        So, one server (the one the user connected to when leaving the comment) was invalidating the page (I assume by deleting it from the cache folder), but the other server wasn’t and displaying the old page.

        Don’t think there’s much you can do about this, – but this might be useful in case anyone else experiences the same problem. Thanks for your reply, anyway.

        1. The only thing that can be done is a intra caches communication… It’s a thing that can be developed easy (I did it on other systems). There are no other solutions I think…

    1. Browser caching has nothing to do with my plugin, which caches page at server side. Try to enable the browser caching in the options panel: that sends a commend to the browser to keep the pages in its local cache. Pay attention, that means users can get and keep old pages until the browser decide to reload them. More, check the notice you have from gtmetrix: on which resources it says to enable the browser caching?

  3. Hi there,

    is it possible to clear the cache with a real cronjob? Cause I need to clear the cache at a certain time eg. 1am… How can I do this with hypercache?

    1. I was thinking something similar, but then I realised that if a page has expired it will get rebuilt when that page is next visited, and I can’t see any harm in leaving the expired pages there, as they will get replaced when the time comes.

      If you don’t actually need to delete them, it might be simpler to just leave them be.

      1. Thanks for your reply. Let me describe my case:

        – no comments or something similiar on the site
        But my problem is the self build upcoming events widget on every page. The cache only needs to be cleared when an event is over or when a post/page/cpt changes. But this widget is just a query so it is not able to start the cache rebuild.

        So in some cases, if a page is cached before midnight it shows an “old upcoming event” until the cache expired. And I dont want to set the expire time to 4 or 6 hours to keep them nearly fresh all the time. Best for me, cache 24 hours, clear cache at midnight so every page shows the correct upcoming events.

        Sorry for my english ;)

  4. Our server is horribly slow with WordPress, but Hyper-cache serves up cached pages almost instantly.

    One problem though, in the footer of our pages we have a Twitter feed that shows how many minutes ago each tweet was posted. On cached pages the time does not change and new tweets do not show. The option to “cache feeds” is not set. Is there a way to get feeds like Twitter/Facebook to refresh on a cached page?

    Our site home page is http://www.drapertools.com/news/ if you have time to look and can see if anything is configured incorrectly.

    Our feeds do not usually update fast, so if this can’t be fixed I could set the cache to expire after 30 minutes, but because posts are not expected to change often I was going to set this to 4 hours.

    1. It’s ok, I found the problem!

      The widget our theme uses to add the Twitter Feed to the page Footer is just outputting the HTML for the tweets at the time the page is loaded. There is no script to refresh it, so the caching works perfectly. I will need to make pages expire more frequently.

  5. Hi, Stefano :
    my website is using hyper-cache. but i have a question.
    could i delete one posts from my hyper-cache ??(because there are 1000+ people on my site. if i delete all cache, the website will be broken.)

    i try to find the post hyper-cache number. i into the /wp-content/hyper-cache/cache and delete the file.
    but it dosen’t work. so please help me to delete one post cache (another methods).

    1. My pugin work as is, probably that is another plugin that can be helpful I don’t know. About the error you have I don’t know, I don’t use that library of php on my plugin. Does the error disappears if you disable my plugin?

  6. This plugin is really good. I use it with SwarmCDN and it works without problem – my website loads under 1sec (before over 4sec). I have some ideas how to improve this plugin, maybe some of them would be added in future releases. There is a list:

    1) RSS caching
    2) Add clear link into admin bar (I know, there is a plugin for this, but it would be nice to add this to Hyper cache plugin)
    3) Schedule cache purge – add scheduler
    4) Cache only new content (older post are not cached anymore) – I like this feature from Lite cache
    5) Show total space of cached files in the settings (next to the page cached)
    6) Is https/http combination supported?

    Thank you again, I am looking for new version ;)

  7. First: great plugin, love this.

    I was wondering though; is it possible to do some sort of hole punching? In other words, not caching specific parts of a page?



    1. No it’s not possible, since the plugin cache the generated HTML. Other plugins have some tricks to not cache part of the page, but I don’t know how they work and more, is that require to load the WP core system, it’s like to not have the cache…

    1. Hi, my plugin DOES not inject any code, any coder can verify it just downloading the plugin source from wordpress.org. So I suggest you to really check you blog for other kind of hacks. Really.

      More, please instead of state that the plugin injects something (it’s so used and from so much time that this problem would be reported time ago), let me, if you want, to help you in finding the problem.

      The furst step is to delete the plugin to be sure it was not infected and reinstall it.

  8. Excelente plugin, trabaja bien , de lo mejor que he probado. Gracias amigo y buen verano.

    Excelent plugin, works fine, better plugin that I installed. Thanks and good summer my friend.

    Please update for ever, thanks

  9. Successfully installed hypercache! Thanks for such simple, one-click plugin.
    Also I’ve installed another plugin which re-generates hypercache every 24 hours. All pages which are expired from hypercache are re-generated and again kept in hypercache.

    1. Restore the original wp-config.php (remove the line you added) and eventually remove the file “wp-content/advanced-cache.php”. But the problem is surely the modification of the wp-config.php. Do not copy the copy in the page since the single quotes are not valid: write if by hand.

      1. I read somewhere: “If it does not add the code above then you have to add it manually. This code is needed for the plugin to work.”

        Probably I misunderstood you.

        I thought I had to add this line of code manually ANYWAY. But it does n’t seem the case anymore? Only in exceptional cases?

        1. Carefully skipped the line and replaced the config-file, and subsequently removed the advanced-cache file, but the problem is still a blank WordPress-page with HTTP-error 500 (Internal Server Error).
          Uninstall WordPress and install again?

          1. Hi, I need and FTP access to the blog and the blog address to find out the problem. As I asked before, try to send me the wp-config.php: if it’s the only file you changed probably it’s a matter to adjust it.

  10. Help! My server is centos + nginx + php5.3. Is there any problem with this environment? The Cleaning process time of hyper cache is always the time of activate the plugin plus 5 minutes. It never changed unless I reactivate the plugin.

  11. I installed W3TC and had many problems. Now I uninstalled HyperCache to use, but I can not remove the folder from the server cache. How do I do that? My Server is: Linux!

  12. I wrote about my issue of using different style for different broser using php. I got the fix by javascript. Now I can use this plugin :-)

    function hello(){
    var browserName=navigator.appName;

    if (browserName=="Microsoft Internet Explorer")
    document.getElementById("demo").innerHTML="It works well when

    h1 is style for IE”;
    document.getElementById(“dynamicstyle”).innerHTML=”It works well when

    h2 is style for non-IE”;


    Default Text

  13. sounds very simple and logical for caching. I guess I can do and still have dynamic nature of my post (with delay of 24 hrs) – that is no issue.
    Please answer this:
    I have different fixes for different browser. (few issues with styles so I dynamically change style in php code for browsers such as if(is_IE) use_style_IE else use_style_all). Is there any way this plugin creates browser specific cached files and serve accordingly.
    Please give a fix/answer asap – thanks

  14. Dear can u help as i install, but i think home page cache is active, or site indexing in Google almost after in 24 hours daily as Cached pages timeout was set 1440 .
    So what i do for this that Google index posts as posts write.

    Also i will check option :-
    Home caching
    DO NOT cache the home page so it is always fresh.

    or not checked. for home page not cache.?


  15. Hyper Cache is awesome… Thanks so much for it.

    I also have “Better WordPress Minify” installed, it was installed before HyperCache.

    Should I disable this minify plugin now? Does Hyper Cache take care of this function?

    Ane one more question.
    I also installed “DB Cache Reloaded Fix” with Hyper Cache but the testing I performed returned slower results with the two installed. So I disabled DB Cache.

    I know results will vary.. but any general comments on above?

    Thanks again for Hyper Cache, its blown away everything I’ve tried.

  16. Hello,
    Just installed the plugin. Now i have access only to the home page but all other links from home page return a 404 (from the host, not WP).
    Within WP admin, when I want to preview a page, I also have 404 errors (from webhost, not WP)
    My install is a WP 3.2.1 in French with a specific theme.
    The define is installed in WP-config.
    Strange though, the cache folder is /wp-content/cache/hyper-cache/”cachefile”

    Please help…


  17. hey great plugin, can you consider a clear cache button at the top of the admin bar, so we dont have to dig into the plug to refresh, i think one of the other cache plugins did that.

  18. Actually installing the plugins under load considerably,
    which is good, however there were serious problems on my site.
    1 .- In Google Chrome updated my page appears.
    2 .- Morzilla my home page appears with old posts.
    3 .- The worst, The Posts do not appear in Google is that search engines do not detect my “New Post”
    Please could give me a solution.

    my email is:

  19. just wanted to know how to enable homepage caching. The option say “home caching” but the description says “DO NOT cache the home page so it is always fresh.”

    Should i check it or uncheck it? i need homepage caching

Leave a Reply