FlyingPress works seamlessly with Cloudflare, including both free and paid plans. Together, they provide powerful frontend optimization and global content delivery—when configured correctly.
No need for CDN URL or API key
Cloudflare is a proxy-based CDN, meaning your site URL itself is the CDN URL.
→ No need to configure a separate CDN URL in FlyingPress.FlyingPress does not require a Cloudflare API key, since it does not need to purge Cloudflare cache directly.
→ Exception: If you're using Cloudflare APO, see below.
Using APO (Automatic Platform Optimization)
If you’re using Cloudflare APO, FlyingPress will automatically purge the APO cache when needed.
You don’t need to enter a Cloudflare API key.
Just make sure the official Cloudflare plugin is active on your site.
No further configuration is required.
Avoid manual full-page caching with Page Rules
Do not use Cloudflare page rules or cache rules to cache HTML/pages manually
→ When purged, Cloudflare will remove everything, including static files like images, CSS, JS, fonts, etc.
→ This hurts your cache hit ratio and is not recommended.
Recommended Cloudflare settings
✅ Enable:
CDN (Proxy ON)
SSL: Full or Full (Strict)
Brotli compression
HTTP/3
❌ Disable:
HTML, CSS, and JS minify in Cloudflare → Let FlyingPress handle minification.
Rocket Loader → May conflict with FlyingPress’s script optimization features.