How do you block websites on Chrome with a password?

Install an extension that supports password protection — LeechBlock NG and BlockSite both do — add the sites you want blocked, then set a password or access code that's required to edit the list or turn blocking off. The catch is that the password guards the extension's settings, not Chrome itself. Anyone can still disable the whole extension from chrome://extensions without entering it, so treat the password as friction, not a lock.

Can you password-protect a website block in Chrome for free?

Yes. LeechBlock NG is free and open-source and lets you require an access code or a typed sentence before its options can be changed. BlockSite has a free tier with password protection, but it caps you at three sites and asks for an account. Neither password stops someone from opening chrome://extensions and switching the extension off, so the protection is real but shallow on any browser extension.

Why isn't a password on a Chrome blocker enough to stop me?

Because the password only locks the extension's settings page. Chrome itself lets you disable or remove any extension from chrome://extensions in two clicks, and that action never asks for the blocker's password. You can also open the site in Safari, Firefox, or an incognito window where the extension isn't running. The password raises a small wall around one door while leaving several others open.

What actually stops me from bypassing a Chrome block?

Friction you'll feel before you act, plus moving the block below the browser. A typed access code or a forced delay buys a few seconds for the impulse to pass, which is often enough. For real resistance, block at the operating-system level instead: a desktop tool blocks across every browser at once and doesn't sit in chrome://extensions, so switching it off takes deliberate effort rather than a quick toggle.

Does Focuh use a password to block sites on Chrome?

No, and that's deliberate. The Focuh Chrome extension blocks your chosen sites during a self-imposed challenge and logs an attempt counter every time you reach for one, rather than hiding behind a password you'd just enter when motivated. It's free with no account, no telemetry, and no three-site cap. If you want blocking that's genuinely hard to switch off, the free Focuh Mac app blocks at the system level instead.

Can I set a password so I can't unblock a site early?

You can set an access code in LeechBlock NG that's required to change its settings before a scheduled window ends, which discourages early unblocking. But no Chrome extension can stop you from disabling it outright at chrome://extensions, so a determined version of you always has a way out. For blocking that resists early exit, an operating-system-level tool with permission-based friction is far more reliable than any in-browser password.

Should I use a password blocker or a system-level blocker?

Use a password-protected extension if your distraction lives entirely in Chrome and you mainly need a speed bump. Use a system-level blocker if you switch browsers to escape, open native apps, or need the block to hold during a long stretch of work. On a Mac, the free Focuh app blocks every browser and native app in one session and is much harder to disable mid-session than any extension.

Chrome extensionwebsite blockerpasswordfreefocus

How to Block Websites on Chrome With a Password (Free)

June 23, 20269 min readFocuh

Trying to block websites on Chrome with a password usually means one thing: you don't trust yourself to leave the block alone. To do it, install an extension that supports password protection — LeechBlock NG and BlockSite both do — add your sites, and set a password or access code that's required to change the settings. The honest catch is that the password guards the extension's options, not Chrome itself, so anyone can still disable the whole extension from chrome://extensions without ever typing it.

This guide shows you exactly how to set up a password-protected block, why it's weaker than it looks, and what to do when you need a block that actually holds.

How to block websites on Chrome with a password

The two free extensions that offer this are LeechBlock NG and BlockSite. LeechBlock NG is the better pick if you want it free with no account.

With LeechBlock NG:

Install LeechBlock NG from the Chrome Web Store.
Open its options and create a block set — add the domains you want blocked, like reddit.com and youtube.com.
Open General Options → Options Protection and turn on an access code or a typed-sentence requirement.
Save. Now the options page asks for that code before anyone can edit your block sets or schedules.

With BlockSite:

Install BlockSite and create the account it requires.
Add up to three sites on the free tier.
Open Settings → Password Protection and set a password.
Confirm. Editing the blocklist now needs the password.

Either way, you've password-protected the settings. That's the part most "block websites on Chrome with a password" guides quietly skip over.

Why a password on a Chrome blocker is weaker than it sounds

Here's the part worth being blunt about. A password on a Chrome extension locks the extension's own options page. It does not lock Chrome. And Chrome gives you a master switch the password can't touch.

