Clear Cache Chrome Android Without Losing Passwords

Delete only cached files. Leave Cookies and site data, Saved passwords, Autofill form data, and other account-related boxes unchecked unless you deliberately want Chrome to forget those records.

That is the decision rule. Chrome's cache holds copies of images, scripts, style sheets, and other website files so pages can open faster on later visits; cookies and site data carry login sessions and site preferences. Google's Chrome support documentation treats these as separate categories of browsing data for good reason.

Choose Cached images and files when a website looks stale, displays broken formatting, or keeps loading an old asset. Select cookies only when the problem appears tied to a login session, consent prompt, shopping cart, or other site state. Clearing history is irrelevant to most rendering faults.

Check one box. In Chrome's Delete browsing data screen, select Cached images and files alone, then confirm the deletion after checking every other visible category.

1. Open the Chrome app on your Android device.
2. Tap the three-dot menu.
3. Select Delete browsing data. On some versions, open History, then tap Delete browsing data.
4. Open More options or the Advanced tab if Chrome shows a simplified screen.
5. Set the time range to All time for a complete cache reset, or choose a shorter range if the fault started recently.
6. Select Cached images and files.
7. Clear the check marks beside Cookies and site data, Saved passwords, Autofill form data, Browsing history, and Site settings.
8. Tap Delete data, then confirm.

Read the final selection twice. Chrome remembers parts of the previous selection on some interfaces, so do not assume that only the cache box is active merely because that is what you intended to clear.

No, if cache is all. Deleting only Cached images and files should leave open tabs, saved passwords, browsing history, and website sign-in cookies in place, although each page may reload its images and scripts.

Sign-outs usually follow the deletion of Cookies and site data, not the cache itself. Passwords are a separate category again: removing a login cookie ends the current site session, while deleting a saved password removes Chrome's stored credential used to fill the form.

Tabs are separate too. They may refresh when revisited because their cached resources have gone, but clearing cached files is not the same command as closing tabs or clearing Chrome's app storage.

Start with one website. If one domain is broken while other sites behave normally, deleting that site's stored data is more precise than wiping browsing data for the entire browser.

Open Chrome, visit the affected website, tap the icon to the left of the address bar, and inspect Cookies and site data or Permissions, depending on the installed Chrome version. The exact menu labels change, but the useful distinction does not: a specific-site reset limits collateral damage, while an all-time cache clear forces every website to download fresh files.

There is a catch. Removing a specific site's data can sign you out of that site because the operation may include its cookies, not merely cached images. Use the global Delete browsing data screen with only Cached images and files selected when preserving site access matters more than targeting one domain.

Use it for stale assets. A cache reset is a sensible fix when one or more pages show old images, malformed styling, obsolete JavaScript, or content that works in an Incognito tab but not in the normal browser.

It is a weak fix for network outages, DNS failures, certificate warnings, exhausted device storage, disabled JavaScript, server errors, or an outdated Android System WebView. If Chrome reports ERR_NAME_NOT_RESOLVED, for example, cached website files are not the first suspect because the browser failed to resolve the address.

Run a quick check first:

• Reload the page once.
• Open the same address in an Incognito tab.
• Try another website.
• Switch between Wi-Fi and mobile data.
• Check Chrome and Android System WebView for updates in Google Play.
• Clear cached images and files only if the evidence points back to stored browser content.

Cache deletion also frees some storage space, but the gain is temporary because websites create those files again as you visit them.

Yes, when Chrome misbehaves broadly. Android's per-app Clear cache control is appropriate when Chrome crashes, refuses to launch properly, or has a damaged cache that cannot be removed from the browser menu.

Open Settings > Apps > Chrome > Storage & cache > Clear cache. Names vary slightly across Samsung, Pixel, and other Android devices, but the dangerous neighboring control is usually unmistakable: Clear storage, Clear data, or Manage storage.

Do not tap that neighbor casually. Android separates cache files from persistent app data, and its app-specific storage model↗ explains that cache files are disposable while other files hold longer-lived state. Clearing Chrome's storage can reset the app and remove local settings or unsynced data; what clearing app data changes is a different operation from emptying its cache.

Stop repeating the wipe. If a complete cache deletion changes nothing, check site data, service workers, extensions on synchronized desktop devices, the network, and the website's own server or content-delivery cache.

For one stubborn website, compare normal and Incognito tabs, then try another browser such as Firefox on the same phone. If Firefox receives the same old page, the origin server, a proxy, or a CDN may be serving it; deleting Chrome files again cannot resolve a copy created outside your device.

If only Chrome fails, update the app through Google Play, restart the device, and inspect available storage. Google's Android Chrome listing↗ is the proper update source. I would not clear all Chrome storage until passwords and other important browser data are confirmed as synchronized, because that larger reset creates more recovery work than most page faults justify.