For the complete documentation index, see llms.txt. This page is also available as Markdown.

CDN

Enable Hostinger's CDN in hPanel to serve static assets from edge locations worldwide, purge cached files, and use built-in optimization and security controls.

A CDN serves static assets from locations close to your visitors, cutting load time for distant users. Find it under PerformanceCDN in your website dashboard. Available on Premium plans and higher; on some plans it's enabled automatically for new sites.

Enable CDN

  1. Open your website dashboard.

  2. Go to PerformanceCDN.

  3. Enable it for your domain.

Static assets route through the CDN automatically — no code changes. Controls are per domain, so a site with several domains can have different settings for each.

Disable CDN

PerformanceCDN → disable for the domain.

Purge the CDN cache

After updating assets, purge so the CDN fetches fresh copies.

  1. Go to CDN.

  2. Click Purge cache.

Full refresh may take a few minutes to propagate globally.

What the CDN caches

Static files:

  • Images (.jpg, .png, .gif, .webp, .svg)

  • CSS

  • JavaScript

  • Fonts

  • Videos and media

Dynamic content (PHP pages, form posts, API responses) is never CDN-cached — it always goes to your origin.

Optimization settings

The CDN panel includes asset-optimization options you can toggle per domain — compression and related speed features. Pair them with PageSpeed test runs to measure the effect.

Security controls

Beyond caching, the CDN panel includes access controls enforced at the edge:

  • IP block list — block specific IP addresses before they reach your site.

  • Traffic blocking by country — block visitors from selected countries, or switch to Allowed countries mode to permit only the countries you list.

Warning: In Allowed-countries mode, visitors from every unlisted country are blocked — double-check the list includes all your real audiences (and your own location).

Analytics

The CDN panel shows per-domain metrics: requests served by the CDN, bandwidth saved, and cache performance. Use them to confirm the CDN is actually absorbing traffic after you enable it.

SSL

CDN-served assets are delivered over HTTPS when your site uses SSL.


Last updated: July 22, 2026

Last updated

Was this helpful?