Google Cloud CDN pricing looks simple at first glance because the public rate card starts with a familiar bandwidth number. In practice, the bill is harder to model because Cloud CDN sits inside a broader Google application-edge stack, so buyers often pay for more than cache egress alone.
That does not make Google Cloud CDN a bad product. It means buyers should evaluate it as part of a layered Google architecture, not as a standalone CDN line item. If you only compare the headline per-GB rate, you can underestimate the real monthly cost and choose the wrong platform for the workload.
Quick buyer verdict
If you already want Google’s external Application Load Balancer, deep Google Cloud integration, and adjacent services like Cloud Armor, Cloud CDN can be a rational choice. It is strongest when CDN delivery is only one part of a broader Google-native web application or API design.
If your main goal is simpler delivery for websites, software downloads, images, VOD, or live streaming, Google’s pricing model is often harder to justify. In those cases, a more delivery-focused platform such as CDNsun can be easier to forecast and may be more economical once Google’s extra billing layers are included.
Cloud CDN vs Media CDN: start with the right Google product
This distinction matters early because many buyers accidentally evaluate the wrong Google service.
Google positions Cloud CDN as the default CDN for web applications, APIs, and image-heavy platforms. Google positions Media CDN more for large-scale video streaming and large file or download delivery. So if your real use case is OTT video, VOD packaging, large software distribution, or delivery economics for media traffic, Cloud CDN is not Google’s cleanest commercial comparison point in the first place.
That also creates a fair comparison angle with CDNsun. CDNsun is built around mainstream delivery use cases such as website acceleration, software delivery, VOD, HLS and DASH streaming, RTMP workflows, and live streaming. It does not need to replicate Google’s full cloud edge ecosystem to be the better commercial fit for those delivery-first workloads. If you want the broader platform context as well, see our related analysis of Google Cloud CDN review in 2026.
What Google Cloud CDN is actually selling
Google Cloud CDN is not just a bandwidth product. It is a cache layer attached to Google’s external Application Load Balancer and broader edge platform.
That architecture brings real advantages. Buyers can combine CDN delivery with Google’s routing, origin options, cache controls, signed URLs, signed cookies, private origin authentication, and Cloud Armor integration. For teams already invested in Google Cloud, that can reduce architectural friction.
But the same architecture is why pricing is easy to underestimate. Instead of one clean CDN invoice, buyers often inherit charges across multiple Google services. For finance teams and smaller engineering teams, that can make forecasting materially harder than with a simpler CDN provider.
Google Cloud CDN pricing structure
Google publicly prices Cloud CDN across three main CDN line items:
- Cache data transfer out
- Cache fill
- HTTP and HTTPS cache lookup requests
According to the official Google Cloud CDN pricing page, Europe and North America start at about $0.08 per GiB for the first 10 TiB of cache data transfer out. Cache fill starts at about $0.01 per GiB. Cache lookup requests are priced at $0.0075 per 10,000 requests. One GiB is about 1.074 GB, so buyers should normalize the units before comparing price cards.
Those are the core numbers most buyers see first. The problem is that they are not the whole bill.
Cacheable traffic can still be influenced by the surrounding Google design. Non-cacheable traffic falls back to normal load-balancing behavior and standard origin-side transfer economics. External origins can be especially tricky because Google states that request bytes sent from Google to the origin are charged at Compute Engine internet egress rates.
So the real commercial model is not just cacheable GB delivered multiplied by a public rate. It is closer to cache egress plus cache fill plus cache lookups plus possible load balancer charges plus possible origin-side charges plus optional security charges.
The load balancing layer buyers miss
One of the most overlooked parts of Google Cloud CDN pricing is the load balancing layer underneath it.
Cloud CDN relies on Google’s load balancer model, and Google separately prices global forwarding rules and load-balancer data processing. The first five global forwarding rules cost $0.025 per hour in total, and each additional rule costs $0.01 per hour. In many regions, load-balancer data processing is around $0.008 per GiB inbound and $0.008 per GiB outbound.
Google also makes an important point in its pricing documentation: cache hits do not transit the load balancer. That helps reduce some external Application Load Balancer costs, which is good news. But it also confirms the larger point that Cloud CDN pricing is intertwined with neighboring Google billing surfaces.
For buyers, the practical lesson is simple: do not evaluate Cloud CDN from the CDN pricing page alone. Model the load balancer too.
Common cost drivers buyers should model carefully
The most common Cloud CDN pricing mistake is treating the public egress rate as the total cost of ownership. In real deployments, additional charges usually come from a few repeat patterns.
1. Weak cache hit ratio
Poor cacheability pushes more traffic down the miss path. That can increase cache fill, increase origin exposure, and reduce the financial benefit of the CDN layer.
2. External origins
This is one of the clearest traps in Google’s documentation. If you use external backends, bytes sent from Google to the origin can trigger Compute Engine internet egress charges. That means a bad cache profile can hurt twice: once on the delivery side and again on the origin side.
3. Request-based billing
Google explicitly charges for cache lookup requests. That is not necessarily expensive in isolation, but it adds another moving part. High-request workloads with many small files can become harder to predict than a pure traffic-based commercial model.
4. Cloud Armor
If you need WAF or DDoS controls, Cloud Armor is a separate charge. Standard pricing includes per-request fees plus hourly policy and rule charges. Enterprise options can add protected-resource and data-processing charges on top. For security-sensitive teams this may still be worth it, but it should be budgeted as part of the edge stack, not treated as an afterthought.
5. Logging and observability model
Cloud CDN logs live through Cloud Logging on the external Application Load Balancer resource. That is workable, but it is different from a bundled raw-log model inside a delivery-specific CDN product. Smaller teams may find this less direct operationally.
Why cache mode selection affects cost
Cloud CDN behavior is also shaped by cache mode selection, and that can change both performance and monthly cost.
The key point is that cache mode is not just a technical tuning detail. It affects what gets cached, what misses, and how much traffic returns to origin.
If you rely on origin headers with a mode such as USE_ORIGIN_HEADERS, weak cache headers can suppress cacheability and leave you with more miss-path traffic than expected. A more aggressive mode such as CACHE_ALL_STATIC or FORCE_CACHE_ALL can improve cacheability in some scenarios, but aggressive caching also carries risk if content is private, user-specific, or simply not safe to cache broadly.
That means cost optimization and correctness are linked. A weak cache policy can make Cloud CDN look more expensive than planned. An overly aggressive one can create content-delivery mistakes. Buyers should model both.
Simple public pricing comparison with CDNsun
The honest comparison is not that CDNsun replaces Google’s full application-edge ecosystem. It does not. Google is stronger when you specifically want deep Google Cloud integration, load-balancer-centric design, and Cloud Armor-style packaging.
The honest comparison is that many buyers do not actually need all of that. They need predictable delivery pricing.
CDNsun pricing for the Business plan is $0.030 per GB in Europe and North America and $0.060 per GB in APAC, South America, and Africa. For normal CDN traffic, CDNsun does not charge a monthly fee for the CDN service itself, includes an unlimited number of requests, includes raw logs, includes streaming, and allows buyers to choose their PoPs directly.
That creates a very different buying experience:
- Google usually requires buyers to model several billing layers together
- CDNsun is closer to a single-purpose delivery bill
CDNsun also has cleaner cache-miss economics for mainstream delivery. Traffic from the customer origin to CDNsun infrastructure is free of charge, and traffic from CDNsun storage to CDNsun edge servers is also free of charge. For buyers who are tired of modeling miss paths, request charges, security add-ons, and load-balancer inheritance, that simplicity is commercially meaningful.
Where CDNsun is a stronger fit
CDNsun is often the more practical option when the workload is straightforward content delivery rather than cloud-native application edge design.
That includes:
- Website acceleration
- Software and game delivery
- Video on demand
- Live streaming
- Buyers who want one platform for delivery plus integrated storage
- Teams that care about simple monthly forecasting
CDNsun also has credibility points worth noting without overstating them. It has been operating since 2012, reports more than 30 data centers worldwide, and says it is trusted by 2000+ customers. It includes 24/7 support, API access with official client libraries, strong reporting, raw logs, and a 15-day trial with $5 credit.
Those are not arguments that CDNsun is always better. They are arguments that it is often a more natural commercial fit when the job is content delivery, not assembly of a broader cloud edge stack.
When Google Cloud CDN is worth it
Google Cloud CDN makes the most sense when you already want the rest of Google’s edge model.
That usually means:
- You are already heavily invested in Google Cloud
- You want CDN tied closely to Google’s external Application Load Balancer
- You need multiple origin patterns across a broader application architecture
- You want tight integration with Google-native security and networking services
- Your workload is more web-app or API centric than delivery centric
In that context, Cloud CDN’s layered pricing can be acceptable because the CDN is only one component in a wider platform decision.
When CDNsun is the simpler fit
CDNsun is usually easier to justify when the buyer wants a CDN first and a cloud platform second.
That is especially true for:
- Marketing and content sites
- Asset-heavy websites
- Download delivery
- Video workflows
- Traffic patterns where request fees and cache-fill modeling add noise
- Teams that want raw logs included
- Teams that value direct PoP selection as a budgeting tool
CDNsun does not need to beat Google on cloud breadth to win those deals. Clearer billing, simpler operations, and competitive delivery economics are often sufficient. Buyers who want to compare plans or start testing can use CDNsun’s company overview, review CDNsun pricing, or go straight to CDNsun.
FAQ
Does Google Cloud CDN charge for requests?
Yes. Google charges for HTTP and HTTPS cache lookup requests, published at $0.0075 per 10,000 requests.
Does Google Cloud CDN charge for cache misses?
Yes, indirectly and sometimes directly. Cache misses can increase cache fill charges, can inherit applicable load-balancer processing or Cloud Storage operation charges, and can expose buyers to origin-side transfer costs. With external origins, Google states that request bytes sent from Google to the origin are charged at Compute Engine internet egress rates.
Is Cloud Armor included with Cloud CDN?
No. Cloud Armor is a separate Google service with its own pricing model, including hourly and per-request charges in Standard and additional protected-resource and data-processing economics in some Enterprise scenarios.
Is Google Cloud CDN the same product as Media CDN?
No. Google documents them separately and positions them for different workloads. Cloud CDN is positioned for web apps, APIs, and image-heavy delivery. Media CDN is positioned more for large-scale video streaming and download delivery.
Is Google Cloud CDN expensive?
Not necessarily. It can be cost-effective in the right Google-native architecture. The issue is not that the base rate is automatically high. The issue is that the real bill is multi-layered, so buyers who only model the headline egress number can underestimate total cost.
Final verdict
Google Cloud CDN pricing is reasonable only when you evaluate it as part of Google’s larger application-edge stack. If that broader stack is exactly what you want, the layered billing may be justified.
If you mainly need clean, predictable delivery economics for websites, downloads, or streaming, the commercial picture changes. In those cases, CDNsun is often easier to forecast and often cheaper because requests, logs, streaming, and incoming traffic are not split across so many separate pricing meters.
The buyer decision comes down to this: do you need Google’s broader cloud edge model, or do you simply need a CDN with simpler delivery economics? For many mainstream CDN workloads, that difference matters more than the headline $0.08 per GiB rate.