Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To clear the Hostinger CDN cache, sign in to hPanel and open Websites → Dashboard → Performance → CDN for the site, then click Flush cache. On Agency hosting, choose CDN directly in the sidebar. Hostinger says the action invalidates cached copies for the whole website within seconds; it does not clear browser, server, or WordPress plugin caches.
Flush the CDN cache in hPanel
- Sign in to hPanel and open Websites.
- Click Dashboard beside the website you updated.
- In the sidebar, select Performance → CDN. On Agency hosting, select CDN directly.
- Click Flush cache.
The flush applies to the entire website, not just one page or file. Hostinger says it takes effect within seconds. Hostinger’s CDN cache guide explains the operation and its scope.
Check whether the CDN is serving the updated content
To inspect a response, open your browser’s developer tools, select Network, click the page or file request, and look under Response Headers for x-hcdn-cache-status. You can also review CDN Analytics in hPanel. Hostinger documents these status values:
- HIT: The response came from CDN cache. Flush the CDN or use Development mode while actively editing.
- MISS: The request fetched content from the website. Make the request again if you want to see whether the response is subsequently cached.
- EXPIRED: The cached copy expired and was fetched again.
- DYNAMIC: The response is not cacheable.
- BYPASS: The CDN cache was skipped, for example while Development mode is on.
- REVALIDATED: The cached content was refreshed.
A first request after a flush may show MISS or DYNAMIC. If a response is MISS or DYNAMIC but still looks old, check other cache layers before blaming the CDN.
Use Development mode only while editing
Development mode tells Hostinger CDN to skip its cache and fetch content from the website on each request. Turn it off when you finish editing so CDN caching can resume. This setting does not disable LiteSpeed server cache or a WordPress caching plugin.
Identify which cache may still contain the old version
A CDN flush only clears the Hostinger CDN layer. Pages and files may also be cached by your browser, LiteSpeed on the server, or a WordPress plugin. Hostinger recommends keeping only one WordPress caching plugin active.
Browser cache
Try a private or incognito window, or force a fresh load with Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsLiteSpeed server cache
In the website dashboard, open Cache Manager and purge the cache. Hostinger describes Cache Manager as controlling LiteSpeed web server cache; it can clear the whole site or a specific URL. This is separate from the CDN flush.
Rank #3
WordPress plugin cache
Use the plugin’s own purge control. Hostinger says LiteSpeed Cache purges usually clear Hostinger CDN pages too, but flushing the CDN is the reliable step if the update remains missing. Keep only one caching plugin active.
No-cache preview
Hostinger’s help guide describes a no-cache preview in hPanel that bypasses applicable LiteSpeed, CDN, and server-side cache layers. If the preview shows your change, cached content is likely involved.
Another CDN
If your site uses a third-party CDN rather than Hostinger CDN, clear the cache from that provider’s dashboard. The steps above apply to Hostinger CDN.
Why some files or pages are cached differently
Hostinger’s caching guide, updated in 2026, describes these behaviors for its products. The durations below are product-specific limits or defaults, not guarantees that every response will be cached for the full period.
| Content or setup | Documented Hostinger behavior |
|---|---|
| Static files on Hostinger CDN | Images, CSS, JavaScript, fonts, and downloads are cached by default for up to two hours, or for the period specified by the site’s cache headers. |
| Optimized or resized images on web hosting | Cached by default for up to 30 minutes, subject to the original image’s cache headers. |
| HTML on web hosting | Cached only when the site marks it cacheable; Hostinger reports HTML is DYNAMIC by default. |
| Hostinger AI Builder sites | The site, including HTML, is cached for up to seven days. The cache refreshes automatically when changes are published; manual cache settings are not available. |
For a response to be cacheable, Hostinger says its headers can use Cache-Control: public with max-age or s-maxage to set a duration. private, no-store, or no-cache keeps a page out of CDN cache. WordPress login cookies and WooCommerce cart or session cookies bypass the CDN cache.
Hostinger also documents LiteSpeed Cache as able to mark public pages cacheable for the plugin’s configured public cache lifetime. Its guide gives seven days, or max-age=604800, as the plugin’s stated default. Changing the plugin’s default public cache lifetime affects pages cached afterward; flush the CDN to apply the new setting to pages already cached.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
