Fastly Streaming Delivery Pricing in 2026: Cost Breakdown & Decision Matrix

A single 1080p live stream to 50,000 concurrent viewers burns through roughly 20 TB per hour. At Fastly's published North American rate of $0.12/GB, that hour costs $2,400 in bandwidth alone — before requests, log streaming, or origin shield charges enter the invoice. For a 4-hour sports broadcast, you are looking at close to $10,000 in CDN spend on a single event. Understanding fastly streaming delivery pricing at the line-item level is the difference between a sustainable streaming operation and one that hemorrhages margin every time viewership spikes. This article gives you the full cost model: per-region bandwidth, request charges, add-on fees that quietly compound, a workload-profile decision matrix you will not find elsewhere, and a side-by-side against alternatives shipping video in 2026.

Fastly Streaming Delivery Pricing: Per-GB Bandwidth Rates in 2026

Fastly's pricing page still advertises a pay-as-you-go model with no minimum commitment. As of Q2 2026, the published per-GB rates by region remain:

These rates are list prices. Enterprise contracts with committed spend can negotiate lower, but Fastly does not publish those tiers. If you push 100+ TB/month and have not renegotiated since 2024, it is worth revisiting — multi-year commits from competing vendors have pressured the mid-market rate downward across the industry in 2026.

Hidden Costs That Inflate Fastly CDN Cost for Video

Bandwidth is the headline number. It is rarely the final number. Streaming workloads on Fastly accumulate charges across several axes that are easy to underestimate during capacity planning.

Request Fees

HLS and MPEG-DASH generate high request volumes by design. A two-hour VOD session at 6-second segment durations creates roughly 1,200 GET requests per viewer. Fastly charges per 10,000 requests, and at scale those fractions compound. For a catalog service with millions of daily sessions, request fees can represent 8–15% of the total CDN bill.

Origin Shield

Fastly media shield pricing is not broken out on the public pricing page. Shield reduces origin load by funneling cache misses through an intermediate PoP, but every shield request is itself a billable request, and the data transfer between shield and edge counts toward bandwidth. For live events with cold-cache bursts, shield traffic can spike hard in the first 30 seconds before segments propagate.

Log Streaming and Real-Time Analytics

Fastly's real-time log streaming (to S3, BigQuery, Datadog, etc.) is included in base pricing up to a threshold, but high-volume streaming services regularly exceed it. If you ingest per-request logs for QoE dashboards, verify whether your log volume triggers overage charges.

Image and Video Optimization

Fastly's image optimization service (Fastly IO) is billed separately. Video-specific transformations at the edge — thumbnail generation, manifest manipulation — typically require Compute@Edge usage, which has its own invocation and duration billing.

Fastly Live Streaming Pricing vs. VOD: Where Costs Diverge

Live and VOD workloads hit Fastly's pricing model differently. Understanding the divergence matters for accurate forecasting.

Live streaming concentrates massive bandwidth into short windows. Cache hit ratios for live are inherently lower during the first segment window, which means more origin pulls and more shield traffic. Fastly's instant purge and sub-second cache propagation are genuine advantages here — stale segment delivery during a live broadcast is a user-visible failure. But you pay for that freshness through higher request rates and shield bandwidth.

VOD workloads benefit from high cache hit ratios on popular titles (often 95%+ for head-of-catalog content). Fastly video on demand pricing is therefore more predictable. The risk is long-tail content: thousands of titles with low viewership that generate cache misses across multiple PoPs. Without careful TTL tuning and origin consolidation, long-tail VOD libraries drive disproportionate origin egress.

2026 CDN Pricing Comparison for Video Streaming

At 500 TB/month — a volume common for mid-size streaming platforms — the gap is stark. Fastly's North American rate yields a $60,000 monthly bandwidth bill. The same volume through BlazingCDN's media delivery infrastructure runs $1,500/month base with overages at $0.003/GB, totaling under $1,500 for the committed tier. BlazingCDN delivers stability and fault tolerance comparable to CloudFront while scaling flexibly under demand spikes — a combination that has attracted enterprise clients including Sony. For teams where bandwidth cost is the dominant line item, the arithmetic is difficult to ignore.

