How to clear cache on Android in Chrome without signing yourself out

The three things people mean by "cache"

Almost every "clear the cache" instruction that ends badly is someone tapping Clear storage when they meant Clear cache. The two buttons sit next to each other, they are worded almost identically, and only one of them is reversible in any practical sense. That is the only real risk in how to clear cache on Android, and it is entirely avoidable.

Clearing one app's cache from Android settings

1. Open Settings, then Apps.
2. Choose the app. Tap See all apps if it is not in the short list.
3. Tap Storage & cache.
4. Tap Clear cache. Leave Clear storage alone.

Wording shifts between manufacturers. Samsung nests it under Storage; some builds say Clear data where stock Android says Clear storage. The two-button shape is consistent everywhere, and the destructive one is always the second. Those four taps clear app cache Android is holding for that one app, and nothing else on the phone is touched.

There is no system-wide "clear all caches" button in current Android. It existed years ago, was removed, and the manufacturer "phone cleaner" tools that offer to replace it mostly delete the same caches Android would have reclaimed on its own. Per-app is the route that does what you asked and nothing else.

How to clear cache on Android inside Chrome

Clearing Chrome's app cache from Android settings and clearing your browsing data inside Chrome are different operations on different stores. For the second:

1. Open Chrome, tap the three-dot menu, then Settings.
2. Go to Privacy and security, then Delete browsing data.
3. Tick Cached images and files only, if you want to keep your sign-ins.
4. Set the time range, then confirm.

Chrome separates Browsing history, Cookies and site data and Cached images and files precisely because they have different consequences. The Advanced tab adds saved passwords, autofill data and site settings, which are rarely what anyone actually intends to remove and are very easy to tick by accident.

If you are signed into Chrome, clearing cookies signs you out on that device but does not touch the same data on your other devices unless sync propagates it. Check what is being synced before assuming a clear is local. Google’s own page on deleting browsing data in Chrome lists what each tick box covers on Android.

Doing it for one site instead of all of them

Usually the problem is one misbehaving site, and clearing everything to fix it is disproportionate. Chrome can scope the operation: under Settings → Site settings → All sites, pick the site and clear its data alone. Your other sessions survive untouched.

This is almost always the right move for a page stuck on an old layout, a checkout that will not proceed, or a login loop. It is faster than the blanket clear and it costs you nothing elsewhere.

Work out which clear you need first

Most searches for how to clear cache on Android are really one of the five symptoms below. The symptom tells you which store is at fault, and picking correctly avoids signing yourself out of everything for no reason.

The fourth row is the most useful diagnostic on the list. If a page behaves correctly in a private tab and incorrectly in a normal one, the difference between them is precisely the stored data, which tells you the problem is yours to clear, and which store to clear, without guessing.

The other browsers on an Android phone

Most Android phones have at least two browsers installed and the menus do not match.

Samsung Internet puts it under Settings → Personal browsing data → Delete browsing data, with the same separation between cached files and cookies. Firefox uses Settings → Delete browsing data and adds something the others lack: Delete browsing data on quit, which applies the chosen categories automatically every time you close the app. If you find yourself clearing manually every few days, that setting is the actual answer.

A browser installed as a system app may also keep a second, separate profile for a work account. Clearing one profile does not touch the other, which explains the occasional case where a site is fixed in one place and still broken in another on the same phone.

Each browser keeps its own copy

Caches are not shared between browsers, and neither is anything else. The browser cache Android reports under Storage is per app, never per phone: Chrome, Firefox and Samsung Internet each hold their own cache, their own cookies and their own site data, in their own app storage. That is why a page that looks stale in one and fresh in another is not evidence of a network problem: you are simply reading two independent copies of the same file, saved at different times.

This makes the second browser a useful diagnostic before you clear anything. If the page is correct there, the copy in the first browser is stale and clearing its cache is the right move. If it is wrong in both, nothing on the phone is at fault and something upstream is serving the old version. A private tab in the same browser is a faster version of the same test, since it starts with an empty store, though it will still use the shared HTTP cache for some resources.

