Method 1 — A blocking extension
The Chrome Web Store has dozens of site-blocking and adult-filtering extensions. Install one, add a password, and Chrome refuses the sites on its list. Two minutes.
Where it stops, in order of how fast people find it:
- Incognito. Extensions are off in incognito windows by default. Unless you explicitly allow the extension in incognito, a private window has no filter at all.
- Remove it.
chrome://extensions, Remove. A "password to uninstall" is a screen the extension draws; Chrome itself never asks for it. - A new profile. Chrome profiles are separate: a fresh profile has no extensions.
- Another browser. Edge is already installed on Windows, Safari on Mac.
An extension is a reminder that lives inside the thing it's supposed to restrain. Why private windows walk through it, layer by layer: does incognito bypass porn blockers.
Method 2 — Lock SafeSearch
Google's SafeSearch hides explicit results in Search and Images. You can turn it on at google.com/safesearch, but on a device you control it's a toggle. The reliable way to lock it is at DNS level: when www.google.com resolves to Google's forcesafesearch.google.com address, every Google search from that device is filtered, in any browser, in any profile, in incognito. Bing and DuckDuckGo have the same mechanism. That's how SELFCNTRL enforces safe search: not a Chrome setting, a DNS answer.
Method 3 — Chrome's own management policies
Chrome can be managed like a company browser. On Windows, the URLBlocklist policy in the registry (HKLM\Software\Policies\Google\Chrome\URLBlocklist) and on Mac the same key in a managed preferences plist block domains Chrome will not open, and the user can't remove them from inside Chrome. IncognitoModeAvailability = 1 removes incognito entirely. It's a real block for Chrome, and it's how schools and businesses do it.
Where it stops: you're the administrator of your own computer. The registry key or the plist that you wrote, you can delete. And it's Chrome-only, by design.
Method 4 — A filtering DNS, under Chrome
Every request Chrome makes starts with the same question to the system: "where is this domain?" A DNS category filter refuses pornography at that step. The site never resolves, in Chrome, in incognito, in a new profile, in Edge, in an app that isn't a browser. The browser is no longer the thing you're fighting.
One Chrome-specific detail matters here. Chrome can use its own encrypted DNS (Secure DNS, under Privacy and security) and skip the system resolver. In its default "automatic" mode Chrome only does that when the system resolver is one of the public providers it knows; a filtering resolver that isn't on that list keeps Chrome on the system path. But the second option, "With: custom provider", lets anyone type in a resolver of their choice, and Chrome will use it. That's a door, and it's in Chrome's own settings. (Firefox has the same feature, and honours a network canary domain,use-application-dns.net, to switch it off.) The whole mechanism, including the three ways around plain DNS filtering: DNS porn blockers explained.
What holds: the filter you can't switch back
Every method above shares one flaw: on your own computer, you hold the key. SELFCNTRL is the DNS filter from method 4 attached to your account instead of to a setting. On Mac and Windows it installs in a few minutes, enforces safe search, and adds curfews that cut the internet on a schedule. Tightening takes effect at once; loosening waits twenty-four hours, and the floor you set never drops. That delay is the difference between a block and a toggle.
On iPhone and iPad, Chrome is just another app under a supervised profile that can't be removed and can't be joined by a VPN. Chrome on iOS doesn't even have its own DNS setting to fight. The device steps: Windows, Mac, iPhone.
Chrome, side by side
| Extension | SafeSearch toggle | Chrome policy | DNS filter (account-locked) | |
|---|---|---|---|---|
| Blocks sites in Chrome | Yes | Results only | Yes | Yes |
| Survives incognito | No (off by default) | No | Can remove incognito | Yes |
| Survives a new profile | No | No | Yes | Yes |
| Covers Edge, Safari, apps | No | No | No | Yes |
| Off in under a minute | Yes | Yes | Yes (you're admin) | No (24-hour delay) |
Questions
Do Chrome extensions work in incognito?
Not unless you allow them one by one under chrome://extensions → Details → Allow in Incognito. By default a private window runs with no extensions, which is why an extension-based blocker is bypassed by Ctrl+Shift+N.
Can I block porn on Chrome for Android?
Chrome on Android follows the device's DNS (Private DNS in Android settings) and Google's SafeSearch lock at DNS level. SELFCNTRL doesn't cover Android today: it locks iPhone, iPad, Mac and Windows. The methods above still apply to Chrome on a computer.
Does Chrome on iPhone bypass Screen Time?
Screen Time's "Limit Adult Websites" applies to Safari and to apps that use Apple's web view; Chrome on iOS uses that web view, so it is generally covered, but the restriction is still undone by the Screen Time passcode. A DNS filter under a supervised profile covers Chrome without depending on that.
What about Chrome's Secure DNS setting?
Chrome can resolve domains over its own encrypted DNS and skip the system resolver. Google designed a canary: if the network's resolver refuses use-application-dns.net, Chrome uses the system resolver instead. A filtering resolver that answers that way keeps Chrome inside the filter.