Open chrome://extensions, find the blocker, and flip the toggle off. Chrome doesn't ask for the extension's password to do that — it's a browser-level control, not an extension-level one. The block is gone, password and all. There are two more open doors next to it:

Another browser. The block only runs in Chrome. Open the same site in Safari, Firefox, or Arc and nothing stops you.
Incognito. Unless you've explicitly allowed the extension in incognito mode, an incognito window runs without it.

So the password raises a small wall around one door while leaving three others wide open. For a casual speed bump that's fine. As a lock, it isn't one.

What a password on a Chrome block actually buys you

Friction — and friction is genuinely useful, as long as you're honest about what it is. The value of an access code isn't that it's unbreakable. It's that the five seconds spent finding chrome://extensions, or typing a sentence you set up while motivated, is often enough for the impulse to pass. Most distracted browsing is autopilot, not a considered decision. Anything that interrupts the reflex tab-open does real work.

What a password can't do is win against a determined you. If you've decided you're getting to that site, you will. That's true of every browser extension, password or not, which is why the better question isn't "how do I lock the extension" but "where should the block live so it's harder to reach around."

Focuh: free Chrome blocking without the password theater

Focuh takes a different angle. Instead of hiding the block behind a password you'd just enter the moment you wanted out, it blocks your chosen sites during a self-imposed challenge and keeps an attempt counter. Every time you reach for a blocked site out of habit, Focuh redirects you to a calm page and logs it.

That counter is the part a password can't give you. Seeing that you opened X eleven times on Monday and twice by Friday is feedback that changes behavior, where a password just stands there daring you to bypass it. Focuh is free with no account, no telemetry, no ads, and no three-site cap, and your blocklist stays in local Chrome storage.

It's not pretending to be a vault. Like any extension, it can be switched off at chrome://extensions. The design bet is that interruption plus visible feedback beats a flimsy password — but if you genuinely need a block that resists you, that has to live below the browser.

When you need a real lockout instead of a password

If a password is really code for "I can't be trusted to leave this alone during work," a browser extension is the wrong layer. You want operating-system-level blocking.

On a Mac, the free Focuh desktop app blocks at the system level using macOS Accessibility APIs. Start a focus session and your blocked sites are unavailable in Safari, Chrome, Firefox, and Arc at once, plus any native app you've added. It doesn't appear in chrome://extensions, so there's no quick toggle — disabling it mid-session means digging into System Settings to revoke a permission, which is exactly the deliberate friction a password is meant to imitate but can't.

If you want blocking strong enough to survive even an uninstall attempt, that's Cold Turkey's territory on Windows and Mac, with locked modes you genuinely can't exit early. Weigh how much enforcement you actually need against how much you want to pay.

Chrome extension vs system-level blocking

What you want	Password-protected Chrome extension	System-level blocker
Blocks sites in Chrome	Yes	Yes
Blocks Safari / Firefox / Arc	No	Yes
Blocks native desktop apps	No	Yes
Survives `chrome://extensions` toggle	No	Yes
Cost	Free (LeechBlock)	Free (Focuh for Mac)
Hard to disable mid-session	No	Yes

The pattern is clear: a password makes one door slightly stickier, while a system-level block closes the whole row of doors at once. If you only ever drift inside Chrome, the extension is enough. If you bypass by switching browsers, the password was never the thing standing in your way.

Which approach should you choose?

You drift inside Chrome and want a speed bump — use LeechBlock NG's access code, free and flexible. The best free website blocker for Chrome roundup compares the options.
You want feedback, not a password — use Focuh and watch the attempt counter drop week over week.
You bypass by opening Safari or a native app — move the block to the OS with the free Focuh Mac app. The system-level vs browser blocking explainer covers why.
You need unbreakable, can't-exit-early blocking — look at Focuh vs Cold Turkey and decide what enforcement is worth to you.

A password on a Chrome blocker isn't useless — but it's a speed bump dressed up as a gate. If a speed bump is all you need, set one up in two minutes. If you need the block to actually hold, stop reaching for a password and move the block somewhere the browser can't switch off.