Website · Documentation · Pricing

Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

Google Cloud CDN is Google’s content delivery service for web applications, APIs, downloads, and other cacheable HTTP content. It runs behind a global external Application Load Balancer and can use Google Cloud backends, Cloud Storage, or an external HTTP origin. Media CDN is a separate Google Cloud product for large-scale video and media delivery.

Network

Cloud CDN uses Google’s global edge network, with caches in more than 100 locations across published metropolitan areas. Several cities have multiple PoPs; city markers are not a count of individual caches.

Origins can be Google Cloud backends or external servers. An external Application Load Balancer routes requests; network edge and interconnect lists describe different infrastructure.

Published cache cities

Approximate city centers, not exact facilities. City counts do not measure network capacity. Published locations can change; some listed places have no marker.

AtlantaCharlestonChicagoColumbusCouncil BluffsDallas/Fort WorthDenverLas VegasLos AngelesMiamiMontrealNew YorkPhoenixQueretaroSalt Lake CitySan FranciscoSeattleTorontoTulsaBogotaBuenos AiresRio de JaneiroSantiagoSao PauloAmsterdamBerlinBudapestDublinFrankfurtGroningenHamburgHelsinkiLondonMadridMarseilleMilanMunichParisPragueSofiaStockholmTurinWarsawZurichDohaMuscatTel AvivBangkokChennaiHong KongJakartaKuala LumpurManilaMumbaiDelhiOsakaSeoulSingaporeTaipeiTokyoSydneyMelbourneJohannesburgLagosMombasa
Cities

Atlanta, Charleston, Chicago, Columbus, Council Bluffs, Dallas/Fort Worth, Denver, Las Vegas, Los Angeles, Miami, Montreal, New York, Phoenix, Queretaro, Salt Lake City, San Francisco, Seattle, Toronto, Tulsa, Bogota, Buenos Aires, Rio de Janeiro, Santiago, Sao Paulo, Amsterdam, Berlin, Budapest, Dublin, Frankfurt, Groningen, Hamburg, Helsinki, London, Madrid, Marseille, Milan, Munich, Paris, Prague, Sofia, Stockholm, Turin, Warsaw, Zurich, Doha, Muscat, Tel Aviv, Bangkok, Chennai, Hong Kong, Jakarta, Kuala Lumpur, Manila, Mumbai, Delhi, Osaka, Seoul, Singapore, Taipei, Tokyo, Sydney, Melbourne, Johannesburg, Lagos, Mombasa

Listed without a marker: Ashburn, Lenoir, Stevenson, The Dalles, Den Helder, Hamina, St. Ghislain, Fujairah, Changhua County, .

Features

FeatureSupported
Web application firewall◐ Partial
DDoS protection◐ Partial
HTTP/3 (QUIC)✓ Supported
TLS 1.3✓ Supported
Instant cache purge◐ Partial
Serve stale while refreshing✓ Supported
Serve stale on origin errors◐ Partial
Image optimization◐ Partial
Signed URLs✓ Supported
Edge compute◐ Partial
Edge functions◐ Partial
Configuration API✓ Supported
Real-time logs◐ Partial
Terraform provider✓ Supported

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

  • Configurable cache keys, policies and CDN-Cache-Control headers.
  • Signed URLs/cookies and private bucket access.
  • Stale-while-revalidate and configurable stale delivery during origin trouble.
  • Host, path and tag invalidation, generally taking about ten seconds.
  • Native image optimization in Preview.

The stale-if-error HTTP directive is not supported, even though configured stale delivery can cover origin errors. Invalidation completion can rarely precede every cache processing the request.

Cloud Armor is separate: edge policies run before cache; backend policies cover misses, bypasses and dynamic requests. Service Extensions add lightweight Wasm logic with separate limits and configuration.

Pricing

  • Delivery: destination and monthly volume determine the per-GiB rate.
  • Lookups: cacheable GET/HEAD requests cost $0.0075 per 10,000, including cache hits.
  • Fill: origin-to-cache traffic is charged separately; origin and cache region affect the rate.
  • Load balancing, external-backend request traffic, origin storage/operations and optional products can add costs.

The calculator models standard cacheable delivery. Opt-in regions, contracts and Global Front End bundles are excluded. Image optimization is temporarily free in Preview; its eventual GA charges are not modeled.

Developer tools

Use supported backend services or buckets with a global external or classic Application Load Balancer. Google Cloud and external origins, GKE, and supported serverless backends have documented setup paths. Configure through console, gcloud, REST APIs or Google Terraform resources.

Cloud Logging exposes request/cache-result fields and Cloud Monitoring exposes metrics. Backend-service sampling is configurable; verify logging coverage, export setup and cost rather than assume a guaranteed live stream. A Cloud Run origin is distinct from a request-path Service Extensions plugin.

When it fits

  • Applications already using Google Cloud load balancing or Google Cloud origins.
  • Teams that need an HTTP CDN with configurable cache policy, signed requests, and Cloud Logging.
  • Workloads that need to place a Google-managed edge in front of an external HTTP origin.

Before you choose

  • Cloud CDN requires Google Cloud load-balancing configuration.
  • A backend Cloud Armor WAF policy does not inspect every cache hit.
  • Use a separate estimate for Media CDN, load balancing, security and origin services.

History

Cloud CDN became generally available in June 2016. Google LLC is part of Alphabet.

Cloud CDN, Media CDN, Cloud Armor and Service Extensions are distinct products or integrations.

Product updates

Sources