Hosting Compatibility

WP Rocket is compatible with 99% of hosts.  Due to the specifics of some hosting platforms, there may be some particular considerations. If you come across a hosting company that wants you to remove WP Rocket, please let us know so that we can contact them directly to become compatible.

Note: If your hosting company is not listed here, it doesn’t mean their hosting is not compatible with WP Rocket. Quite the opposite, in most cases it will mean WP Rocket works just fine on their hosting environments, so there isn’t anything to be pointed out about them in this document.

In this article

DreamPress

  • WP Rocket is automatically compatible with DreamHost's DreamPress platform:
  • Page caching is automatically disabled, but all other optimizations will still be applied
  • Varnish add-on is auto-enabled and will keep the cache clearing synchronized
  • HTML expires rule is removed from htaccess to allow for proxy caching

GoDaddy

Flywheel

  • Page caching is automatically disabled on Flywheel, but all other optimizations will still be applied.
  • To use WP Rocket, you must turn on Enable WP_CACHE  from the Advanced tab of your Flywheel site card dashboard:

  • If you want to use Flywheel's CDN and WP Rocket's file minification, retrieve your unique Flywheel CDN domain from your website’s source code, or ask Flywheel’s support about it. Then enter your CDN domain in the CNAME field on WP Rocket’s CDN settings panel, and activate the checkbox “Enable Content Delivery Network” on the same panel.
  • WP Rocket automatically detects if you use Flywheel and auto-purges their Varnish caching when your WP Rocket cache is purged. 

Hostgator Managed WordPress Hosting

  • WP Rocket is now allowed on their system :)

RunCloud

  • RunCloud is technically a server management panel rather than a host. But they added compatibility to their RunCloud Hub plugin to ensure that cache purging is synchronized.

Savvii

  • WP Rocket is compatible with Savvii hosting.
  • Our page cache is disabled but all other features will work. 
  • Cache purging is synchronized between WP Rocket and Savvii's cache.

Siteground

SpinupWP

  • WP Rocket is compatible with Spinup hosting.
  • Our page cache is disabled but all other features will work. 
  • Cache purging is synchronized between WP Rocket and Spinup's cache.

Synthesis

  • W3 Total Cache is pre-installed, but you can delete it and install WP Rocket instead, with no problems. 

WP Engine

  • WP Rocket is the only caching plugin that is allowed on their system. We worked closely with their team to meet their requirements. 
  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with WP Engine's caching. All other features such as LazyLoad, minification etc. are available.
  • WP Rocket automatically detects if you use WP Engine and auto-purge their Varnish caching when your WP Rocket cache is purged. 
  • WP Rocket will automatically be allowed on your staging site even if you have a Single license. Staging won't count as an additional site.
  • If you are using WP Engine's CDN service, you still have to enable the CDN option in WP Rocket, and enter your CDN URL so the plugin can detect it and function correctly. If you're not sure what your CDN URL is, you can find it by following the instructions in WP Engine's doc.
  • WP Engine has deprecated the use of the htaccess file. They apply those related optimizations in their server configuration instead. WP Rocket does not require the use of the htaccess file on WP Engine - all features will still work as expected.
  • WP Rocket will not create an advanced-cache.php file on WP Engine sites.

Kinsta

  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with Kinsta’s caching. All other features such as LazyLoad, file optimization, etc. are available.
  • If you are using Kinsta's CDN service, they will handle the CDN setup for you, but you still have to enable the CDN option in WP Rocket and enter your unique Kinsta CDN domain, so our plugin can detect it and function correctly. You can find your unique Kinsta CDN domain from the CDN tab in your Kinsta account.

Amazon Lightsail (Bitnami)

  • In Bitnami environments, the .htaccess file may not be available for WP Rocket to work automatically. To resolve, use the helper plugin below to disable the use of the .htaccess file for those environments:

    📥  Download (.zip): WP Rocket | No .htaccess
    Developers: You can find the code for this plugin on GitHub.

  • The Bitnami stack has PageSpeed Module (mod_pagespeed) enabled by default. It needs to be disabled to avoid conflicts with WP Rocket. To disable it, please follow the steps provided in this Bitnami documentation: Disable PageSpeed

WordPress.com

  • WP Rocket is the only caching plugin allowed on sites hosted at WordPress.com.
  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with WordPress.com’s caching. All other features such as LazyLoad, file optimization, etc. are available.
  • WP Rocket can only be installed and used If you have a Business or eCommerce plan. If you have a Personal or Premium plan you’re not allowed to install WP Rocket nor any other plugin on your site(s).
  • We recommend disabling the Page Optimize plugin to prevent conflicts with WP Rocket.

Pressable

  • The page caching feature of WP Rocket is automatically disabled to prevent conflict with Pressable's caching. 
  • All other features such as LazyLoad, file optimization, etc. are available.

RAIDBOXES

  • WP Rocket is compatible with RAIDBOXES. However, you must first deactivate the server-side cache of RAIDBOXES in the settings of your box, if you want to use WP Rocket.
    RAIDBOXES-Cache deaktivieren
  • Alternatively, you can use RAIDBOXES' caching system and disable WP Rocket's Cache.
  • When you turn off WP Rocket, you'll see a warning that certain entries in the wp-config.php cannot be changed. That's the case with RAIDBOXES. Just click the Force Disabling link in the alert.

Pantheon

The permissions restrictions can be bypassed when one of the following alternatives is implemented:
  • Creating a symlink for the advanced-cache.php file and manually creating the file in the uploads folder. Please see this article for more info. 
  • Customizing the cache folder and config file as shown in this article.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.