How-To

How to Clear WordPress and Hostinger Cache Properly

Clear WordPress, LiteSpeed, Hostinger server, CDN and browser caches without randomly deleting files.

How to Clear WordPress and Hostinger Cache Properly
Quick answer

Purge the WordPress cache plugin first, then Hostinger/server cache, then CDN cache, and finally hard-refresh or use a private browser window.

A WordPress site can have several caches at once. Clearing only one may leave an old page visible, so it helps to know which layer you are purging.

Clear WordPress and Hostinger cache illustration
TechGuru illustration

1. Purge the WordPress cache plugin

For LiteSpeed Cache, use LiteSpeed Cache → Toolbox → Purge → Purge All. Hostinger documents both the WordPress-admin method and advanced alternatives in its LiteSpeed guide.

2. Flush Hostinger cache

In hPanel, open the site and check WordPress → Overview for the cache-flush control. Hostinger’s general cache guide also covers browser and hosting layers.

3. Purge CDN cache

If a CDN is enabled, purge it separately. CDN caching is not necessarily cleared by a WordPress plugin purge.

4. Refresh your browser

Hard-refresh or use a private window. If another device sees the new page while yours does not, local cache is the likely culprit.

When developing

Do not repeatedly purge caches if you can temporarily use an appropriate development mode. Re-enable normal caching when the editing session is finished so visitors receive the performance benefit.

Cache-layer checklist

Use the symptom to choose the next check instead of changing several settings at once. Make one change, retest the exact URL, and keep a note of what changed.

Symptom What it suggests Next check
Browser Only your device is stale Hard refresh or private window
WordPress plugin Logged-out page is stale Purge the cache plugin
Hostinger/server Several devices are stale Flush hosting cache
CDN Different regions remain stale Purge CDN cache

Before you make a risky change

Take a current backup or restore point before editing configuration files, permissions, PHP settings or database URLs. Avoid deleting unrelated DNS, email, security or rewrite rules simply to see whether the problem disappears.

How to confirm the fix

Retest the exact public URL in a private browser window and, where relevant, on a second device or network. A fix is only confirmed when the original symptom is gone without creating a new error elsewhere on the site.

Keeping this guide accurate

Technology changes quickly. We review and update guides when products, pricing or recommendations materially change.