Fastly CDN Pricing in 2026: Rates, Hidden Fees & Decision Matrix

A single misconfigured origin shield on Fastly can quietly add $800/month to your invoice before anyone notices. That is the kind of detail that makes Fastly CDN pricing worth dissecting beyond the headline rate card. As of Q2 2026, Fastly still bills purely on consumption — bandwidth, requests, and optional add-ons — with no flat-rate plans and no free tier. This article gives you the exact per-GB and per-request rates across every billing region, a full accounting of the add-on costs that inflate real-world invoices, and a workload-profile decision matrix you will not find in Fastly's own docs or in any competing page-1 result.

How Fastly CDN Pricing Works in 2026

Fastly does not publish plan tiers. Every account is usage-based, metered monthly, and invoiced in arrears. There are three cost axes: bandwidth, HTTP/HTTPS requests, and add-on services. Understanding each one independently is the only way to model your actual spend.

Bandwidth Rates by Region (as of May 2026)

Fastly groups its PoPs into billing regions and applies tiered volume pricing within each. The first 10 TB/month in any region carries the highest per-GB rate; costs step down at 10 TB, 50 TB, 150 TB, and 500 TB thresholds. Published rates for the first 10 TB tier:

At higher volume tiers (150 TB+), North America/Europe rates drop toward $0.04/GB. But most mid-market customers never reach those thresholds in a single region. If your traffic splits 60/30/10 across NA, APAC, and India, each region meters independently — you pay three different first-tier rates, not a blended one. This is the single biggest source of bill shock for teams migrating from flat-rate providers.

HTTP/HTTPS Request Charges

Request fees are separate from bandwidth and also region-tiered. For the first 10 billion requests per month:

For API-heavy workloads serving many small responses, request costs can rival or exceed bandwidth costs. A service returning 2 KB JSON payloads at 500 million requests/month in NA would pay roughly $375 in request fees but only ~$120 in bandwidth. Factor both axes into your model.

The Add-Ons That Inflate Your Fastly CDN Cost

Fastly's base metering is only part of the invoice. Several features that competitors bundle into their standard offering are billed separately on Fastly:

• Next-Gen WAF (Signal Sciences): Priced per request inspected, with enterprise contracts typically starting around $3,000/month minimum. No self-serve pricing is published as of Q2 2026 — you negotiate directly.
• Image Optimizer: $0.0025 per unique transformation. For e-commerce catalogs regenerating thumbnails across device breakpoints, this line item compounds fast.
• Log Streaming (real-time): Included in the base platform for syslog and basic endpoints, but high-volume streaming to services like BigQuery or S3 incurs additional data transfer charges from Fastly's side.
• Dedicated TLS (custom IP SSL): $100/month per certificate slot. Wildcard certs reduce this, but multi-domain deployments with distinct cert requirements add up.
• Origin Shield: No explicit per-request charge, but enabling it routes all cache misses through a designated shield PoP, adding an extra hop of bandwidth that shows up on your invoice as internal transfer.

A realistic mid-market Fastly invoice — 20 TB/month in NA, 5 TB in APAC, WAF enabled, image optimization on, two dedicated TLS certs — lands between $3,500 and $5,000/month. The bandwidth-only sticker price would suggest closer to $2,000.

Fastly Pricing vs. Cloudflare vs. CloudFront in 2026

Comparing Fastly pricing against Cloudflare and CloudFront requires normalizing for what is bundled vs. billed separately.

Fastly's real competitive advantage is sub-second config propagation and VCL/Wasm-based edge logic. You pay more per GB for that programmability. If your workload does not need instant purge or complex edge routing, the premium is hard to justify on cost alone.

Workload-Profile Decision Matrix: Which CDN Fits Your Stack

This matrix maps common architecture profiles to the CDN that delivers the best cost-to-capability ratio as of 2026. It is the section you will not find on Fastly's pricing page or in any competitor comparison currently ranking.

