6 Chrome settings tweaks every power user needs to know

ZDNET published a column by Jack Wallen laying out six Chrome settings changes aimed at improving privacy and security and cutting down on interruptions, rather than adjusting appearance, tab handling or speed. Each recommendation comes with the exact menu path in Chrome's settings so readers can make the change quickly.
The first item is Chrome's Safe Browsing protection level, found under Settings, Privacy and security, then Security. Chrome offers three tiers. Enhanced Protection warns about dangerous sites, runs deeper scans of suspicious downloads, extends protection across Google services and sends the URLs a user visits to Google Safe Browsing. Standard Protection covers sites, downloads and extensions without that reporting. No Protection turns these safeguards off. Wallen notes that Enhanced is typically the default but recommends confirming it, and flags the trade-off: Enhanced sends more data to Google, so someone who weighs privacy as heavily as security could reasonably drop to Standard, which still blocks most threats.
Second is blocking third-party cookies, under Settings, Privacy and security, Third-party cookies. The column argues these cookies exist to build marketing profiles, follow users across sites and feed targeted advertising, and that blocking them reduces cross-site tracking, limits fingerprinting and closes off some security exposures. Wallen acknowledges the familiar cost: some sites break when third-party cookies are blocked, and suggests opening those in another browser that also blocks them. That advice will land differently for product teams than for individuals, since a browser that silently fails on a checkout or embedded login flow is a support problem, not a preference.
Third, location access. The path is Settings, Privacy and security, Site settings, Permissions, Location, where the setting "Don't allow sites to see your location" should be selected. The justification is personal safety: a web page that knows where you are can, in the wrong hands, reveal that you are away from home or help someone track your movements. Default-deny for location is a reasonable stance; the obvious cost is that mapping, local search and store-availability features lose precision unless you re-grant permission case by case.
Fourth, password saving. Under Passwords and autofill, then Google Password Manager, then Settings, the slider for "Offer to save passwords and passkeys" can be switched off. Wallen's argument is that a browser's built-in manager is not as safe as a dedicated tool such as KeePassXC, which keeps credentials in an encrypted vault and does not expose them to whatever page the browser happens to be showing. He concedes the inconvenience. This is a judgment call: built-in managers are convenient and sync across devices, but a separate vault narrows the attack surface by keeping stored credentials out of the browser process entirely.
Fifth, notifications. Under Settings, Privacy and security, Site settings, Notifications, the option "Don't allow sites to send notifications" should be checked. The reasoning is attention rather than security: every pop-up interrupts a task and costs time getting back into flow, so the author disables notifications across browsers, desktops and even phone lock screens, and chooses when to be distracted, usually after finishing something. For anyone building a web product, this is a reminder that notification permission prompts are often declined outright; email or in-app messaging may be the more reliable channel.
Sixth, downloads. Under Settings, Downloads, enabling "Ask where to save each file before downloading" returns control over where files land. Left alone, everything accumulates in the default Downloads folder, mixing installers, documents and disk images. Wallen, who downloads many .deb and .AppImage packages on Linux along with documents and ISO images, prefers to route each file to its proper place, which keeps the folder navigable and prevents unrelated items piling up.
Taken together, the list leans on defaults that favor convenience and Google's services over tight control, which is typical of mainstream browsers. Most of the changes are reversible and inexpensive to try, which is why this kind of checklist circulates widely. A likely trade-off is that a heavily locked-down browser fails quietly on some sites, so anyone applying all six at once should expect occasional breakage and know how to allow a specific exception rather than turning protections off wholesale.
Why it matters: IT administrators, support teams and developers who test in Chrome can adopt these settings as a baseline, but should be aware that blocking third-party cookies and notifications can change how their own sites behave for users who do the same. Product teams in particular may want to check that logins, payments and embedded content still work under these conditions, since a growing share of visitors will run a hardened browser. Treating strict defaults as a test case, rather than an edge case, is a reasonable inference from the direction these recommendations point.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
For improved privacy and security, fewer interruptions, and enhanced productivity, I highly recommend changing these default browser settings.