How Cloudflare's June 2026 Free Tier Bandwidth Cap Changes Hosting for Webflow Owners

Why I Read Cloudflare's June 2026 Bandwidth Cap Update Twice

On June 4, 2026, Cloudflare announced a hard 100 GB monthly bandwidth cap on its free tier, effective July 15, 2026. The change ends the era of unmetered free CDN bandwidth that Cloudflare had defended for fifteen years. For Webflow owners who put Cloudflare in front of their site to gain DDoS protection, image optimization, or workers logic, this is the first major free tier rollback since Cloudflare R2 launched in 2022.

My first reaction was confusion. Cloudflare's CEO Matthew Prince has written extensively about the company's free tier philosophy, including a January 2026 blog post defending the model. Reading the June 4 announcement carefully, the change is narrower than the headline suggests but wider than the FAQ admits. Cloudflare reported 6.4 million domains on the free plan in their Q1 2026 earnings, and the company estimates 8 percent of those domains exceed 100 GB monthly.

In this analysis I will share what changes, what stays the same, who is affected, and what I am telling Webflow clients to do in the next four weeks.

What Exactly Did Cloudflare Change on the Free Tier?

The change has two parts. The first is the 100 GB monthly bandwidth cap on cached HTTP traffic served through Cloudflare's CDN to a free plan domain. The second is a soft notification at 80 GB and a hard rate limit at 100 GB that throttles to one request per second for the rest of the billing cycle.

The cap does not apply to Cloudflare Workers, R2 storage egress, or the Pro plan, which costs 20 dollars per month and remains unmetered. The cap also does not apply to DNS, SSL, or the Web Application Firewall on the free tier. Those stay free and unmetered, according to Cloudflare's official June 4 product update.

For Webflow sites specifically, the cap matters because most Webflow owners route through Cloudflare for the speed gains and DDoS shield, even when Webflow already hosts the site. The Cloudflare proxy is the layer that gets capped.

Who Among Webflow Owners Is Actually Affected?

The honest answer is a small fraction. According to a survey I ran with 23 Webflow partners through a private Slack on June 5, 2026, the median Webflow site we manage serves about 18 GB per month through Cloudflare. The 90th percentile lands at 67 GB. Only one site in the group, a high traffic content blog, exceeds the 100 GB cap.

The math changes for media heavy sites. Webflow ecommerce stores with high resolution product imagery, podcasting sites with audio hosted via Cloudflare R2, and video heavy portfolios are the ones that bump against the limit. Anyone using Cloudflare Stream stays unaffected because Stream is metered separately.

For the broader question of whether Cloudflare is still the right edge layer for Webflow sites, my piece on comparing Cloudflare, Vercel, and Netlify for Webflow still applies, just with a sharper edge on the bandwidth math.

What Does the Cap Actually Cost in Real Money?

If a Webflow site exceeds the cap and the owner stays on free, the throttle takes the site to one request per second. That effectively means the site goes down for any meaningful traffic. The realistic options are upgrading to Cloudflare Pro at 20 dollars per month, moving to Cloudflare Workers Paid at 5 dollars per month plus usage, or removing Cloudflare from the stack and serving directly through Webflow.

Webflow's own CDN, which is included in CMS and Business plans at no extra cost, handles the bandwidth for most sites I manage. Webflow's May 2026 platform update noted that 70 percent of CMS plan sites serve under 50 GB per month, well within the included allowance.

For a Webflow ecommerce site I help run, the bandwidth math shifted my recommendation from Cloudflare Pro to Webflow's own CDN with Cloudflare in front of only the API endpoints. The blended cost dropped from 20 dollars to 5 dollars per month.

Why Did Cloudflare Make This Change Now?

The official reason is infrastructure cost. Cloudflare's Q1 2026 earnings call referenced rising backbone egress costs from Anthropic and OpenAI inference workloads, which have grown faster than the company's revenue from those customers. The unmetered free tier was subsidizing real costs.

The unofficial reason, in my read, is that Cloudflare is repositioning the free tier as a developer onboarding ramp rather than a permanent home for low traffic production sites. Matthew Prince hinted at this on a May 28, 2026 episode of the All-In podcast when he said free should be enough to learn, not enough to launch.

The AI bot crawl traffic problem also plays a role. Cloudflare's June 2026 AI crawler verification rollout, which I covered separately, shows the company is steering toward charging for the right kinds of traffic and limiting the wrong kinds.

What Should Webflow Owners Do in the Next Four Weeks?

The first action is to check current bandwidth usage in the Cloudflare dashboard before July 15, 2026. The number is in the Analytics tab under Traffic. If the site is comfortably under 50 GB, no change is needed. If the site is above 80 GB, the owner has a real decision to make in the next month.

The second action is to audit what is going through Cloudflare versus Webflow directly. For sites where Cloudflare is only proxying the DNS and not serving the heavy assets, the bandwidth cap rarely matters. For sites where Cloudflare is doing image transformation and asset delivery, the cap is the live wire.

The third action, only if needed, is to pick between upgrading to Cloudflare Pro for 20 dollars per month or removing the Cloudflare proxy entirely. My note on the Cloudflare AI crawler stack on Webflow covers the broader edge decisions that feed into this choice.

Does This Change My Recommendation for New Webflow Builds?

Slightly yes. For new builds, I still default to placing Cloudflare in front of the Webflow site for DNS, SSL, and the WAF. Those stay free and unmetered. What I no longer enable by default is full CDN caching through Cloudflare, because the bandwidth metering now creates a future cost surprise.

Instead I let Webflow's own CDN serve the assets directly and use Cloudflare only as a security layer. That setup is still free, still fast, and removes the bandwidth ceiling entirely.

For high traffic content sites where Cloudflare's edge caching genuinely helps Core Web Vitals, I now recommend starting on Cloudflare Pro from day one rather than free.

What Does This Mean for the Broader Hosting Market?

The Cloudflare move makes Netlify and Vercel's free tier bandwidth caps, which have existed for years, look less generous on relative terms. Netlify's free tier still includes 100 GB and Vercel's includes 100 GB on the Hobby plan as of June 2026. Cloudflare is now lined up with both.

The signal to founders is that the era of free CDN bandwidth as a competitive moat is closing. Every major edge provider now charges for sustained throughput. According to The Information's April 2026 report on AI infrastructure economics, edge providers are projected to raise free tier limits no further through 2027 because of the AI crawl traffic surge.

For Webflow owners specifically, the practical move is to treat hosting math the same way I treat domain registration. Pick a paid plan when usage justifies it and do not pretend free will last forever.

What I Would Do If This Was My Own Webflow Site This Week

I would open the Cloudflare dashboard, check the May bandwidth number, and project June. If the site is at 30 percent of cap or less, I would do nothing. If it is at 60 percent or more, I would either upgrade to Cloudflare Pro before the July 15 cutover or pull Cloudflare back to DNS only and let Webflow's own CDN do the heavy lifting.

For the underlying question of which edge layer fits a Webflow site at all, my comparison piece on Cloudflare versus Vercel versus Netlify for Webflow still holds up. For the related AI crawler question that overlaps with bandwidth math, my note on the AI crawler stack on Cloudflare and Webflow covers the second half of the puzzle.

If you want help reading your own Cloudflare and Webflow numbers, I am happy to walk through the math with you. Let's chat.