Google Cloud is Google's cloud-services brand for businesses and developers. Cloud CDN focuses on caching for websites and applications, while Media CDN serves live and on-demand video and large-file delivery. The services suit teams that want to manage content delivery alongside Google Cloud load balancing, storage, monitoring and security.
Mountain View, California, United States (Google headquarters)
Listing
Parent Alphabet: NASDAQ GOOGL / GOOG; Google Cloud is not separately listed
Google's cloud services and the Google Cloud brand
Larry Page and Sergey Brin founded Google, which was incorporated in the United States in 1998 and is headquartered in Mountain View, California. Its developer cloud services date back to the App Engine preview in 2008. Google introduced the Google Cloud brand in 2016 to bring its enterprise cloud products together. Following the 2015 reorganization, Google became part of Alphabet; Google Cloud operates within that business and is not a separately listed company.
Two CDN products with different delivery priorities
Cloud CDN entered alpha in 2015 and became generally available in 2016, providing edge caching for websites and applications. Media CDN became generally available in April 2022, drawing on the distribution infrastructure Google built for services such as YouTube. It targets high-throughput streaming and large-file delivery. The products have different configuration models and traffic priorities, so the choice depends on content, origin architecture and operational requirements.
Deployment alongside load balancers and origins
Cloud CDN works with a global external Application Load Balancer or a classic Application Load Balancer, with caching enabled on a backend service or bucket. Origins can run on Google Cloud or connect from other environments through supported external backends. Media CDN uses routing, cache and origin resources to deliver content from public HTTP origins, with authenticated access also available for private Cloud Storage buckets. Both use Google's global edge infrastructure and provide cache controls, logging and access controls. They fit engineering teams comfortable configuring cloud infrastructure.
An expanding cloud and security platform
Google Cloud completed its acquisition of Mandiant in 2022. Google completed the Wiz acquisition in March 2026, bringing Wiz into Google Cloud while retaining its brand. These acquisitions broaden the cloud security business; security for a CDN deployment still requires selecting and configuring the relevant products, such as Cloud Armor, with their own capabilities and charges. The contracting entity for Google Cloud depends on the customer's billing address and service category, and may be Google LLC or a regional affiliate. Procurement should follow the applicable agreement and account details.
Web and application teams already using Google Cloud
Cloud CDN works with external Application Load Balancers, Cloud Storage and supported compute backends to deliver images, scripts and other cacheable responses. It suits teams keeping delivery within existing projects, access controls and monitoring.
Design cache keys, cookie handling and freshness rules, decide which responses are safe to share, and budget for load balancing, cache fill and requests together.
Video platforms and large download services
Media CDN targets high-throughput streaming and large downloads. It can use HTTP origins on Google Cloud, another cloud or on premises, with routing, signed requests and tiered caching to control delivery.
Ask sales or your account team to enable the project, then test playback startup, origin traffic and total cost with your actual bitrates, content popularity and target ISPs.
Platforms combining delivery with access control
Depending on the CDN selected, Cloud Armor policies, signed URLs or cookies, and Cloud Logging can connect content access and request troubleshooting to existing operations.
Security-policy and extension support differ between the products. Confirm additional charges, Preview limitations and the conditions for storing cached content across regions.
Choose by workload: evaluate Cloud CDN for website and application caching, and Media CDN for high-throughput video or large downloads. Test cache hits, latency and origin load from the regions and ISPs you serve, and rehearse origin failures and alternative delivery paths.
03
Services and products
Core products from official sources
Explore products by use case: what they do, how to use them and whether they are billed separately.
Cloud CDN for websites and applications
Web and application delivery
Cloud CDN caches website assets, images and cacheable application responses on Google's global edge network. It works with a global external or classic Application Load Balancer and can use Compute Engine, Cloud Storage, GKE or HTTP origins in another cloud or on premises. Cache keys, TTLs, signed URLs, private-origin access and targeted invalidation give teams control over delivery.
Cache egress, cache fill and GET/HEAD lookups are metered separately; load balancing and origin services have their own charges.Official product information
Media CDN for video and large downloads
Media delivery
Media CDN is designed for live and on-demand video and high-throughput file delivery. EdgeCacheService manages domains, TLS, routing and caches; EdgeCacheOrigin controls origin connectivity and retries. It supports tiered origin shielding, private Cloud Storage origins, signed URLs and cookies, and path or tag invalidation. HTTP/2 is enabled by default for clients; the account team must enable HTTP/3 (QUIC). TLS delivery on your own domain and Google-managed certificates carry no additional charge.
Sales or the account team must enable each project; delivery usage, capacity and additional services follow the agreed quote.Official product information
Cloud CDN image optimization — Preview
Image processing
Cloud CDN offers native image optimization in Preview for teams testing image processing within their delivery workflow. The feature is subject to Pre-GA terms, and its eventual GA processing charges should be included in a production budget.
No image-optimization feature charge during Preview; GA charges will apply. CDN delivery and other services remain billable.Official product information
Cloud Armor security
Application and edge security
Cloud CDN integrates with Cloud Armor for WAF, access controls and DDoS protection. Media CDN supports edge security policies with IP, geography, header and ASN filtering, currently requiring account-team allowlisting; Threat Intelligence requires the Enterprise tier. Edge and backend policies run at different stages, so placement must account for cache hits and traffic sent to origins.
Standard meters policies, rules and requests. Enterprise adds subscription, protected-resource and data-processing charges.Official product information
Service Extensions
Edge extensions
Service Extensions inserts custom logic into load-balancer and CDN processing paths. Media CDN's Preview Wasm plugins can normalize headers, influence cache keys and validate custom tokens before cache lookup. They support request and response headers, but not gRPC callouts, body callbacks or trailer processing. Load-balancer plugins and callouts to customer-managed services are separate deployment options.
Load-balancer extensions meter invocation events; Media CDN extension access and charges should be confirmed with its service arrangement.Official product information
Global Front End Enterprise — Preview
Consolidated frontend
Global Front End combines the global external Application Load Balancer, Cloud CDN, Cloud Armor and Service Extensions. Enterprise is an optional project-level consolidated billing tier for compatible forwarding rules. Backend resources in other projects retain their own product billing. Standalone Cloud CDN usage pricing remains available.
Consolidated regional data processing, request counts and an hourly instance fee for each forwarding rule.Official product information
Sources: Google Cloud (Cloud CDN / Media CDN) official product pages and developer documentationVerified: 2026-11-16
04
Plans and pricing
Official public pricing
Website delivery and security plans · monthly and annual billing shown separatelyUSD
Cloud CDN pay as you go
Websites, applications and existing Google Cloud origins
Usage based
Monthly billing
Monthly cache egress uses four tiers for each project and destination. Cache fill and GET/HEAD lookups are additional.
Load balancing, origin compute and storage, uncacheable traffic, security and logs are charged by the services used. Contact sales for volume discounts above 500 TiB a month.
Media CDN project arrangement
Live video, VoD and large-file delivery
Custom quote
Agreed terms
Ask Google Cloud sales or your account team to enable Media CDN for the project before deploying EdgeCacheService and its origins.
Agree on destinations, monthly delivery, peak throughput, capacity allotment, origin traffic, requests, security, logs, extensions and support. Cloud CDN rates and automatic trial access do not carry over.
Global Front End Enterprise
Teams consolidating edge routing and security
Usage based
Preview
An optional project-level billing tier combines compatible global external load balancing, Cloud CDN, Cloud Armor and Service Extensions.
US$0.20 per forwarding-rule instance-hour and US$0.0075 per 10,000 requests, plus regional data-processing tiers. The usage details list the regional rates.
Backend projects retain separate product charges. Pre-GA terms apply during Preview.
New-customer Welcome credit
Eligible first-time Google Cloud customers
US$300 credit
90 days
You must never have been a paying Google Cloud, Google Maps Platform or Firebase customer and must not have taken the trial before. A valid payment method and identity/payment verification are required.
Cloud CDN can be tested with the credit. There are no automatic trial charges; upgrading enables billing beyond eligible credit or free allowances. Any unused credit still expires 90 days after signup.
Without an upgrade, expiry or credit exhaustion closes billing and stops resources. A 30-day recovery grace period follows; trial resources are permanently deleted if the account is not upgraded.
How are separate products billed?
Product
Allowance / base fee
Usage prices
Cache egress: North America and Europe
USD/GiB, per project and destination each month.Tiers <10 / 10–150 / 150–1,000 / ≥1,000 TiB cost US$0.08 / 0.055 / 0.03 / 0.02 respectively.North America includes Hawaii.
US$0.02–0.08 / GiB
Cache egress: APAC, South America and other destinations
The same four monthly tiers cost US$0.09 / 0.06 / 0.05 / 0.04 per GiB.APAC includes Hong Kong;other destinations include Mexico, Central America and the Middle East.Usage is accumulated separately for each destination.
US$0.04–0.09 / GiB
Cache egress: China destination
The same four tiers cost US$0.20 / 0.17 / 0.16 / 0.145 per GiB.Mainland China traffic is served from Google locations outside mainland China, rather than an in-country CDN deployment.
US$0.145–0.20 / GiB
Cache egress: Oceania
The same four tiers cost US$0.11 / 0.09 / 0.08 / 0.065 per GiB.Includes Australia, New Zealand and surrounding Pacific islands;excludes Hawaii.
US$0.065–0.11 / GiB
Opt-in network region: Jakarta
With BYOIP opt-in network regions enabled: US$0.12 / 0.095 / 0.08 per GiB for <10 / 10–150 / 150–500 TiB a month.Above 500 TiB requires a quote.
US$0.08–0.12 / GiB
Opt-in network regions: Doha and Dammam
With BYOIP opt-in regions enabled, the same three tiers cost US$0.11 / 0.09 / 0.06 per GiB.Contact sales above 500 TiB.
US$0.06–0.11 / GiB
Cache fill within North America or Europe
Origin-to-cache transfers within North America or within Europe.North America includes Hawaii.
US$0.01 / GiB
Cache fill within other regions
Transfers within each of APAC, South America, the Middle East, Africa or Oceania.APAC includes Hong Kong.
US$0.02 / GiB
Inter-region cache fill
For example, filling an APAC cache from a North American origin.
US$0.04 / GiB
HTTP/HTTPS cache lookups
GET and HEAD requests cause lookups;POST and PUT do not incur this lookup item.Bytes sent to external origins and uncacheable responses can incur other network charges.
US$0.0075 / 10,000
Load-balancer forwarding rules
Under standalone billing, the first five global forwarding rules together cost US$0.025/hour, then US$0.01/hour for each additional rule.Global and regional rules are counted separately per project.
From US$0.025 / hour
Load-balancer data processing
Inbound and outbound external Application Load Balancer processing each cost US$0.008/GiB.Responses served directly from the edge cache do not pass through the load balancer and avoid that outbound processing item.
US$0.008 / GiB
Cloud Armor Standard
Global-policy requests cost US$0.75/million;regional-policy requests cost US$0.60/million.Each policy costs US$0.006849315/hour and each rule US$0.001369863/hour. reCAPTCHA is additional.
US$0.75 / million
Cloud Armor Enterprise CDN processing
Paygo CDN processing costs US$0.0375 / 0.03 / 0.025 / 0.02 per GiB for monthly tiers <100 / 100–500 / 500–1,000 / ≥1,000 TiB.Annual rates are US$0.025 / 0.02 / 0.015 / 0.01.Subscription and protected resources are additional;Annual commits for one year.
US$0.01–0.0375 / GiB
Load-balancer extension invocations
Plugins include 2 million invocation events per account each month, then US$0.10/million.Callouts cost US$0.10/million.One request can cause multiple events;customer-managed compute and cross-region traffic are additional.This allowance is not a Media CDN free plan.
US$0.10 / million
Cloud Logging storage
Ordinary logs cost US$0.50/GiB streamed into storage, with the first 50 GiB/project/month free and 30 days of storage included.Retention beyond 30 days costs US$0.01/GiB/month.Export destinations and other log classes have their own prices.
US$0.50 / GiB
GFE Enterprise instances
The consolidated tier charges for every compatible forwarding-rule instance-hour, rather than the standalone first-five-rules price.
US$0.20 / rule-hour
GFE Enterprise requests
A single request rate covers application and edge-cached traffic in the consolidated tier.Processing and instance charges are additional.
GFE Enterprise processing: China and opt-in regions
Same five tiers, USD/GiB.China destination: 0.172 / 0.1531 / 0.1487 / 0.1381 / 0.1196;other destinations incl.Mexico, Central America and Middle East: 0.1033 / 0.0844 / 0.08 / 0.0693 / 0.054;opt-in Jakarta: 0.1243 / 0.1086 / 0.1042 / 0.0904 / 0.0814;opt-in Doha and Dammam: 0.121 / 0.1084 / 0.104 / 0.0807 / 0.0717.Confirm project scope and applicable SKUs before selecting the tier.
Regional tiers
Cloud CDN meters GiB/TiB. The destination is where traffic leaves Google's network, with monthly tiers accumulated separately for each project and destination. Cache hits incur egress and lookup charges; misses add cache fill and applicable load-balancing or storage operations. Uncacheable responses use the relevant origin network rates. Published prices are USD; other billing currencies use their local SKUs. Estimate the optional Global Front End Enterprise tier separately from standalone service pricing. Media CDN requires its own enablement and commercial arrangement.
Cloud CDN fits an existing cloud load-balancing and application architecture, while Media CDN provides a dedicated path for video and large content. Both suit teams able to manage caching, permissions and usage budgets.
Use casesProductsPricing and termsDocumentationSupport resources
Why we recommend it
Cloud CDN adds caching to external Application Load Balancers and works with existing Google Cloud backends and operating tools.
Media CDN combines routing, content authentication and tiered caching with cloud or on-premises HTTP origins for media delivery.
Cache controls, access policies and logs help teams tune delivery by content type and trace edge and origin requests.
Considerations
Budget for cache delivery, cache fill, requests, and the associated load-balancing, origin and security charges together. Media CDN requires enablement through sales or an account team; assess Preview features and their production-support limits separately. Validate target-region performance and cache data-location requirements, and keep a tested failover plan for critical services.
CdnChart Editorial· Reviewed 2026-11-16
Related articles
Explore Google Cloud (Cloud CDN / Media CDN) products, use cases and buying advice
No articles about Google Cloud (Cloud CDN / Media CDN) yet.