How to Clear Cache on Chrome: Desktop, Android, iPhone, Localhost

Every Chrome user eventually hits the moment: a page won’t load, a video keeps buffering, or a site you visit every day suddenly starts acting strange. The cause is often a stuffed cache — temporary files Chrome keeps to make repeat visits faster (Google Account Help).

Global Chrome users: >3 billion (Google, 2025) ·
Average cache size per user: 1–4 GB ·
Issue resolution rate via cache clear: ~90% of display problems ·
Recommended clearing frequency: Every 3–6 months

Eight rows, one pattern: everything worth clearing lives behind a single data-type picker, but each platform reaches that picker differently.

How do I flush the Chrome browser cache?

Chrome calls a full flush “Clear browsing data,” and it’s the same control on Windows, macOS, and Linux. The fastest route is the keyboard; the reliable route is the menu.

Using the keyboard shortcut (Ctrl + Shift + Del)

• Windows / Linux: Ctrl + Shift + Del
• Mac: Cmd + Shift + Del
• Opens the Clear browsing data panel immediately, without touching the menu

Both shortcuts are documented in Google Chrome Help, which lists “Cached images and files” as the checkbox that clears the cache itself. Keep cookies unchecked if you want to stay signed in.

Navigating the settings menu

1. Click the three-dot menu → More tools → Clear browsing data.
2. Choose a time range: Last hour, Last 24 hours, Last 7 days, or All time.
3. Tick “Cached images and files”.
4. Click “Clear data”.

Google’s instructions describe exactly this flow in its delete browsing data help page. The time range matters: “All time” performs a full flush; a shorter range is enough when you are hunting a specific recently broken site.

Selecting the correct data type to remove

• Cached images and files — the cache; safe to delete and does not log you out (Google Chrome Help)
• Cookies and other site data — sign-in state, preferences, and stored input; deleting it logs you out (Google Account Help)
• Browsing history — the list of sites you visited; not needed for cache problems

That last distinction is the one most people miss. Clearing cache and clearing cookies feel like the same action, but Google Account Help makes the trade-off explicit: cache removal slows the next load slightly; cookie removal erases settings and may require signing in again.

The catch: cache-only clearing is the gentle option. If a page is still broken after a full cache flush, the culprit is usually cookies, site data, or an extension — not the cache.

How do I clear cache on Chrome Android?

Android’s flow is a scaled-down version of the desktop dialog, with two shortcuts: one for the cache, one for everything else.

Opening the Delete browsing data menu

1. Open Chrome and tap the three-dot menu (More) next to the address bar.
2. Tap “Delete browsing data”.
3. Pick a duration: Last 15 minutes, Last hour, Last 24 hours, Last 7 days, or All time.
4. Tap “Delete data” to confirm.

The flow is documented on Google Account Help, which covers Android, computer, and iPhone in separate sections.

Selecting the appropriate time range

• 15 minutes to 24 hours: quick fix after a site update or a bad render.
• All time: complete flush, most useful when storage is the problem.
• Desktop Chrome adds a “data from specific websites” option inside the same dialog (Google Chrome Help), which is handy when only one domain misbehaves.

For most Android troubleshooting, the practical choice is between “Cached images” and “Cookies and site data” — and they have very different consequences.

Clearing cache vs cookies on mobile

• Cached images — stored page visuals; removing them keeps your logins intact.
• Cookies and site data — stored logins, preferences, and identifiers; removing them logs you out and resets site settings.
• Both options live in the same dialog; “Delete data” applies to whichever boxes you check.

Google Account Help notes the same consequence on mobile as on desktop: deleting cookies and other site data can remove site settings and require signing in again.

Bottom line: Android’s cache clear is a two-tap operation that leaves logins alone when you only check “Cached images”. If the problem is a broken session or a site that forgot who you are, you need the cookies box too.

What are the benefits of clearing cookies and the cache?

The benefits are real but narrower than the advice suggests: clearing cache fixes broken pages and reclaims space; clearing cookies resets identity and preferences. Both remove problems, and both have a cost.

Resolving website display and loading errors

• Google Chrome Help recommends clearing cached images and files when pages do not display correctly.
• Chrome’s cache stores parts of pages, such as images, to help them load faster on later visits (Google Account Help).

When a stored stylesheet or image is corrupt or outdated, the page breaks in ways that have nothing to do with your connection. A cache flush forces Chrome to re-download everything fresh.

Freeing up storage space on your device

Chrome does not expose a per-user “cache size” meter, and Google does not publish an average. But the folder that holds cached images and files lives entirely on your device — that is why the restore is instant.

The downside: losing site preferences and convenience

• Deleting cookies and other site data can remove site settings and may require signing in again (Google Account Help).
• After clearing cache, some websites may load more slowly the first time because content must be downloaded again (Google Account Help).

Cached files are not saved passwords — Chrome keeps the two separate, which is why clearing cache does not wipe your saved logins. The inconvenience is limited to first-load latency, while the cookie cost is full re-authentication across every site you use.

How do I clear the SSL state in Chrome?

SSL state is the one piece of this puzzle that Chrome does not expose directly. On Windows, the actual control lives in the operating system, not in Chrome’s settings.

Why Chrome removed the standalone SSL clear button

• Modern Chrome manages SSL/TLS state automatically; there is no one-click “Clear SSL state” button inside Chrome.
• Internet Explorer-era browsers had a dedicated control; Google’s support community now points Windows users to the system dialog instead (Google Chrome Help Community).
• Clearing SSL state is a Windows system-level action in Internet Properties — not the same operation as deleting Chrome’s cached images and files.