Workload-Profile Decision Matrix: Which CDN Fits Your Streaming Architecture

No single CDN is optimal for every streaming topology. This matrix maps provider strengths to specific workload profiles — use it to shortlist before running your own benchmarks.

The key insight: Fastly's value concentrates in latency-critical, logic-at-the-edge workloads. If your streaming architecture does not require sub-second cache invalidation or per-request Wasm execution, you are paying a premium for capabilities you are not using.

Cost Optimization Tactics for Fastly Streaming Workloads

If you are committed to Fastly, there are concrete ways to reduce your effective per-GB cost:

• Segment duration tuning: Moving from 2-second to 6-second HLS segments reduces request count by 3× with marginal latency impact for non-real-time streams.
• Shield placement: Choose shield PoPs geographically closest to your origin. Misplaced shields add latency and inter-PoP transfer cost without improving hit ratio.
• Surrogate-Key purging: Use granular purge keys instead of wildcard purges to avoid unnecessary cache busting, which drives re-fetch storms.
• ABR ladder optimization: Trim renditions that account for less than 2% of session time. Fewer renditions mean fewer unique segments cached per title, improving storage utilization at the edge.
• Multi-CDN for overflow: Route baseline traffic through Fastly and burst traffic through a lower-cost secondary CDN. This caps Fastly spend while preserving its latency advantages for your primary audience tier.

FAQ

How much does fastly streaming delivery cost for a 100 TB/month video platform?

At list rates as of Q2 2026, 100 TB of North American delivery costs approximately $12,000/month in bandwidth alone. Add request fees (typically 8–15% extra for HLS/DASH workloads), origin shield traffic, and log streaming, and realistic all-in cost lands between $13,500 and $15,000/month before negotiated discounts.

Is Fastly media shield worth it for multi-CDN streaming?

Shield reduces origin load and improves cache consistency, which is valuable when running multi-CDN with DNS-level switching. However, shield itself generates billable requests and inter-PoP bandwidth. For VOD catalogs with 90%+ cache hit ratios, the incremental cost of shield may outweigh the origin savings. Benchmark both configurations over a 7-day window before committing.

What is Fastly live streaming pricing for HLS delivery specifically?

Fastly does not differentiate pricing between HLS and DASH — both are billed at the same per-GB and per-request rates. The cost difference between protocols comes from segment size and manifest request frequency. CMAF with chunked transfer encoding on Fastly can reduce segment count for low-latency live, slightly lowering request-based charges.

How does Fastly CDN pricing compare to CloudFront for video on demand?

CloudFront's volume tiers start lower (as low as $0.02/GB at the 5 PB+ tier as of 2026), and its free-tier origin fetches from S3 eliminate a cost category Fastly charges for. For AWS-native VOD pipelines, CloudFront typically runs 40–60% cheaper than Fastly at equivalent volume. Fastly's advantage is programmability and purge speed, not unit cost.

Can I reduce Fastly video on demand pricing by adjusting cache TTLs?

Yes. Extending TTLs on immutable segments (which HLS/DASH segments inherently are) to 30+ days eliminates unnecessary revalidation requests. Ensure your manifest TTLs remain short (2–6 seconds for live, 60+ seconds for VOD) while segment TTLs are set aggressively long. This alone can improve edge hit ratios by 3–5 percentage points on long-tail catalogs.

Run Your Own Numbers This Week

Pull your last 30 days of CDN invoices and break out bandwidth, requests, shield transfer, and add-on charges into separate columns. Calculate your effective per-GB cost — the real number, not the published rate. Then model the same traffic volume against two alternative providers using their public rate cards. If your effective Fastly cost exceeds $0.08/GB and you are not using Compute@Edge, you have optimization headroom worth six figures annually at scale. Start there.