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.

Jason Bahl

<p>WPGraphQL for Advanced Custom Fields is a free, open-source WordPress plugin that adds ACF Fields and Field Groups to the WPGraphQL Schema.</p>
<h4>Create ACF Field Groups</h4>
<p>Create ACF Field Groups and Fields using the ACF User Interface, register them with PHP, or leverage ACF local JSON. Each field group and the fields within it can be configured to “Show in GraphQL.”</p>
<h4>Query your fields with GraphQL</h4>
<p>Once your field groups and fields are configured to “Show in GraphQL,” they become available in the GraphQL Schema for querying.</p>
<h4>Supported Field Types</h4>
<p>WPGraphQL for ACF provides support for most built-in field types of ACF (free & PRO) and extends support to most field types from ACF Extended (free & PRO).</p>
<h3>Updating</h3>
<p>If you are updating from WPGraphQL for ACF v0.6.* or older, check out the <a href="https://acf.wpgraphql.com/upgrade-guide" rel="nofollow ugc">Upgrade Guide</a></p>
<p>For non-major version updates, automatic updates usually should work smoothly, but we still recommend you back up your site and test on a staging site.</p>
<p>Before updating WPGraphQL for ACF, review the release notes on <a href="https://github.com/wp-graphql/wpgraphql-acf/releases" rel="nofollow ugc">GitHub</a>.</p>
<p>We follow Semantic Versioning (Semver) for meaningful releases:</p>
<ul>
<li><em>MAJOR</em> version for incompatible API changes,</li>
<li><em>MINOR</em> version for backwards-compatible functionality additions,</li>
<li><em>PATCH</em> version for backwards-compatible bug fixes.</li>
</ul>
<p>Learn more about Semver at <a href="https://semver.org" rel="nofollow ugc">semver.org</a>.</p>
<h3>Support</h3>
<ul>
<li><a href="https://github.com/wp-graphql/wp-graphql/discussions" rel="nofollow ugc">General Help Requests</a>: For general questions and help requests, create a new topic in Github Discussions</li>
<li><a href="https://www.wpgraphql.com/discord" rel="nofollow ugc">Discord Community</a>: The WPGraphQL Discord is a great place to communicate in real-time. Ask questions, discuss features, get to know other folks using WPGraphQL.</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/issues/new?assignees=&labels=&projects=&template=bug_report.yml" rel="nofollow ugc">Bug Reports</a>: Report a bug in WPGraphQL</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/issues/new?assignees=&labels=&projects=&template=feature_request.yml" rel="nofollow ugc">Feature Requests</a>: Suggest an idea, feature, or enhancement for WPGraphQL.</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/security/advisories/new" rel="nofollow ugc">Report a Security Vulnerability</a>: Report a security vulnerability.</li>
</ul>
<h3>FAQs</h3>
<p><strong>Does this work with ACF Extended?</strong></p>
<p>Yes! WPGraphQL for ACF allows you to query for (most) fields created with ACF Extended.</p>
<p><strong>Can I filter and sort queries by ACF Fields using WPGraphQL for ACF?</strong></p>
<p>At this time WPGraphQL for ACF does not support filtering or sorting queries by ACF Fields. “Meta Queries” are often very expensive to execute, so we currently do not support filtering by ACF fields out of the box, but are exploring options for supporting it without the performance penalty.</p>
<p><strong>I think I found a bug, where do I report it?</strong></p>
<p>If you think you found a bug, please open an issue on <a href="https://github.com/wp-graphql/wpgraphql-acf" rel="nofollow ugc">GitHub</a>. The more details you provide in the issue, and the more clear your steps to reproduce are, the higher chances we will be able to help.</p>
<p><strong>Can I use ACF Free or Pro with WPGraphQL for ACF?</strong></p>
<p>Yes! WPGraphQL for ACF works great with ACF Free and Pro. The Pro version of ACF has some additional features, such as Flexible Content Fields, Repeater Fields and Options Pages that are supported by WPGraphQL for ACF.</p>
<p><strong>Do I have to use Faust.js to use WPGraphQL for ACF?</strong></p>
<p>No! While <a href="https://www.wpgraphql.com" rel="nofollow ugc">wpgraphql.com</a> and <a href="https://acf.wpgraphql.com" rel="nofollow ugc">acf.wpgraphql.com</a> are built using <a href="https://faustjs.org/" rel="nofollow ugc">Faust.js</a> and Next.js, you can use WPGraphQL for ACF with any GraphQL client, including Apollo, Relay, Urql, etc.</p>
<p><strong>I have an ACF Extension that adds a new field type, will it work with WPGraphQL for ACF?</strong></p>
<p>WPGraphQL for ACF supports the field types that come with ACF (Free and PRO) as well as the field types in ACF Extended (Free and PRO). Support for additional field types can be added by using the “register_graphql_acf_field_type” API.</p>
<p><strong>Do I need WPGraphQL and ACF to be active to use this?</strong></p>
<p>This plugin is a “bridge” plugin that brings functionality of ACF to WPGraphQL. Both WPGraphQL and ACF need to be installed and active in your WordPress installation for this plugin to work.</p>
<p><strong>How much does WPGraphQL for ACF cost?</strong></p>
<p>WPGraphQL for ACF is a FREE open-source plugin. The development is sponsored by <a href="https://wpengine.com/atlas" rel="nofollow ugc">WP Engine Atlas</a>.</p>
<p><strong>Does WPGraphQL for ACF support GraphQL Mutations?</strong></p>
<p>GraphQL Mutations are not yet supported. We are working on adding support for Mutations in the future. We are waiting for the GraphQL “@oneOf” directive to be merged into the GraphQL spec before we add support for Mutations.</p>
<p><strong>Does this work with Field Groups registered in PHP or JSON?</strong></p>
<p>Yes! You can register ACF Field Groups and Fields using the Admin UI, PHP or JSON. WPGraphQL for ACF will detect the Field Groups and Fields and add them to the GraphQL Schema. If using PHP or JSON, you will need to set the “show_in_graphql” setting to “true” to expose the Field Group and Fields to the GraphQL Schema. There might be other settings that need attention at the field group or field level that might impact the schema or field resolution.</p>
<h3>Privacy Policy</h3>
<p>WPGraphQL for Advanced Custom Fields uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect telemetry data upon user confirmation, helping us troubleshoot problems and improve the product.</p>
<p>The Appsero SDK <strong>doesn’t collect data by default</strong> and only starts gathering basic telemetry data when a user allows it via the admin notice. No data is collected without user consent.</p>
<p>Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses data</a>.</p>


WPGraphQL for ACF

WPGraphQL for ACF seamlessly integrates Advanced Custom Fields with WPGraphQL.

Images Sync for Cloudflare vs WPGraphQL for ACF