Cyclone Static

Yes. Cyclone Static captures the fully-rendered HTML output of each page as WordPress and your page builder produce it, including all JavaScript and CSS references. The static file closely matches what a live WordPress request would produce.

No. Logged-in users bypass the static cache and receive live WordPress. Divi’s visual builder, preview functions, and WordPress admin features work as before.

Deactivation removes the Cyclone Static block from .htaccess — Apache falls through to WordPress for all requests. A prompt appears asking what to do with your cached files: Keep cache files (recommended if you plan to reactivate — files are served again immediately upon reactivation) or Delete cache files (removes them from disk now). If you dismiss the prompt without choosing, your files are kept.

Deleting the plugin removes the .htaccess rules, drops the queue database table, and removes plugin settings. Your cached files are only deleted if you chose Delete cache files when you deactivated — if you chose to keep them or never saw the prompt, they remain on disk at their original location.

Yes. Cyclone Static installs its .htaccess rules before W3TC rules, so static files are served by Apache before W3TC is consulted. CDN purges are routed through W3TC automatically when it is active.

Yes, but you must follow the safe removal procedure. See the Removing W3 Total Cache guide in the collapsible section on the Cyclone Settings page. Removing W3TC without preparation can break your site’s styles and scripts.

The free version works behind Cloudflare without any special configuration — Cloudflare will cache and serve your static files as normal, and its CDN cache will refresh as files expire or are manually purged from the Cloudflare dashboard. Direct Cloudflare cache purging via API is available in Cyclone Static Pro.

Yes, with manual configuration. Cyclone Static manages .htaccess automatically on Apache but cannot write Nginx config files. The Settings page includes a ready-to-paste Nginx server block under Settings → Nginx Configuration . Copy that snippet into your site’s server block before the location block that passes requests to PHP-FPM.

Yes, when the php-brotli extension is installed on your server. Cyclone Static automatically generates a pre-compressed index.html.br alongside the standard index.html.gz for every cached page. Apache serves the best variant the browser supports — Brotli first, then gzip, then uncompressed. If php-brotli is not installed, gzip and uncompressed files are generated as normal with no configuration required.

When a new comment is posted and approved, Cyclone Static automatically re-queues the parent post for regeneration so the cached page reflects the updated comment count and list. Comments awaiting moderation do not trigger a regeneration — the page is only updated when the comment transitions to approved status.

It depends on the complexity of your pages. A typical WordPress page generates a static file of 50–300 KB. A 4,000-page site would require roughly 200 MB – 1.2 GB. Cyclone Static displays your current cache size and available disk space on the Dashboard.

Cyclone Static can run on WooCommerce sites with manual configuration. Add /cart/, /checkout/, /my-account/, and /wc-api/ to the exclusions list under Settings → Exclusions — this prevents session-sensitive pages from being cached. Product pages cache and serve correctly for anonymous visitors; Add to Cart functions normally via WooCommerce’s AJAX handling. Stock level display may lag until pages regenerate.

No. Multisite support is available in Cyclone Static Pro, distributed from kryptonmediagroup.com/cyclone-static.

Yes — two, and both are intentional. Your site’s root .htaccess receives a single, clearly-delimited block ( # BEGIN Cyclone Static … # END Cyclone Static ) inserted ahead of the WordPress rules; this is what tells Apache to serve a cached file directly when one exists. It is a read-modify-write of your existing file — no other rules are touched — and it is removed automatically when you deactivate the plugin. The cache directory ( wp-content/uploads/cyclone-static/ ) also contains its own small .htaccess , which has no rewrite rules : it only grants Apache permission to serve the cached HTML and its pre-compressed .gz / .br variants and sets the correct Content-Encoding and Content-Type headers on them. It lives alongside your cached files and is removed when the cache is deleted. This is the same pattern used by other caching plugins such as W3 Total Cache and WP Super Cache.