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

NAVER Cloud Platform Global CDN delivers files and media through a partner network in Classic and VPC environments. Global CDN retires on December 31, 2026, and new creation is blocked. Existing users must migrate to Global Edge, NAVER’s replacement CDN.

NAVER’s September 17, 2026 release added console migration to Global Edge. Plan and test the migration before the retirement date. The Global CDN capabilities described here do not establish identical behavior or pricing on Global Edge.

Network

Global CDN uses an external delivery network. NAVER warns about delivery quality in Korea and China; China also requires the applicable ICP license. Check audience coverage separately from the cloud region where you manage the service.

Features

FeatureSupported
Web application firewallNot listed
Bot protectionNot listed
DDoS protectionNot listed
Rate limitingNot listed
HTTP/3 (QUIC)Not listed
TLS 1.3Not listed
Tiered cachingNot listed
Origin shieldNot listed
Instant cache purge◐ Partial
Serve stale while refreshingNot listed
Serve stale on origin errorsNot listed
Image optimizationNot listed
On-demand video✓ Supported
Live videoNot listed
Digital rights managementNot listed
HLS / DASH packagingNot listed
WebSocketsNot listed
Signed URLs✓ Supported
Edge computeNot listed
Edge functionsNot listed
Key-value storageNot listed
Configuration API✓ Supported
Real-time logsNot listed
Log exportNot listed
Terraform providerNot listed

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

  • Origins: web servers or NAVER Object Storage, using HTTP or HTTPS.
  • Delivery: HTTP/2, cache controls and cache purge.
  • Access and monitoring: token/referrer rules, usage reports and access logs.

Pricing

Global CDN retires on December 31, 2026, and is closed to new creation. For an existing service, confirm charges through the remaining service period. Budget the Global Edge replacement separately using NAVER’s current calculator or a confirmed quote. Include any Object Storage and origin traffic charges. The handbook’s USD traffic presets do not automatically convert NAVER’s local-currency tariffs into a complete estimate.

Developer tools

Use the console’s Global Edge migration feature for an existing Global CDN service. It was added in NAVER’s September 17, 2026 release. Complete the migration before Global CDN retires on December 31, 2026.

Validate origins, domains, certificates, cache rules, token/referrer controls, purge behavior and logs on the replacement. Check the applicable Classic or VPC setup and update application or DNS references as needed. The Global CDN guide and API reference describe the retiring product; verify Global Edge’s own configuration and API requirements.

When it fits

  • Existing Global CDN customers planning their move to Global Edge before December 31, 2026.
  • NAVER Cloud workloads evaluating Global Edge as the replacement delivery service.

Before you choose

  • New Global CDN deployments: new creation is blocked.
  • Workloads relying on Global CDN after December 31, 2026.
  • Migrations that assume Global Edge has identical configuration, coverage or pricing without checking its own documentation.
Sources