Why blocking Chrome specifically
Chrome on iOS has a few properties that make it worth targeting directly. First, it syncs open tabs, browsing history, and bookmarks with your Google account and any desktop or Android device you use. That cross-device continuity lowers the cost of picking up where you left off -- you open the app and the rabbit hole you left yesterday is sitting there waiting. Second, Chrome's address bar doubles as a search box, which means "looking something up quickly" and "opening a browser tab" are the same gesture. The friction that normally separates search intent from full browsing sessions is gone. Third, Incognito mode hides sessions from the Chrome history view, which can make it easier to rationalise usage that you would otherwise see accumulating.
It is worth being clear about one important fact before you start: Screen Time limits on Chrome alone will not block browsing. Safari is the default browser Apple ships with iOS and it is not removable. If you cap Chrome and leave Safari uncapped, you have not blocked the behaviour -- you have just changed which app you open to do it. Any effective Chrome block therefore has two parts: deal with Chrome, then deal with Safari too.
The good news is that iOS Screen Time includes a Web category under App Limits that covers all browsers simultaneously -- Chrome, Safari, Firefox, Edge, and any other third-party browser. Setting a limit there is more durable than targeting apps individually and survives you switching browsers mid-day.
Method 1: Delete Chrome
How: Hold the Chrome icon > Remove App > Delete App. Chrome is gone from your phone. Your bookmarks and open tabs remain in your Google account and will be there when you reinstall.
Strength: 2/10 on its own. Reinstalling Chrome from the App Store takes under a minute. The only mechanism at work is friction, and friction collapses under a genuine urge. Deleting Chrome also does nothing about Safari.
The cross-device wrinkle: because Chrome syncs with your Google account, any tabs you had open on desktop remain there waiting. If your actual browsing problem is desktop Chrome, deleting the iOS app solves the wrong half. Audit where the usage actually happens before committing to this.
When to use: as a 7-day experiment to see whether you actually want Chrome off your phone or just feel like you should. If you reinstall within 48 hours, the underlying pull is stronger than this method handles. If you stay off it for a week and feel better, keep it deleted and tackle Safari separately.
Method 2: App Limit on the Web category
How: Settings > Screen Time > App Limits > Add Limit > tap the "Web" category (do not expand it to individual apps -- tap the category row itself) > Next > set your daily limit (15 minutes, 30 minutes, or 1 minute if you want a near-hard block) > Add.
Why the Web category matters: this single limit applies to every browser installed -- Chrome, Safari, Firefox, DuckDuckGo, Edge, all of them. The minute countdown is shared across all of them. If you use 10 minutes in Safari and 10 minutes in Chrome and your limit is 15 minutes, you hit the block after 15 minutes total. This is the right surface to target if you want to reduce browsing without caring which app you open to do it.
The Incognito note: Chrome's Incognito mode does not bypass Screen Time limits. The timer runs regardless of whether the tab is incognito or not. Screen Time measures foreground app usage, not browser history, so private browsing provides no escape from the limit.
Strength: 2/10 without a passcode ("Ignore Limit For Today" is two taps); 7/10 with a Screen Time passcode you do not know.
When to use: first serious attempt at reducing browsing time. Cheap, fast, and covers all browsers in one setting. If you bypass the limit on the first day, escalate to Method 3.
Method 3: Screen Time passcode
How: Settings > Screen Time > Use Screen Time Passcode > set a 4-digit code different from your unlock passcode. Combine this with the Web category App Limit from Method 2. The "Ignore Limit For Today" button now requires entering the Screen Time passcode before it will let you through.
Strength: 5/10 if you know the passcode and just have to enter it yourself; 9/10 if you do not. The most realistic version of "do not know it": ask a partner, parent, sibling, or close friend to set the code on your behalf without telling you what it is. They are the override authority. You can ask them to let you through for a specific reason, but the decision is theirs.
The address-bar problem: Chrome's combined search-and-address bar is one reason browsing sessions spiral. You open Chrome to look something up, the search results contain links, the links contain more links, and 45 minutes have passed. The limit does not prevent this spiral -- it just stops it at the wall. The passcode keeps that wall solid when your in-the-moment self would otherwise knock it down.
When to use: after Method 2 has failed (you bypassed the limit within a week). The passcode-held-by-someone-else is one of the cheapest hard commitment devices available. No apps to buy, no hardware, just a relationship with someone who will not give you the code back in a low-willpower moment.
Method 4: Content Restrictions
How: Settings > Screen Time > Content & Privacy Restrictions > turn on > iTunes & App Store Purchases > Installing Apps > Don't Allow. This prevents Chrome from being reinstalled if you deleted it. Then go to Content Restrictions > Web Content > Allowed Websites Only, and add only the sites you genuinely need. Any site not on the list is blocked in every browser.
Strength: 8/10 alone; 10/10 combined with a Screen Time passcode you do not control. Allowed-websites-only is a near-total browser block -- it is the same parental control used to lock down children's devices. The trade-off is that it is inconvenient when you legitimately need a site that is not on your list.
The sync consideration: blocking Chrome on iOS does not affect Chrome on desktop. If your browsing problem spans devices, this method solves only the phone half. For a complete picture you need separate controls on desktop -- browser extensions, router-level DNS filtering, or app-level limits depending on your OS.
When to use: when you have decided you want browsing heavily restricted for an extended period and Methods 1-3 have not held. Set up your allowed-websites list carefully before enabling -- it is tedious to modify once the passcode is set and someone else holds it.
Method 5: Add a verified-exercise consequence
How: Set a daily total screen time limit in iOS Screen Time (covering the Web category, or your overall daily total). Install ScreenFine ($1/week subscription). When you go over your daily limit, ScreenFine logs a behavioural overage -- each 15-minute block over the limit requires 25 pushups to clear. Chrome browsing minutes count toward the daily total the same as any other app.
Strength: 8/10. The consequence is real and physical. The user can pause the jar at any time, which is the autonomy escape hatch -- but pausing is a deliberate decision with visible cost, not a tap-through on an "Ignore Limit" prompt. The difference between a soft limit and this is that this one costs you something in the real world.
Why this works differently: the address-bar-search spiral in Chrome is driven partly by the absence of any real cost per session. Each lookup feels trivially cheap. A verified-exercise consequence attaches a real, dated, visible cost to the aggregate. It does not block individual sessions -- it makes the pattern of excess legible and uncomfortable in a way that a soft warning screen does not.
When to use: when soft methods (1-4) have failed and you need a structural commitment device but do not want hardware or a passcode held by someone else. Loss aversion -- the discomfort of a real cost, not just a number -- is the smallest mechanism that actually changes habitual behaviour. See the loss aversion guide for the underlying reasoning.
Which method should you pick?
- First attempt: Method 2 (Web category App Limit, no passcode). Audit phase. Watch what happens when the limit fires.
- If Method 2 fails within a week: Method 3 (Screen Time passcode held by someone else). Cheapest escalation, zero cost.
- If you want Chrome specifically gone: Method 1 (delete). Run the 7-day experiment. Remember to cap Safari separately via the Web category limit.
- If you want extended restricted browsing: Method 4 (Content Restrictions, allowed-websites-only). Plan your list before enabling.
- If 1-4 have all failed and you still cannot stop: Method 5 (verified-exercise consequence). Hard commitment device for when friction is not enough.
One thing worth naming directly: most people who look for "how to block Chrome on iPhone" are not dealing with Chrome as the specific problem. They are dealing with browser access in general -- the ability to look anything up, go anywhere, at any moment. Chrome is the app they happen to use. Blocking Chrome without a plan for the underlying browser access is like unplugging one socket in a room full of them.
The methods above work in ascending order of seriousness. Most people need Method 2 or 3. The subset who need Method 5 usually know it by the time they reach this page -- they have already tried and bypassed the softer versions. If that is you, the soft options are not going to get stronger with repetition. Something structural has to change.