Franky

<p><strong>Images Sync for Cloudflare</strong> automatically uploads your WordPress images to Cloudflare Images and stores optimized delivery URLs directly in post meta. Perfect for headless setups, JAMstack sites, or anyone who wants fast, globally-distributed images without changing their workflow.</p>
<h4>Why Use This Plugin?</h4>
<p>Headless frontends need stable, cacheable CDN URLs. This plugin makes WordPress the source of truth while Cloudflare Images handles delivery and optimization. No custom resolvers needed — just query the meta field.</p>
<h4>Features</h4>
<ul>
<li><strong>Flexible Mappings</strong> — Map any image source (Featured Image, ACF fields, post meta) to Cloudflare Images with customizable delivery URL storage</li>
<li><strong>Preset System</strong> — Define reusable presets for OG images, thumbnails, heroes, squares — consistent URLs across your site</li>
<li><strong>Preview Studio</strong> — Visually test how images look with different presets before going live</li>
<li><strong>Auto-Sync</strong> — Images sync automatically on post save, or bulk-process existing content via Action Scheduler</li>
<li><strong>Flexible Variants</strong> — Smart detection prevents broken images and 9429 errors</li>
<li><strong>Headless-Ready</strong> — URLs stored in post meta, perfect for GraphQL/REST API consumption</li>
<li><strong>WP-CLI Support</strong> — <code>wp cfimg sync</code> commands for scripted workflows</li>
<li><strong>Secure Storage</strong> — API token encrypted with libsodium (AES-256 fallback)</li>
<li><strong>No Lock-in</strong> — Your images stay in WordPress Media Library; Cloudflare URLs are plain meta values</li>
</ul>
<h4>Security</h4>
<p>Your Cloudflare API token is encrypted at rest using modern cryptography (libsodium or AES-256-CBC with HMAC). The token is never stored in plain text and is only decrypted when making API requests.</p>
<h4>Requirements</h4>
<ul>
<li>Cloudflare account with <a href="https://www.cloudflare.com/products/cloudflare-images/" rel="nofollow ugc">Cloudflare Images</a> subscription</li>
<li>API Token with “Cloudflare Images: Edit” permission</li>
</ul>
<h3>External services</h3>
<p>This plugin optionally connects to external Cloudflare services to upload, manage, and deliver images. No connection is made until the user configures API credentials and explicitly triggers a sync, test, or preview action.</p>
<h4>Cloudflare Images API</h4>
<p>This plugin sends requests to the <a href="https://api.cloudflare.com/" rel="nofollow ugc">Cloudflare API</a> (<code>api.cloudflare.com</code>).</p>
<p>Data sent to Cloudflare (only when the user configures credentials and triggers actions):</p>
<ul>
<li>API token — for authentication (sent as a Bearer token header, never logged or stored in plain text)</li>
<li>Image files — binary content of WordPress media attachments</li>
<li>Image metadata — WordPress attachment ID and a purpose label (e.g. “preview”)</li>
<li>
<p>Configuration updates — Flexible Variants enable/disable flag</p>
</li>
<li>
<p><a href="https://www.cloudflare.com/terms/" rel="nofollow ugc">Cloudflare Terms of Service</a></p>
</li>
<li><a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare Privacy Policy</a></li>
<li><a href="https://developers.cloudflare.com/api/" rel="nofollow ugc">Cloudflare API Documentation</a></li>
</ul>
<h4>Cloudflare Image Delivery</h4>
<p>Delivery URLs use the <a href="https://imagedelivery.net/" rel="nofollow ugc">Cloudflare Image Delivery</a> CDN (<code>imagedelivery.net</code>). These URLs are stored in post meta and served directly to site visitors by their browsers. The plugin itself makes one request to this service to detect Flexible Variants support (canary check).</p>
<p>No visitor data, IP addresses, cookies, or personal information is ever sent to Cloudflare by this plugin.</p>
<ul>
<li><a href="https://www.cloudflare.com/terms/" rel="nofollow ugc">Cloudflare Terms of Service</a></li>
<li><a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare Privacy Policy</a></li>
<li><a href="https://developers.cloudflare.com/images/" rel="nofollow ugc">Cloudflare Images Documentation</a></li>
</ul>
<h3>Privacy Policy</h3>
<p>This plugin does not collect, store, or transmit any personal user data. Only image files and technical metadata (attachment IDs, image hashes) are sent to Cloudflare.</p>
<h3>Credits</h3>
<p>Developed by <a href="https://301.st" rel="nofollow ugc">301st</a> with <a href="https://claude.ai" rel="nofollow ugc">Claude AI</a>.</p>


Images Sync for Cloudflare

Auto-sync WordPress images to Cloudflare Images. Stores optimized CDN URLs in post meta — ready for headless, ACF, or classic themes.

Benjamin Intal

gambitph

<p>Using WordPress entirely as a CMS (a <a href="https://medium.com/@jchiatt/headless-wordpress-with-react-d573bca02ee0" rel="nofollow ugc">Headless WordPress</a>) is a plausible option for people building web apps using technologies such as React JS or Angular JS to entirely build their front-end.</p>
<p>Doing this, the front-end (e.g. built with React) becomes decoupled from the back-end (e.g. WordPress). Since WordPress is being used strictly to manage and serve the content via REST API, the WP front-end becomes unusable and unnecessary – hence the term <em>“headless WordPress”</em>.</p>
<p><strong>This plugin essentially removes the front-end of WordPress.</strong></p>
<blockquote>
<p>Note that the REST API, and other non-front-end stuff should work as normal.</p>
</blockquote>
<h4>Features</h4>
<ul>
<li>No settings page</li>
<li>Allows backend access</li>
<li>Allows REST API endpoints</li>
<li>Redirects (403 Forbidden) all front-end pages to the login page</li>
</ul>


Redirect Front-end to Login | Headless WP

Redirects all front-end pages to the login page, best for building a headless WP REST API backend

Images Sync for Cloudflare vs Redirect Front-end to Login | Headless WP