For bandwidth-intensive delivery — video, game patches, large binaries — Fastly's per-GB cost is 3–6x higher than volume-optimized alternatives. At 100 TB/month in NA alone, Fastly's blended rate sits around $0.06/GB ($6,000), while BlazingCDN delivers the same volume at $0.003/GB ($1,500/month flat), with 100% uptime SLA, fast scaling under demand spikes, and fault tolerance on par with CloudFront. Clients like Sony use BlazingCDN at these tiers. The cost delta at 500 TB or 1 PB becomes a line item large enough to fund an entire engineering headcount.

Modeling Your Real Fastly CDN Cost: A Worked Example

Assume a media company delivering 30 TB/month: 22 TB from NA, 6 TB from APAC, 2 TB from India. They serve roughly 200 million requests/month, use the image optimizer for 5 million transformations, and hold two dedicated TLS certs.

• NA bandwidth: 10 TB × $0.12 + 12 TB × $0.08 = $1,200 + $960 = $2,160
• APAC bandwidth: 6 TB × $0.19 = $1,140
• India bandwidth: 2 TB × $0.28 = $560
• Requests: 200M / 10,000 × $0.0075 (weighted avg) ≈ $150
• Image Optimizer: 5M × $0.0025 = $12,500
• Dedicated TLS: 2 × $100 = $200

Total: approximately $16,710/month. Strip out the image optimizer and the bill drops to $4,210 — illustrating how a single add-on can quadruple your spend. Before committing, run this exercise with your own traffic mix. Fastly's billing dashboard exposes per-region breakdowns that make this straightforward.

FAQ

How much does Fastly CDN cost for a small site?

Fastly has no free tier. A site serving 500 GB/month from North America would pay roughly $60 in bandwidth plus a few dollars in request fees. The developer trial offers a $50 credit, which covers light testing but not sustained production use.

What are Fastly's pricing tiers and how do volume discounts work?

Fastly uses tiered volume pricing within each billing region, with breakpoints at 10 TB, 50 TB, 150 TB, and 500 TB per month. Discounts apply only within a single region — traffic in Asia does not count toward your North America tier. Custom enterprise contracts with committed-use discounts are available above 100 TB/month.

Does Fastly charge separately for HTTP requests?

Yes. Request fees are metered independently of bandwidth at rates starting from $0.0075 per 10,000 requests in NA/EU. For workloads with high request counts and small response bodies (APIs, JSON endpoints), request costs can exceed bandwidth costs.

How does Fastly's free tier compare to Cloudflare's?

Fastly does not have a persistent free tier. Cloudflare's free plan includes unmetered bandwidth, basic caching, and a shared SSL cert — sufficient for low-traffic sites. Fastly's developer trial ($50 credit) is designed for evaluation, not long-term free hosting.

Is Fastly or CloudFront cheaper at 50 TB/month?

At 50 TB/month in North America, CloudFront's blended rate lands near $0.065/GB versus Fastly's approximately $0.09/GB blended. CloudFront wins on raw cost; Fastly wins on config speed and edge compute flexibility. The right choice depends on whether your architecture needs sub-second purge or tighter AWS integration.

What hidden fees should I watch for on Fastly?

Image Optimizer charges per transformation, WAF pricing requires a sales conversation, and origin shield adds internal bandwidth to your bill. Dedicated TLS is $100/month per slot. Always model your invoice with add-ons included, not just bandwidth.

Run Your Own Numbers This Week

Pull your last three months of CDN logs. Break out bandwidth by region, request counts by endpoint type, and list every add-on you currently use. Plug those numbers into Fastly's published rates, then run the same model against two alternatives. The delta will tell you whether you are paying for capabilities you use or subsidizing features you never enabled. If your bandwidth exceeds 25 TB/month and edge compute is not a hard requirement, the math almost certainly points away from Fastly. Start with the model. Let the numbers decide.