The same independence applies to signing out. Clearing cookies in one browser leaves your sessions in the others untouched, which is occasionally the answer to a problem rather than a complication: if a site has locked itself into a bad session, opening it in the other browser gets you working again without clearing anything at all.

What the cache actually is

Every page you load is dozens of separate files: the document, stylesheets, scripts, fonts, images. Most of them do not change between visits, and most of them are shared across many pages of the same site. Re-downloading them every time would waste both your data and the server's, so the browser keeps copies and re-uses them until the server's own rules say they have expired.

This is why a stale page is the classic cache symptom. The site published a new stylesheet, your browser is still holding the old one because it was told the old one was good for a month, and the result is a page assembled from two different versions of itself. Clearing forces a fresh fetch and the mismatch disappears.

It also explains why clearing costs so little. Nothing in the cache is unique to you and nothing in it is irreplaceable — by definition, every item is a copy of something the server will hand over again on request.

Nor is the cache one flat pile. The browser keeps separate stores for page resources, for fonts, for compiled scripts and for prefetched navigations, and the single tick box in the settings screen empties all of them together. That is worth knowing only for the consequence: the first page you open after a clear is slower than usual by a noticeable margin, and that is the cache being rebuilt rather than anything having gone wrong.

Cache is not the only thing sites store

Modern sites keep more than cached copies. A site installed to your home screen as an app can hold an offline database, a service worker that serves pages without touching the network, and its own storage quota that survives an ordinary cache clear. This is deliberate: it is what lets a mail or maps site work with no connection.

When a site behaves strangely and a cache clear changes nothing, that stored layer is usually why. Clearing cookies and site data for that one site removes it, at the cost of signing you out there, which is the trade to make knowingly rather than by clearing everything and hoping.

Service workers keep a copy of their own

There is a second cache that the browser cache screen does not cover, and it explains most of the cases where a page stays stale after a clear. A site can install a service worker: a small script that sits between the page and the network and answers requests from its own store, which is how a site keeps working offline and why some sites open instantly on a bad connection. That store is site data, not cache, so ticking cached images and files leaves it exactly where it was.

The symptom is specific enough to recognise. The page loads immediately, looks like a version from days ago, and a hard reload changes nothing, because nothing is reaching the network. The fix is to clear that one site's data rather than the browser's cache, from the padlock or tune icon in the address bar, then reload. Installed web apps added to the home screen keep the same store, so uninstalling and re-adding the shortcut achieves the same thing for those.

What Android's storage screen is telling you

Under Settings → Storage Android reports two numbers per app, and reading them the wrong way round is what sends people to the wrong button. The cache figure is disposable: Android may reclaim it on its own when space runs short, and it will refill as you use the app. The user-data figure holds accounts, settings, downloads registered by the app and the site data described above, and nothing reclaims it automatically.

A browser cache Android displays as several hundred megabytes is doing its job rather than misbehaving, and a cache figure that rebounds within a day is normal and not a fault. A browser holding a large user-data figure usually means a lot of site data rather than a lot of history, since text records are small; offline maps, installed web apps and media stored by sites are what move that number. If storage is genuinely tight, that is the figure to inspect app by app, and the honest answer is often that a single app is holding most of it and clearing every cache on the phone would not have helped.

When clearing the cache is the wrong fix

A cache clear is a reasonable first move for a page that renders stale, a site stuck on an old version of itself, or an app misbehaving straight after an update. Those are genuine cases and it genuinely resolves them.

It is not a storage fix. Android treats cache as reclaimable space and frees it automatically under pressure, so when you clear app cache Android would have reclaimed anyway, the megabytes return within days and the phone is no emptier than before. If storage is the real problem, the things taking the room are video, photos and apps you do not open.

It is also not a privacy measure. Clearing removes what has already been written; preventing it from being written is private browsing, and changing what gets stored by default is a matter of browser settings — particularly the third-party cookie rule, which decides how much there is to clear in the first place.