Module page (https://www.drupal.org/project/cloudflare_purge) says purge by cache tag only works with Enterprise Cloudflare. Looking at https://developers.cloudflare.com/cache/how-to/purge-cache/#availability..., this should be available on free tier too.

Can this module purge by tags on free tier?

Is use of this module viable on CF free tier for a website with dynamic user content and a lot of authenticated traffic?

Comments

klemendev created an issue. See original summary.

flashwebcenter’s picture

Title: Purge by cache tag » Cache tag purging on Cloudflare Free tier
Status: Active » Fixed

Hello,

Great catch. Cloudflare updated their policy in April 2025, and all purge methods (including cache tags, prefixes, and hostnames) are now available on all plans, including the Free tier: https://developers.cloudflare.com/changelog/2025-04-01-purge-for-all/

Can this module purge by tags on the Free tier?
Yes. The module supports cache tag purging on the Free tier.

Is it viable for high-traffic sites with authenticated users?
For Free-tier deployments with heavy traffic:

  • Enable queue processing to batch invalidations via cron.
  • Be selective about which entity types trigger automatic purges.
  • Monitor purge volume and API usage.

For authenticated traffic, Cloudflare does not cache personalized responses, so purging primarily affects anonymous page views.
The previous warning messages have been replaced with informational notices in the latest release.

Best regards,
Alaa

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

flashwebcenter’s picture

Title: Cache tag purging on Cloudflare Free tier » Cloudflare Policy Update: All Purge Methods (Cache Tags, Prefixes, Hostnames) Now Available on Free Tier. Module Fully Supported
klemendev’s picture

Thank you for the clarifications :)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.