Skip to content

Black Friday 50% off your first year on all premium plugins and the Suite.

See the deals

Install TurboCache

Requirements, installation and exactly what TurboCache changes in wp-config.php, wp-content and .htaccess when you activate it.

2 min read · Updated 5 November 2026

Requirements

  • WordPress 5.8 or later.
  • PHP 7.4 or later.
  • A writable wp-content folder (for the cache and the advanced-cache.php drop-in) and, ideally, a writable wp-config.php.
  • Works on Apache, LiteSpeed and Nginx. On Apache and LiteSpeed rules are written to .htaccess; on Nginx you include a generated snippet yourself.

Optional server extras

None of these are required, but each one unlocks a feature. The CDN and advanced tab shows which ones your server has under Environment.

  • GD or Imagick with WebP support — needed to create WebP copies of images. Without an encoder the WebP checkbox shows “no encoder on this server”.
  • AVIF support in PHP — needed for AVIF copies; otherwise the option shows “not supported by this PHP”.
  • PHP brotli extension — needed for the pre-compressed Brotli copy of each page. gzip works with the standard zlib extension.
  • PHP tidy extension — only for the “Tidy” level of Fix markup.

Install

  1. Download the plugin zip from your account at bytekeel.com.
  2. In WordPress open Plugins → Add New Plugin → Upload Plugin, choose the zip, then Install Now and Activate Plugin.
  3. Deactivate any other page-cache or minification plugin first (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, Autoptimize and similar). Two caches fighting over the same drop-in is the most common cause of trouble.
  4. Add your licence key — see Activate your licence.

What activation changes on your server

A page cache that runs before WordPress needs a few files outside the plugin folder. TurboCache makes these changes for you and undoes them on deactivation:

  • Cache folder — wp-content/cache/turbocache/ is created, with an .htaccess that blocks PHP execution and directory listing inside it.
  • Drop-in — wp-content/advanced-cache.php is copied in. It never overwrites a working drop-in that belongs to another plugin.
  • wp-config.php — if WP_CACHE is not already on, this line is added near the top: define( 'WP_CACHE', true ); // Added by TurboCache.
  • .htaccess (Apache/LiteSpeed) — a block between # BEGIN TurboCache and # END TurboCache with browser-cache headers, pre-compressed file serving and WebP/AVIF negotiation. It is written on the first admin page load after activation.
  • Nginx — the equivalent rules are written to wp-content/cache/turbocache/turbocache-nginx.conf for you to include in your server configuration.

If wp-config.php is not writable, add define( 'WP_CACHE', true ); yourself above the line that says “That’s all, stop editing!”. Until you do, the TurboCache screens show a warning and pages cannot be served before WordPress loads.

Moving the cache folder

To move the cache folder, define a TURBOCACHE_CACHE_DIR constant in wp-config.php (a WPCA_CACHE_DIR constant from the plugin’s former name is still honoured). The page-cache drop-in follows the custom folder, but the optional object cache always uses wp-content/cache/turbocache/, so leave the constant unset if you use the object cache.

Next step

On the very first activation WordPress takes you straight to the setup wizard. Activate your licence first, then follow Setup wizard and recommended settings.

Did this answer the question? No — open a support request