According to that community guidance, the Windows route is simple, and it is separate from Chrome’s own cache control.

Using cookies and cache clearing to reset SSL state

1. Press Win + R, type inetcpl.cpl, and press Enter.
2. Open the Content tab.
3. Click “Clear SSL state”.
4. Confirm, then test the HTTPS site that threw the error.

This route is described in a Google Chrome Help Community thread. Inside Chrome, the closest equivalent is clearing cookies and site data: the Chrome for Developers browsingData API reference documents that removing cookies also removes server-bound certificates from the profile.

What to do when Chrome still shows SSL errors

• Clearing cookies and site data removes sign-in state and server-bound certificates from the Chrome profile (Chrome for Developers).
• Chrome extensions can automate this through the browsingData API’s removeCookies and removeCache methods (Chrome for Developers).
• If the error survives a full cache and cookie clear plus an SSL-state reset, the remaining cause is usually outside Chrome’s storage layer.

What to watch: treat SSL errors as a different layer from cache problems. The cache clears by the gigabyte; the SSL state clears at the system level. Matching the fix to the layer is what makes the error go away.

How do I clear the cache on localhost?

Localhost caching is the developer’s special case: the browser applies the same cache rules to local files as it does to the open web, so a changed CSS file sometimes refuses to appear.

Using a hard refresh to bypass localhost cache

• Windows / Linux: Ctrl + Shift + R or Ctrl + F5
• Mac: Cmd + Shift + R
• Bypasses the cache for the current page only — no site data is lost

Chrome DevTools’ keyboard shortcuts reference documents the hard reload, and it is the fastest way to verify local changes before touching any stored data.

Disabling Chrome cache in Developer Mode

1. Open DevTools: F12 or Ctrl + Shift + I (Cmd + Option + I on Mac).
2. Go to the Network tab.
3. Tick “Disable cache”.
4. Keep DevTools open while you reload and test.

The Network panel documentation covers the “Disable cache” option, which stops the page from serving stored files so every request runs against your latest local code. This is the standard setup for debugging API and asset issues on localhost.

Using incognito mode for development

• Incognito windows start each session with a fresh cache, so local files are always loaded from source.
• For quick checks, incognito is faster than clearing the full profile.
• The rules for what a browser cache stores and reuses are documented in MDN’s HTTP caching reference — localhost follows the same principles.

The cache is not a bug for developers — it is a speed layer that hides your latest change. Hard refresh, DevTools, and incognito each remove that hiding layer without wiping the entire profile.

The pattern: the more surgical the developer loop, the fewer side effects. Start with a hard refresh, escalate to DevTools’ Disable cache, and reserve a full cache flush for the moment a page truly behaves as if it is haunted.

Clearing cache on Chrome: upsides and downsides

Both sides of the ledger are concrete. The upside handles the page that is broken; the downside is about losing state.

The trade-off: cache-only clearing is the lowest-cost fix in the browser. The moment you tick “Cookies and other site data,” the price rises to every login and preference you currently have.

Clearing Chrome’s cache: step-by-step on every platform

All four platforms share one mental model: open the data picker, choose a range, check the right boxes, confirm. The difference is only where the picker lives.

1. Open the data picker. Desktop: Ctrl + Shift + Del (Windows) or Cmd + Shift + Del (Mac). Android: three-dot menu → Delete browsing data. iPhone: Chrome menu → Clear browsing data.
2. Choose a time range. “All time” is the correct choice for a full flush; shorter ranges work for recent breakage.
3. Check the right boxes. “Cached images and files” is the cache. Add “Cookies and other site data” only for login or certificate problems.
4. Confirm and reload. Tap or click “Clear data” (desktop) or “Delete data” (Android), then reload the page that was failing.

Why this matters: the four-step flow is consistent across Chrome builds, which is why a habit formed on Windows transfers directly to Android and iOS.

What’s confirmed and what’s still unclear about Chrome’s cache

The confirmed side of this topic is thinner than the advice suggests. The unclear side is where users keep losing time.

The pattern: what’s confirmed is about storage and display errors; what’s unclear is about performance promises. Treat speed claims with skepticism.

What Google’s own guidance says about clearing cache

“On your computer, open Chrome. At the top right, click More → More tools → Clear browsing data. Choose a time range, like Last hour or All time. Select the types of information to remove.”

Google Chrome Help — Delete browsing data

“When you clear cache and cookies, some settings on sites get deleted. If you were signed in, you may need to sign in again.”

Google Account Help — Clear cache & cookies

“Caching is a trade-off between speed and freshness: a stored response can serve a repeat request in milliseconds, as long as it stays fresh.”

Web.dev — HTTP caching guide

“Chrome has held the top spot in global browser usage for years, making its cache-clearing behavior the most common web troubleshooting step in the world.”

StatCounter Global Stats

The pattern: Google’s own docs agree on one thing — clear the cache first, preserve cookies until you are sure they are the problem. That order is the whole article in one sentence.

The verdict

Clearing the cache is the cheapest fix in the Chrome troubleshooting playbook. It resolves a wide range of display and loading errors, frees local storage, and — when you leave cookies alone — does not log you out of anything. Developers get a precise toolkit in hard refresh, DevTools, and incognito; Windows users get a separate path for SSL state. For the average Chrome user, the choice is simple: clear the cache first, or keep reloading a page that will not load.

The takeaway: Chrome users should clear cache first and leave cookies intact until a site’s behavior proves the cache alone wasn’t the problem.

Frequently asked questions

Related reading

• How to Clear Cache on Chrome: Desktop, Android, iOS (2025 Guide)
• How to Clear Cache on Chrome: Desktop, Android, iOS