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.
There is a specific kind of tired that comes from losing an hour to your phone when you meant to be asleep. You are not browsing because anything is interesting. You are browsing because it is there — because the feed is one tap away, asks nothing of you, and never runs out. If you have landed on this page, you have probably already tried the obvious fixes: going to bed earlier, putting the phone down earlier, promising yourself that tonight is different. The reason those promises keep failing is that they ask your most depleted self to out-argue your most persuasive software.
A better approach is to stop negotiating at night entirely. Blocking apps on a schedule means the decision happens once — during the day, while you are awake enough to make it — and then repeats every evening without further input. Your iPhone can do this with built-in tools, and there are dedicated blockers that make the same idea simpler. This guide walks through both routes honestly, including where each one tends to fall apart.
Why a schedule beats a promise
The reason scheduled blocking works when willpower fails is worth understanding, because it explains every design choice that follows. A promise like “I won't scroll tonight” is not really a decision — it is a commitment to make hundreds of tiny decisions later, each one at the worst possible moment. Every time a notification lands, every time a pause opens up in the evening, every time your thumb drifts to a familiar icon, the question gets asked again: now? just for a second? Each individual check is trivially easy to justify, and the costs only become visible in aggregate, at 12:30 AM, when it is too late to vote differently.
A schedule flips that structure. The question “should I open this app right now” is replaced by a fact: at this hour, this app does not open. There is nothing to deliberate, nothing to rationalize, nothing to win or lose. You made the decision once, in daylight, and tonight it simply executes. The fatigue that would have argued you back into the feed at 11 PM has nothing to argue with — the door is just closed.
This is also why the blocking has to be automatic. Any system that asks you to activate it each evening — a focus mode you remember to start, a session you manually begin — has a built-in failure point at exactly the moment you are least likely to use it. The whole point is that the boundary exists whether or not tonight-you feels like having one.
First, decide what “blocked” actually means for you
Before touching any settings, spend a minute on scope, because the difference between a block that lasts and one you abandon by Thursday is usually here. The question is not “how do I make my phone stop being a phone.” It is “which specific apps turn my bedtime into a suggestion.”
For most people that list is short — somewhere between two and six apps. Short-form video, one or two social feeds, maybe news, a forum, or a shopping app that somehow becomes fascinating at midnight. These are the apps with no natural stopping point, where “I'll just check” reliably converts into forty minutes. Write them down. That list is your block list, and it should be shorter than you think.
Equally important is the list of things that stay available. Calls and messages from people who might genuinely need you. Maps, if you drive or travel late. Music, podcasts, audiobooks. Your alarm. Health and authentication apps. Reading. A phone that still does its useful jobs at night is not a failed block — it is a block you can actually live with. The people who make their entire phone unusable tend to discover, around day three, that they have simply uninstalled the system.
Option one: schedule Downtime with Apple Screen Time
Your iPhone ships with a scheduling feature called Downtime, buried inside Screen Time. Apple's description is accurate: during Downtime, apps and notifications can be blocked while calls, messages, and the apps you choose to allow remain available. Menu names shift slightly between iOS versions, but the path starts the same way.
Open Settings and find Screen Time. If you have never used it, you will be asked to turn on App & Website Activity first — that is the underlying tracking the schedules depend on. Then tap Downtime, enable Scheduled, and set your start and end times. You can apply the same window every day or customize it by day of the week, which is useful if your Friday nights genuinely differ from your Tuesdays.
The critical step most people miss is the toggle labeled Block at Downtime. Without it, Downtime behaves more like a quiet reminder than a restriction — apps get dimmed, but the door stays open. Turn it on.
Next, open Always Allowed and audit it carefully. Everything on that list stays reachable during Downtime, and the defaults may include apps you were hoping would be blocked. Keep the people and tools you might truly need — Phone, Messages, FaceTime, whichever essentials apply to your life — and remove the ones that only pretend to be essential. This is where the honest list from earlier pays off.
Finally, glance at App Limits while you are in there. App Limits and Downtime are different tools: limits cap total daily minutes, while Downtime controls when apps are available at all. If your problem is “I want less Instagram overall,” a limit helps. If your problem is “Instagram after 11 PM,” Downtime is the right instrument, and a daily allowance can actually undermine it — you can spend your whole allowance in bed.
Sources: Set schedules with Screen Time on iPhone (Apple Support)
Downtime is genuinely good software for a free built-in feature, but it is worth knowing its two weak points before you rely on it. First, its model runs broad-to-narrow: it restricts everything by default and asks you to maintain the exceptions, which means the setup work is ongoing rather than finished. Second, its boundaries are soft where it matters. If you set the rule yourself, dismissing it yourself is usually a couple of taps — and those taps are easiest to justify at exactly the moment the limit fires. For some people that friction is enough. For others it becomes a nightly ritual of tapping “Ignore Limit” while feeling mildly worse about themselves.
Option two: one fixed nightly rule
The alternative philosophy is to trade flexibility for finality. Instead of designing a schedule, you accept a fixed one — and the app's entire job is to make that one boundary boring and reliable.
That is the shape of 9to9, and it is worth describing plainly because it is a different bet than most blockers make. The schedule is always 9 PM to 9 AM; there is nothing to configure. During the day you choose which apps and websites count as distractions — individually, or by category — and that is the setup. At 9 PM the selected apps are shielded. At 9 AM they come back on their own. There is no nightly start button, no session to begin, no discipline required at 8:58 PM.
The escape hatch is deliberately sized: Temporary Access opens your blocked apps for five minutes, then the block resumes automatically. That matters more than it sounds. A block with no exceptions eventually meets a real need — a code sent to a messaging app, a link a friend insists you open, a boarding pass in a walled-off app — and a rigid block teaches you to break it. Five minutes is long enough for the errand and short enough that it cannot quietly become the rest of the evening.
Setup takes a few minutes. Install the app, grant the Screen Time permission when prompted (that permission is what allows any third-party app to shield other apps on iOS), choose your distracting apps and websites during daytime hours, and you are done. One small ritual worth doing: that first night, at 9:05, try to open one of your selected apps. Watching the shield actually appear converts the whole thing from an intention into a fact, and it makes the boundary much easier to trust for the rest of the week.
Sources: Screen Time technology frameworks (Apple Developer)
Choosing between them
Neither option is universally better, and the honest answer depends on which failure you are trying to fix.
Choose Downtime if your life genuinely needs different schedules on different days, if you want the broad allow-list model, or if you would rather not install anything. It costs nothing, it is already on your phone, and for plenty of people it is enough — especially if the “Ignore Limit” button has not yet become a habit.
Choose a fixed blocker if your problem is specifically the night-and-morning window and you have noticed that flexibility is the thing you keep exploiting. If every configurable system eventually becomes a negotiation you win against yourself, a schedule you cannot edit is a feature, not a limitation.
Whichever you pick, resist the urge to stack systems on day one. Running Downtime, App Limits, and a third-party blocker simultaneously creates a maze you will not want to maintain, and when something misbehaves you will not know which layer caused it. Start with one, live with it for a week, and add complexity only if a specific gap appears.
The failure modes worth knowing about
A few honest warnings, because every blocking setup has a characteristic way it dies. The first is allow-list creep — the slow expansion of “essential” apps until the exceptions swallow the rule. It starts innocently: you keep the browser available for legitimate reasons, then Reddit works through the browser, and within a week the block exists mostly in name. The fix is to review your exceptions monthly and ask of each one whether it is essential or merely wanted.
The second failure mode is more subtle: the bypass becoming a ritual. If your system offers an easy override — an “Ignore Limit” button, a passcode you know by heart — the override stops being an exception and becomes part of the nightly loop. Check, get blocked, override, scroll, feel worse. If you catch yourself in that pattern, the answer is not more self-criticism; it is a different tool whose escape hatch is sized for errands rather than sessions.
And the third is overcorrection after a lapse. One bad night does not mean the system failed — it means the system met a night. The instinct to respond by blocking everything, everywhere, produces a fortress you will abandon by Friday. Adjust the smallest thing that would have prevented that specific lapse and leave the rest alone.
If your nights do not look like nine-to-nine
A fixed boundary only helps if your life roughly follows the clock it assumes. If you work nights, care for someone on an unpredictable schedule, or your evenings simply do not map onto a 9 PM cutoff, be honest about that rather than forcing a rule that will not fit. In that case, Downtime's customizable schedule — or a fully configurable blocker — is the better instrument, because a boundary you resent is a boundary you will dismantle.
Similarly, if the phone is doing real overnight work for you — on-call duties, a monitor for a kid's room, a partner who reaches you through a specific app — build around it rather than pretending it away. Both approaches described here let essential communication through; the point of the exercise has never been to make you unreachable, only to make the bottomless parts quiet.
The safety check worth doing before you rely on any of this
App blocking is a habit tool, not a safety system, and it is worth one deliberate pass before the first night. Confirm that phone calls ring through. Check that the messages and people you might need overnight are not blocked. Think about transportation, two-factor authentication, health apps, home controls — anything whose absence would turn from inconvenience into problem at 1 AM. Both approaches above let you keep all of these; you just have to actually do it.
Then leave it alone. The setup only works if you stop relitigating it — adjust your block list during the day if something is missing, but let the nights be boring. That boredom, it turns out, is the point.