kryptonmediagroup

<p>Cyclone Static generates fully-rendered static HTML files for every page on your WordPress site and instructs Apache to serve them directly — bypassing PHP, WordPress, and the database for anonymous visitors.</p>
<p>When a static file exists for a requested URL, Apache reads it from disk and sends it without starting PHP or querying the database. The visitor receives a complete HTML page. Their browser runs your JavaScript, plays your audio, renders your animations — everything works as it did before, because the static file contains the same HTML WordPress would have generated.</p>
<p>Logged-in users, POST requests, query strings, and administrative paths bypass the static cache and receive live WordPress as normal.</p>
<h4>Key features</h4>
<ul>
<li><strong>Static file serving</strong> — Apache serves files directly from disk. PHP and the database are not involved in serving anonymous page requests.</li>
<li><strong>Automatic regeneration</strong> — When you publish or update a post or page, it is automatically queued for regeneration. You do not need to do anything.</li>
<li><strong>Reduced attack surface</strong> — Static HTML files do not execute PHP or query a database. Common WordPress-targeted attack vectors that require a live PHP process — such as SQL injection via PHP, PHP code execution, and xmlrpc.php abuse — do not apply to anonymous page requests served as static files.</li>
<li><strong>CDN integration</strong> — Works alongside W3 Total Cache. Direct integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.</li>
<li><strong>W3 Total Cache compatible</strong> — Installs its .htaccess rules before W3TC rules. Works alongside or without W3TC.</li>
<li><strong>Non-destructive</strong> — Deactivating the plugin removes the .htaccess rules and WordPress resumes normal operation. Your cached files are not deleted without your explicit consent — a prompt appears when you deactivate, asking whether to keep or delete them.</li>
<li><strong>Free and open</strong> — No license required. Support via the WordPress.org community forums.</li>
</ul>
<h4>System requirements</h4>
<ul>
<li>WordPress 6.0 or later</li>
<li>PHP 8.0 or later</li>
<li><strong>Apache web server</strong> with mod_rewrite enabled</li>
<li>.htaccess support enabled (AllowOverride All or equivalent)</li>
<li>WordPress Multisite is not supported in this version — Multisite support is available in Cyclone Static Pro</li>
</ul>
<p><strong>Nginx users:</strong> Cyclone Static manages .htaccess automatically on Apache. If your server runs Nginx, the Settings page includes a ready-to-paste Nginx server block under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Nginx Configuration</strong>.</p>
<h4>CDN support</h4>
<p>The free version works automatically alongside W3 Total Cache — CDN purges are routed through W3TC when it is active.</p>
<p>Direct API integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.</p>
<h4>Privacy</h4>
<p>Cyclone Static does not collect, transmit, or store any personal data. The queue table stores only URLs. No external service is contacted except the CDN purge APIs you explicitly configure.</p>
<h3>Support</h3>
<p>Support is provided via the WordPress.org community forums. Post your question there — answers are public, so search first as your question may already be answered. For private inquiries, you can reach us at support@kryptonmediagroup.com. Confirmed bugs are addressed through plugin updates. Private one-on-one support is not offered via the forums.</p>
<h3>External Services</h3>
<p>Cyclone Static can optionally connect to the following third-party services to purge cached content from your CDN. These connections are only made when you configure a CDN provider under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> CDN Integration</strong> and a purge is triggered. No data is sent to these services unless you explicitly configure them.</p>
<h4>Bunny.net</h4>
<p>Used for CDN cache purging. Your Bunny.net API key and Pull Zone ID are sent to the Bunny.net API.<br />
* Service: https://bunny.net/<br />
* API documentation: https://docs.bunny.net/reference/purgepublicpullzone<br />
* Privacy policy: https://bunny.net/privacy/</p>
<h4>Cloudflare</h4>
<p>Used for CDN cache purging. Your Cloudflare API token and Zone ID are sent to the Cloudflare API.<br />
* Service: https://www.cloudflare.com/<br />
* API documentation: https://developers.cloudflare.com/api/resources/cache/methods/purge/<br />
* Privacy policy: https://www.cloudflare.com/privacypolicy/</p>
<h4>KeyCDN</h4>
<p>Used for CDN cache purging. Your KeyCDN API key and Zone ID are sent to the KeyCDN API.<br />
* Service: https://www.keycdn.com/<br />
* API documentation: https://www.keycdn.com/api<br />
* Privacy policy: https://www.keycdn.com/privacy</p>
<h4>Amazon CloudFront</h4>
<p>Used for CDN cache invalidation. Your AWS Access Key, Secret Key, and CloudFront Distribution ID are sent to the Amazon CloudFront API.<br />
* Service: https://aws.amazon.com/cloudfront/<br />
* API documentation: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CreateInvalidation.html<br />
* Privacy policy: https://aws.amazon.com/privacy/</p>


Cyclone Static

Serve static HTML files directly from disk — no PHP, no database queries for anonymous visitors.

PiotrPress

Clearcode

<p>The CC-Cache plugin supports caching of Posts, Pages, and any public Custom Post Types – including single and archive pages.<br />
It also supports a “static page display” option: Front page, Posts page, and standard Latest Posts listing.<br />
This plugin is compatible with Multisite WordPress installations.</p>
<h4>How does it work?</h4>
<p>When a user (i.e. someone who is logged out of WordPress) opens a page for the first time, the plugin saves all the rendered html to a file in the wp-content/cache directory.<br />
From this moment onwards, any user who accesses the site will be served content directly from the generated html file. WordPress at this point is not initialized for this page.<br />
The generated cache file will be removed when you make changes to the corresponding Post/Page, and then the process starts from the beginning.<br />
You can also clear all cached files from the Cache options page (visit the ‘Settings > Cache’ page in wp-admin), or manually delete files from the wp-content/cache directory.</p>
<h4>Tips & Tricks</h4>
<p>You can check if a page’s content is served from a cache file by opening the page’s source code in the browser and scrolling down to the closing <code><body></code> html tag.<br />
If the content is cached, you should see a comment with the date and time the page was last cached, for example:<br />
    </p>
<p>You can disable cache for a single request and get the raw html by adding <code>cache=false</code> to a URL’s parameter, for example:<br />
    http://example.com/?cache=false</p>
<p>You can disable cache for a single request and get the raw html by adding <code>cache=false</code> HTTP header.</p>
<p>Logged-in users always get the raw html.</p>
<h4>Ideas for future versions</h4>
<ol>
<li>Add support for Categories, Tags, Taxonomies, and Authors.</li>
<li>Add support for RSS/Atom feeds.</li>
<li>Add support for Nginx and IIS servers.</li>
<li>Add support for other WordPress Filesystem Methods.</li>
<li>Add regenerate function for all cache files.</li>
</ol>
<h3>Requirements</h3>
<ol>
<li>Apache server</li>
<li>mod_rewrite</li>
<li>Write access to wp-content/cache directory</li>
<li>PHP interpreter version >= 5.3</li>
</ol>

CC-Cache

A simple and fast cache plugin based on static-rendered html files served by Apache with mod_rewrite.

Cyclone Static vs CC-Cache