If a fixed nighttime boundary fits your routine, you can download 9to9 from the App Store and choose the apps and websites you want quiet from 9 PM to 9 AM.
Website blocking on the iPhone is the least understood piece of the puzzle, and also the most frequently needed — because the moment you block an app, some part of you discovers that the same content lives at a URL. The Twitter app is blocked but twitter.com works. The Reddit app is shielded but Safari is right there. If you have ever caught yourself doing exactly this, you already know the problem: a block that covers the app and not the site is a block with a door left open.
It is also the piece that most cleanly separates a boundary from a performance of one. An app block that leaves the website open is not really a block — it is a suggestion with a workaround, and a workaround that works is not a workaround, it is just the route. The website question is where you find out whether the boundary is real.
The good news is that iOS can restrict websites — both broadly and per-site — and third-party blockers can do it on a schedule. The less good news is that Apple's version has real limitations, and knowing where they are saves you an evening of confused setup. Here is the honest picture.
When website blocking is the missing piece
Before the setup, it is worth knowing whether this is even your problem. App blocking covers most of the nighttime scroll for most people — the habit is attached to the app, and blocking the app is enough. Website blocking becomes necessary in two specific cases: when you have caught yourself routing around an app block through the browser, and when the thing you lose time to was never an app in the first place — a news site, a forum, a blog that exists only as a URL. If neither is true for you, this whole article is a detail you may not need. If one is, it is the piece that makes the app block actually hold.
Apple's built-in website restrictions
The native path runs through Screen Time's content controls: Settings, then Screen Time, then Content & Privacy Restrictions — turn those on if they are not already — then into App Store, Media, Web & Games, and Web Content. There you get the real instrument: you can limit adult websites and then add specific URLs to a Never Allow list, or go further and restrict browsing to only approved sites.
It works — a site on Never Allow is genuinely blocked in Safari. The limitation is what it is not: it is not a schedule. The list applies all the time, not at night. So if your goal is “block these sites at bedtime but leave them during the day,” Apple's native tool cannot express that — it is always-on. You can make the list work for sites you never want at all, but for the specific nighttime problem, the per-URL approach has to be paired with Downtime — which restricts Safari more broadly — and that brings the bluntness problem: Downtime can block the whole browser, which is a bigger hammer than a few sites deserve.
Sources: Set schedules with Screen Time on iPhone (Apple Support)
The routes the habit actually takes
A useful frame before the mechanics: the late-night browse is rarely about a specific site. It is about a behavior — the idle check, the reflexive open — and the site is just where it lands. When you block one URL, the behavior does not disappear; it finds the next one. That is why the list approach alone is always slightly behind: you block Reddit, and the habit moves to the forum; you block the forum, and it moves to the news. The durable answer is the combination — the short list of your real sites plus the scheduled window during which the whole category of idle browsing is quieter — rather than an ever-growing blacklist that chases the habit one step behind.
The precision approach: block the sites, keep the browser
The setup that actually works for the nighttime version of this problem is narrower: block the specific websites that pull you in, on a schedule, while Safari itself keeps working for everything legitimate. That requires a blocker that can do per-site scheduling — a level of precision the native tools do not offer for websites specifically. In 9to9, websites are selected alongside apps in the same daytime choice: you mark the URLs that count as distractions — reddit.com, x.com, whatever your actual late-night sites are — and they are shielded on the same 9 PM to 9 AM schedule as the apps.
The reason to prefer the narrow version over blocking all of Safari is the same reason the whole approach works: a phone that still does its jobs is a system you can live with. The browser is too useful — transit, directions, the actual web, the thing you need at midnight that is not a feed — to sacrifice for the sake of a few sites. Block the sites; keep the browser.
There is also a gentler truth under the precision approach: you are not blocking the sites because they are bad. You are blocking them at night because they are exactly good enough at the wrong hour. A site that is a reasonable lunch read and a terrible midnight one is the normal case, not the exception — which is why the schedule, rather than the always-on ban, is the shape that fits.
A word on other browsers and apps that browse
One honest gap to name: the website restrictions and per-site blocks apply to the browsers iOS knows about — Safari and, depending on the setup, the other browsers that use the same web layer. A dedicated in-app browser inside a social app is a different thing — the link that opens inside Instagram is not Safari, and a website block may not catch it. If your late-night browsing happens inside another app's embedded browser, the fix is to block that app rather than chase the site — the container, not the contents.
Build the list from reality, not theory
The most common mistake in website blocking is overreach — a blacklist of forty sites you might conceivably get lost in. That list is a maintenance problem and it misses the point. The sites that actually need blocking at night are the ones you personally open on autopilot — and for most people that is a short, embarrassing list: the social sites, the news site you check compulsively, a forum, maybe a shopping site that becomes fascinating at midnight.
Start with those — the four or five that are real — and leave the theoretical ones off. A block list of your actual habits is a small thing that works; a comprehensive list of the entire distracting internet is a big thing you will stop maintaining. Watch your own Screen Time report for what actually shows up after your intended bedtime; that data is a better blacklist than any guess.
A word on the always-on versus scheduled choice
The two instruments answer different questions and it is worth keeping them separate. The Never Allow list in Screen Time is the right tool for the sites that are pure loss — the ones you never want, at any hour. The scheduled block is for the much more common case: the site that is fine at lunch and corrosive at midnight. Most people's list is mostly the second kind, which is why the scheduled version — the one that lets the site exist during the day and closes it at night — is the one that fits the actual problem. The always-on list is for the rare site that has no good hour.
What to expect once the sites go quiet
An honest note on the transition, because website blocking has a specific feel that is worth knowing in advance. Unlike an app block — where the icon is right there, dimmed, announcing the boundary — a blocked site just fails to load, which can feel broken rather than closed. It helps to remember it is working as intended: the blank page or the shield is the curfew, not a bug. And the habit that drove you to the address bar will keep suggesting itself for a while — the typed URL is a reflex — but each empty load is a small proof that the door is closed, and the suggestions thin out as they stop being rewarded.
The questions that come up
Can I block a website without blocking all of Safari? Yes — through the Never Allow list in Screen Time's web-content restrictions (always-on), or through a blocker with per-site scheduling (which can restrict to night hours). The second is the version that fits the bedtime problem.
Should I block news sites at night? If “one headline” reliably becomes a loop, yes — the news will still be there in the morning, and midnight is the worst possible time to be informed about the world's problems. A site you cannot stop checking is a site that belongs on the list regardless of how worthy the content feels.
What about the always-on list? The Never Allow list is right for the sites you never want — the ones that are pure loss. The scheduled block is for the sites that are fine at noon and corrosive at midnight. Most people's list is mostly the second kind.
The whole point of the precision approach is that it is proportionate: the browser keeps working, the useful web stays open, and only the specific sites that reliably turn a check into a session go quiet at night. It is not about blocking the internet. It is about closing the few doors that keep the evening open past when it should have ended.
One last honest caveat: if you find yourself constantly adding new sites to the list — chasing the habit as it migrates from one URL to the next — the list is not the problem. The need underneath is. A site list handles the doors you know about; it cannot handle the reason you keep finding new ones. If the browsing keeps finding fresh outlets night after night, that is worth noticing — the fix at that point is less about which sites to block and more about what the late-night browsing is actually for.