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 gesture that anyone who has tried to use Screen Time on themselves knows by heart. The alert appears — time's up on the app — and your thumb is already moving before you have read it. Ignore Limit. Fifteen more minutes. The whole transaction takes less than a second, requires no thought, and completely undoes the thing you set up to protect yourself. If that gesture has become automatic for you, the problem is not that you lack discipline. The problem is that you are fighting the system on the terms it designed.
It helps to see the shape of it clearly. You set a limit during the day, in a moment of reasonable intentions. The limit fires at night, at the exact moment your desire for the app is highest and your resolve is lowest — the two are perfectly, uselessly synchronized. And then the phone itself hands you the exit: not a pause, not a delay, just a button that says, essentially, “or don't.” You are not failing the system; the system is asking you to win an argument it is specifically built to help you lose.
So the fix is not to try harder at the button. It is to change what the button is.
What the limit was actually built to do
It helps to be fair to the tool, because understanding what Screen Time is for explains why it keeps failing you. Screen Time is, at its core, a measurement and awareness system: it shows you where your time goes, and it offers gentle interventions — a limit that warns, a downtime that dims — designed to inform a reasonable user. It is the phone's way of saying “here is the data, make a good choice.” That is a reasonable design for a tool meant to inform an adult, and it is a terrible design for a boundary, because a boundary's whole job is to not require a good choice at the moment of maximum temptation.
Once you see that, the repeated bypassing stops being mysterious. You are not failing to use the feature correctly; you are discovering that the feature was never the thing you needed. You needed a wall, and you were given a speedometer.
Why the button exists (and why it beats you)
Screen Time was designed for parents managing kids' phones and for gentle self-awareness — a dashboard, a nudge, a speedometer. It was not designed to be a wall you cannot get past, because Apple's whole model is that the device ultimately answers to its owner. The Ignore Limit button is a feature in that model: the phone trusts you. The trouble is that at 11:47 PM, the “you” being trusted is the worst possible version to be making the call.
Once you see it that way, the repeated tapping stops looking like a personal failing and starts looking like a design mismatch. You wanted a boundary; you installed a suggestion. The remedy is to replace the suggestion with something that was actually built to be a boundary — or to change what kind of rule you are asking Screen Time to enforce.
The nightly pattern that produces the tapping
It is worth being precise about when the ignoring happens, because it is almost never random. The Ignore Limit reflex concentrates at specific moments — the last half-hour before bed, the wake-up-at-3-AM reach, the transition when a show ends and the couch goes quiet. These are not weak-willed moments; they are the moments the day has already emptied you out, and the limit is arriving at exactly the wrong time to be meaningful.
That pattern is the argument for the time-based fix in miniature. The limit that keeps getting ignored at 11 PM is not a bad limit — it is a limit arriving at a moment when no limit can win. The schedule that closes the door at 9 PM works because it does not have to be honored at 11; it was already honored, automatically, before the moment existed.
The strictest native option: a passcode you do not hold
The genuinely firm version of Screen Time exists, and it is this: a Screen Time passcode that you do not know. If a trusted person — a partner, a friend — sets the passcode, the Ignore Limit path closes, because bypassing the limit requires the code you do not have. For some people this is exactly the right answer: the boundary becomes real precisely because you cannot dissolve it yourself.
It is also, for most adults, a strange amount of infrastructure for the problem. It means coordinating with another person, it means explaining the system, it means the unlock is only ever as available as that person is — and it carries a faintly parent-child energy that some find effective and others find quietly absurd. If the arrangement fits your life, it is the strongest thing iOS offers without another app. If it does not, the fix is elsewhere: not in making the wall taller, but in making the rule different.
Sources: Set schedules with Screen Time on iPhone (Apple Support)
Move the decision earlier: time rules, not volume rules
The deeper fix is to notice what kind of rule keeps losing. “Instagram gets 30 minutes” is a volume rule — it spends the day counting, and it fires its interruption at whatever hour the minutes run out, which is often the hour you are most vulnerable. It also leaves the decision of where to spend the allowance entirely open: the 30 minutes are available at midnight same as noon, and at midnight they go further than they should.
A time rule answers a different question. Not “how much” but “when.” Instagram is unavailable after 9 PM — that is a rule with a clock attached, and it fires before the scroll rather than in the middle of it. The difference in outcomes is the difference between being interrupted mid-session and the session never starting. One is an argument you keep losing; the other is a door that was never open.
This is what Downtime does natively — a scheduled window when marked apps are unavailable, with the allow-list controlling what stays — and it is why it beats App Limits for the specific problem of nighttime use. The limit asks “have you had enough”; the downtime asks nothing, because the window simply is.
Make the escape hatch the right size
Here is the counterintuitive part: the answer to a too-easy override is not always an impossible one. A block with no exit at all eventually meets a real need — the code sent to a blocked app, the link a friend must show you, the genuine emergency — and a system that cannot bend at all is a system that gets uninstalled the first time it truly inconveniences you. The goal is not a wall you cannot get past. It is a gap small enough that only the real things fit through.
This is the logic behind 9to9's five-minute Temporary Access — long enough for the errand, short enough that it cannot quietly become the rest of the evening. The escape hatch is deliberately sized for the difference between “I need to do a specific thing” and “I want to keep scrolling.” The first fits through the window; the second does not, which is precisely the distinction a good boundary needs to make.
Remove the cues that keep starting the fight
The other half of the fix is upstream of the button entirely. The Ignore Limit reflex only fires when the app has already pulled you in — the notification, the icon, the badge, the idle reach. Every one of those cues removed is a fight that never has to happen.
Turn off the non-human notifications — every alert whose job is to pull you back into an app rather than connect you to a person. Move the distracting apps off the first Home Screen, into the App Library or a folder, so the idle glance stops being an idle open. Charge the phone beyond arm's reach at night, so the reflex has to become a decision before it can become a scroll. None of this is a block; all of it reduces the number of times per day the habit gets invited to start, and the version of you that has to keep declining the invitation is the version that keeps losing.
Building the version that holds
Put the pieces together and the working setup looks like this: a time-based boundary (Downtime or a fixed blocker) covering the hours when the ignoring happens; a narrow block list of the two-to-six apps that actually become sessions; the cues removed so the reflex fires less often; and an escape hatch sized for errands rather than evenings. Every element is aimed at the same target — the moment of in-the-moment choice — because that is the moment the Ignore Limit button has been winning. Remove the moment, and there is nothing left to ignore.
The other thing worth trying first
Before changing tools entirely, one honest check on your current setup: are the limits you have set actually the right ones? A limit that is too generous — an hour of Instagram, say — never fires early enough to matter, and a limit that is too strict invites the bypass. There is a version of the problem where the limit's real flaw is that it was calibrated to a person you are not: too ambitious, too broad, covering apps that were never the problem. Tightening the list to the two or three that actually become sessions is worth a try before concluding the whole approach is broken — sometimes the limit is not too weak, just aimed at the wrong thing.
When ignoring the limit is telling you something
A last thought, because the pattern is worth listening to rather than just suppressing. If you keep bypassing the limit at the same hour, in the same place, every night — that is data. It is saying that particular window is where the need lives, and the need is real enough to keep finding the override. Sometimes the honest response is a stronger block. Sometimes it is noticing what the scroll is covering — the evening with no other plan, the day that left no room — and addressing that instead of just walling off the symptom.
What success actually looks like
The version of “fixed” worth aiming for is not a phone you can never get into — it is a night where the question of whether to keep scrolling simply does not arise. The apps are quiet at 9 PM, the useful phone still works, the escape hatch exists for the real need, and the reflex that used to end in Ignore Limit ends instead at a shield that does not argue. After a week or two of that, the strangest part is how little you think about it — the boundary is just there, the way a locked door is just there, and the evening is free to be an evening again.
The Ignore Limit button is not a moral test you keep failing. It is a design detail that was never built to stop you. Stop asking it to.