{"id":18721,"date":"2026-09-23T04:37:14","date_gmt":"2026-09-23T04:37:14","guid":{"rendered":"https:\/\/www.hostinger.com\/support\/?p=18721"},"modified":"2026-09-23T04:37:14","modified_gmt":"2026-09-23T04:37:14","slug":"how-hostinger-cdn-caching-works","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/how-hostinger-cdn-caching-works\/","title":{"rendered":"How Hostinger CDN caching works"},"content":{"rendered":"

Hostinger CDN<\/a> caches copies of your website’s files on servers close to your visitors and serves them without contacting your hosting server. Static files are cached automatically, HTML pages are cached only when your website asks for it, and requests that belong to a logged-in visitor or a shopping cart are never served from the cache. Knowing these rules explains why a change appears immediately in one place and later in another.<\/p>

What Hostinger CDN caches<\/h2>
\n\n\n\n\n\n\n\n\n\n\n
\n

Content<\/b><\/p>\n<\/td>\n

\n

Cached at the CDN edge<\/b><\/p>\n<\/td>\n

\n

Default duration<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Static files: images, CSS, JavaScript, fonts, downloads<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Up to 2 hours, or the time set by your website’s cache headers<\/p>\n<\/td>\n<\/tr>\n

\n

Optimized images (WebP, resized)<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Up to 30 minutes by default on web hosting, or the time set by the original image’s cache headers<\/p>\n<\/td>\n<\/tr>\n

\n

HTML pages on web hosting (WordPress, PHP, Node.js)<\/p>\n<\/td>\n

\n

Only when marked cacheable by your website<\/p>\n<\/td>\n

\n

The time your website or caching plugin specifies<\/p>\n<\/td>\n<\/tr>\n

\n

Website Builder and Horizons websites<\/p>\n<\/td>\n

\n

Yes, the whole website<\/p>\n<\/td>\n

\n

Up to 7 days; refreshed when you publish<\/p>\n<\/td>\n<\/tr>\n

\n

Redirects (301, 302) and not-found (404) responses<\/p>\n<\/td>\n

\n

Yes, briefly<\/p>\n<\/td>\n

\n

301 up to 2 hours; 302 up to 20 minutes; 404 a few seconds for pages and a few minutes for files<\/p>\n<\/td>\n<\/tr>\n

\n

Pages for logged-in visitors, carts, and checkouts<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

—<\/p>\n<\/td>\n<\/tr>\n

\n

Error responses (5xx)<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Never stored; a copy cached earlier may be served instead while your website returns errors<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>

Static files are cached with a default lifetime of two hours when your website sends no Cache-Control<\/code> or Expires<\/code> header. The Content Delivery Network (CDN) follows the header when it does — s-maxage<\/code> applies to the CDN, max-age<\/code> to both the CDN and browsers. See Advanced CDN header management at Hostinger<\/a> for the directives.<\/p>

Because redirects are cached too, a redirect you have already corrected can keep being served from the edge for up to two hours. Flush the CDN cache<\/a> after changing redirects.<\/p>

How HTML pages are cached on web hosting<\/h2>

Hostinger CDN fetches HTML pages from your hosting server on every request by default and reports them as DYNAMIC in the x-hcdn-cache-status<\/code> header. Two things make the CDN cache a page.<\/p>

The LiteSpeed Cache plugin caches the page for the plugin’s public cache lifetime (the plugin default is 7 days, max-age=604800<\/code>) when it marks a page as publicly cacheable, and Hostinger CDN usually clears its cached pages when the plugin purges. Lowering Default Public Cache TTL<\/strong> in the plugin applies to pages cached afterwards; flush the CDN cache<\/a> to apply it to pages already cached.<\/p>

Cache headers from your application are cached for that time when a response carries Cache-Control: public<\/code> with a max-age<\/code> or s-maxage<\/code> value. Cache-Control: private<\/code>, no-store<\/code>, or no-cache<\/code> keeps the page out of the CDN cache.<\/p>

Requests carrying a WordPress login cookie or a WooCommerce cart or session cookie bypass the cache entirely, so logged-in users, customers with items in the cart, and the checkout always receive fresh pages from your server.<\/p>

NOTES<\/strong><\/p>