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.
The two tools get confused constantly, and the confusion matters because they are answers to different questions. An app timer — Apple's App Limits, most digital-wellbeing apps — caps how much you use an app: thirty minutes of Instagram, an hour of TikTok. An app blocker changes when you can use it: the app is available during the day and unavailable at night. For the specific problem of the phone stealing your sleep, the second is almost always the better tool, and the reason is worth understanding rather than just asserting.
The same app can wear both hats — know which one you set
A practical confusion worth clearing up, because it is the source of a lot of “my limit isn't working”: the same app or feature can be configured as either a timer or a block, and people routinely set one expecting the other. Screen Time's App Limits are timers — daily budgets. Its Downtime is a block — a schedule. They sit in the same menu and look similar, and choosing the timer when you meant the block produces exactly the failure described below: a limit that can be spent at midnight. So before the comparison, make sure you know which instrument you are actually holding.
The timer's model: a budget that does not know what time it is
The app timer's idea is reasonable: most screen-time problems are problems of volume, and a cap on the volume is a direct answer. If you are spending two hours a day on an app, a forty-five-minute limit is a real reduction. For the daytime version of the problem — the app that eats the afternoon in scattered sessions — a timer is a legitimate instrument.
The failure is that a budget has no clock. The forty-five minutes are equally available at noon and at midnight, and the timer does not distinguish between them. Which means the whole allowance can be spent in bed — the exact hours you most needed to protect. A thirty-minute cap does nothing to stop the thirty-minute scroll that starts at 11:45 PM; it just makes sure the scroll ends at 12:15, having already taken the hour you could least afford. The timer answered “how much.” It was never going to answer “when.”
There is a second, quieter failure: the override. Most app timers are soft by design — when they fire, the phone offers to let you continue. You set the rule yourself, so you hold the keys yourself, and the moment the limit arrives is precisely the moment you least want it. A cap you can dismiss is a cap that becomes a notification you are good at dismissing.
Sources: Set schedules with Screen Time on iPhone (Apple Support)
What each one feels like to live with
Worth describing, because the difference is not just abstract. A timer day feels like being watched — a running total, a cap approaching, a decision at the moment the number runs out. It is a continuous negotiation with yourself about whether this session is worth the remaining minutes. A blocker day feels like nothing — the apps are there during the allowed hours and simply not during the others, and there is no ongoing tally to manage. For the person who finds the timer's constant accounting tiresome, the blocker's silence is the appeal; for the person who finds the blocker's rigidity suffocating, the timer's flexibility is the point.
The blocker's model: a schedule that does not care how much
The blocker answers a different question. Rather than metering the app, it changes whether the app is available at all during a window — the schedule says the feed is closed from 9 PM to 9 AM, and within that window the question of how much time you have spent is moot, because the session cannot begin.
That is exactly the property the sleep problem needs. The harm is not the total minutes; it is the session at the wrong hour — the scroll in bed, the feed before the alarm, the check that becomes the stolen hour. A block prevents the session rather than interrupting it, which is the difference between an argument you keep losing and a door that was never open.
The honest cost: a block is blunter than a timer. A cap lets you use the app at any hour within the budget; a block removes it entirely during the window, including for uses that might have been fine. That is the trade — more restriction, applied to fewer hours, in exchange for the restriction actually holding.
The mistake of using a timer for a sleep problem
It is worth naming the specific error, because it is common and it produces a particular frustration: someone sets a forty-five-minute Instagram limit, keeps hitting it in bed, keeps tapping through, and concludes the tool does not work. The tool was working as designed — it capped the total. What it could not do is what was actually needed: stop the app from being available at the hour that mattered. The failure was not the tool's discipline; it was a category error — a volume answer applied to a timing problem. The fix is not a stricter limit; it is a different instrument.
Why the night specifically favors the schedule
The case for the blocker over the timer is strongest precisely at night, for reasons worth naming. The evening is when the timer's weaknesses are worst: the budget that can be spent in bed is spent in bed, and the override that requires resisting arrives at the moment of least resistance. And the night is when the blocker's strength matters most: the schedule runs automatically, before the tired hours, and does not require an in-the-moment win.
The research framing supports the same conclusion. The consensus on screen use and sleep points to timing — use close to bedtime — as the relevant factor, more than total daily use. If the harm is about when rather than how much, then a tool that controls when is the right instrument, and a tool that only controls how much is answering a question the research is not asking.
Sources: The impact of screen use on sleep health across the lifespan: consensus statement (PMC)
The version of each that actually holds
Both tools come in strong and weak forms, and the distinction matters more than the category. A timer that is soft — one tap to continue — barely counts as a timer. A blocker you can dismiss just as easily is a timer wearing a blocker's costume. The real axis is not timer-versus-blocker but soft-versus-hard: does the boundary require an in-the-moment win, or does it exist whether or not tonight-you honors it? The tools that hold are the ones where the decision was made in daylight and does not come back for renegotiation — whether they are called timers or blocks is almost beside the point.
When the timer is the right tool
To be fair to the timer: there is a problem it solves better. If the issue is volume across the day — the app that eats the afternoon, the total you want to shrink — a cap is the direct instrument, and the blocker's all-or-nothing window is a poor fit for a scattered-hours problem. The timer is also the better tool when you want the app to stay available but want a nudge toward less of it — a gentler intervention for a milder habit.
And there is a version of the problem that is genuinely both: too much of the app during the day and the wrong hours at night. For that, the honest answer is that the tools are not mutually exclusive — a timer for the daytime volume plus a scheduled block for the night covers the whole problem, at the cost of two systems instead of one. The advice against stacking tools applies to redundancy, not to two tools answering two different questions.
The questions that follow
Can I use both? Yes — the timer for the day's total, the block for the night's hours. Just do not confuse them: the cap will not protect the bedtime, and the schedule will not shrink the afternoon.
What about the override problem? The timer's is softer — a tap to continue. The blocker's depends on the tool: a scheduled block with no easy bypass (or a small, deliberate one like a five-minute access window) is the version that holds; a block you can dismiss in one tap has the timer's failure in a different costume.
Which should I try first? The blocker, if the problem is the night. The timer, if the problem is the day's total. The combination, if it is genuinely both — though start with one and add only if a specific gap appears.
The simplest version of the answer: the timer asks “have you had enough,” and at 11 PM the answer is always “not yet.” The blocker asks nothing, because the window is already closed. For the problem of the phone and the sleep, that difference is the whole thing.