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 question usually arrives in a specific form: “can I make Instagram stop working at 10 PM?” Not delete it, not limit it — just make it unavailable during the hours when it reliably does damage. The answer is yes, and your iPhone already has the machinery. What is less obvious is that iOS gives you two different tools that look similar and solve different problems, plus a third approach that removes the configuring altogether. The tool you pick should depend on which problem you actually have, so let us start there.
It is also worth saying upfront what this is not: locking apps on a schedule is not the same as locking them away. You are not giving up the apps, or your account, or your streaks — you are giving the apps hours, the way you would give a store hours. The feed can be open all day and still be closed at night; those are not in conflict, and keeping that distinction is what makes the whole thing livable.
First, figure out which problem you are solving
There are two versions of “I want to lock this app,” and they need different instruments.
The first version is about volume: the app is fine in moderation but eats too much of the day. “I want no more than thirty minutes of TikTok.” That is a budget, and iOS handles budgets with App Limits — a daily allowance that fires when the time is spent.
The second version is about timing: the app is fine during the day and corrosive at a specific hour. “I do not want Instagram in bed” or “I do not want Reddit before I've had coffee.” That is a window, and it is what Downtime — or a scheduled blocker — is for. The distinction matters because people routinely reach for the wrong one: they set a thirty-minute App Limit and then wonder why they can still burn the whole allowance at midnight in bed. The limit answered “how much.” It was never going to answer “when.”
There is also a third, quieter question worth asking while you are here: which apps are actually the problem? Most people can name two to six. The short-video app, the social feed, maybe news or a forum. If your list is longer than that, it is probably not a list of distractions — it is a general unease about the phone, and a targeted block is the wrong tool for that. Start with the apps that turn a quick check into a lost hour; you can always widen later.
And one practical habit that makes the whole setup honest: watch your actual behavior for a day or two before configuring anything. The apps you think are the problem and the apps that are the problem are not always the same list — the one you open forty times without noticing is the one that needs the lock, and you will not find it by guessing. Check your Screen Time report for the apps that show up most between your intended stopping time and your actual one; that data is a better block list than any guess.
Lock apps on a schedule with Downtime
Downtime is Apple's built-in answer to the timing problem, and it lives inside Screen Time. The path, in the current version of iOS — menu names shift slightly between versions, but the route holds — starts in Settings, then Screen Time. If you have never turned Screen Time on, you will be prompted to enable App & Website Activity first, because the scheduling features sit on top of that tracking layer.
Inside Downtime, turn on Scheduled and set your start and end times. You can run the same window every day or customize it per day of the week — useful if your Friday nights genuinely differ from your Tuesdays. Then, and this is the step that makes it real, turn on Block at Downtime. Without that toggle, Downtime is advisory: apps dim and warn, but the door stays open. With it, restricted apps are actually restricted.
The other half of the setup is Always Allowed, the list of apps and contacts that stay reachable during Downtime. Audit it carefully — anything on that list is exempt, and the defaults may include apps you expected to be blocked. Keep the ones that are genuinely essential — Phone, Messages, FaceTime, maps, health, whatever your real life needs — and pull out the ones that are merely persuasive. The quality of your Downtime is largely the quality of this list.
Sources: Set schedules with Screen Time on iPhone (Apple Support)
Downtime's model is worth understanding because it explains both its strength and its friction. It works broad-to-narrow: everything gets restricted during the window except what you explicitly allow. That is powerful — a genuinely quiet phone during the hours you choose — and it is also maintenance. The allow-list becomes a thing you tend, and every app you forgot to exempt becomes a small annoyance that argues for loosening the whole thing. Some people live happily inside that model. Others find it slowly dissolves as the exceptions pile up.
Lock apps by daily budget with App Limits
The other native tool answers the volume question. Settings, then Screen Time, then App Limits, then Add Limit — choose an individual app or a category and set the daily allowance. When the time is spent, the app notifies you and restricts further use until tomorrow.
App Limits are honest tools for the problem they are built for. If your issue is that Twitter eats two hours scattered through the day, a forty-five-minute cap is a real intervention. But know the limits of the limits: they are soft by design. When one fires, iOS offers to let you keep going — one more minute, fifteen more, or the rest of the day — and since you set the rule yourself, you hold the keys yourself. For some people the interruption is enough; for others the override becomes part of the ritual, which is how a limit quietly becomes a notification you are good at dismissing.
A word about hard locks
At this point some people ask about the strict version — a passcode someone else holds, a lock with no override, an app that cannot be reasoned with. It exists, and for a few people it is right. But for most adults it overshoots the problem. A lock you cannot open means the first genuine need — the boarding pass, the emergency, the thing a partner needs right now — forces you to either break the system or live with being locked out of your own phone, and both teach you to remove the system entirely. The useful middle ground is access that is possible but deliberate: a barrier the impulse cannot cross in one tap, with a door sized for real errands. The goal is not to make yourself a prisoner of your own settings; it is to make the easy thing at 11 PM be something other than the feed.
The third option: a fixed nightly block
If the problem you named is specifically the night-and-morning window — the feed in bed, the scroll before coffee — there is a simpler shape available: a blocker that does one recurring window and nothing else. This is the approach 9to9 takes, and it is best understood as a bet about where the problem lives.
The setup is a single decision made once: during the day, you choose which apps and websites count as distractions — individually, or by whole categories like Social or Games. After that, there is nothing to manage. At 9 PM the selected apps are shielded; at 9 AM they return. There is no session to start, no schedule to configure, no nightly act of remembering — the boundary just repeats, which is the point. The fixed hours are not a limitation so much as the product: a schedule you cannot adjust is a schedule you cannot renegotiate at 11:30 PM.
The one deliberate escape is five-minute Temporary Access — enough for the boarding pass, the login code, the thing a friend needs you to see — after which the block resumes on its own. Third-party blockers on iOS work through Apple's own Screen Time frameworks, the same APIs that Downtime is built on, which is why the permission prompt during setup asks for Screen Time access.
Sources: Screen Time technology frameworks (Apple Developer)
What an ordinary night looks like once it is set up
To make the abstraction concrete: with any of the three methods properly configured, 9 PM arrives and the selected apps simply stop. The icons may still be there — dimmed, or shielded — but the door is closed. The phone still works for everything you left available; only the marked distractions are quiet. The first night you will test it — you should test it — by trying to open one of the blocked apps at 9:05, watching it refuse, and feeling the strange small relief of a rule that holds without you holding it.
After that, the boundary fades into the background, which is the entire point. You do not think about the block every night the way you do not think about a locked front door — it is just how things are. The feeds return at 9 AM or whenever your window ends, and the arrangement that sounded like a restriction reads, in retrospect, like the only part of the phone that was ever under control.
Which method should you actually choose
The honest answer depends on the shape of your problem. If the problem is daily volume — too much of an app spread across waking hours — App Limits is the right native tool. If the problem is a window and you need the window to be yours — different hours on different days, an allow-list you control — Downtime is built for that. And if the problem is specifically that the night and morning keep disappearing into the same few feeds, and you have noticed that configurable systems become negotiations you keep winning against yourself, the fixed blocker is the version with fewer places to hide.
Two warnings apply to all three. First, do not stack them on day one — overlapping systems create a maze where you cannot tell which layer failed, and a system you cannot diagnose is a system you will delete. Pick one, live with it a week, and add only if a specific gap shows up. Second, before you rely on any of them, check that the essentials survive: calls, messages, authentication, health, transportation. A block that strands you at 1 AM is a block that gets removed, and the point of all of this is a boundary you can actually live with — night after night, without thinking about it.
That is really the whole answer. Yes, the iPhone can lock apps at certain times. The harder question was never whether the feature exists — it is whether the boundary holds when the tired version of you comes asking. Choose the tool whose version of “no” you cannot easily talk out of it.