How to set app limits on iPhone

To set an App Limit on iPhone: open Settings, tap Screen Time, tap App Limits, tap Add Limit, choose an app or category, set a time budget, and confirm. That's the entire base setup, and it's free and built into every iPhone running a reasonably current iOS version — no separate app or subscription required. The step most guides skip, and the one that actually determines whether the limit means anything, is setting a Screen Time passcode under Screen Time settings, since without one, the limit you just set can be raised or removed in the same number of taps it took to create it. It's also worth knowing App Limits can be applied to a whole category (Social, Games, Entertainment) rather than one app at a time, which is faster to set up but less precise than picking individual apps.

The mechanism behind an App Limit

Once set, an App Limit runs entirely on-device: iOS tracks foreground usage time for the app or category, and when the budget is hit, the app is greyed out on the home screen and, if opened, shows a native Screen Time block screen instead of launching. This happens locally — there's no server-side tracking or remote enforcement — which is why the limit resets automatically at midnight local time and why restoring the device or removing Screen Time configuration clears it. "One More Minute" and "Ask For More Time" buttons appear on that block screen by default; without a Screen Time passcode, tapping either simply extends the limit for the day, no barrier involved. It's worth noting the block screen itself is the same native iOS interface regardless of which category or app triggered it, which is part of why App Limits feel consistent across the whole system rather than app-by-app — the entire mechanism lives at the OS level, not inside any individual app being limited. The greyed-out home screen icon during an active limit is also a useful passive cue on its own, separate from the harder block — some people find just seeing the icon dimmed is enough of a reminder to redirect attention, even before attempting to open the app. Some people intentionally rely on this passive cue alone for lower-stakes apps, reserving the harder passcode-gated limit for the one or two apps that genuinely need it.

What a Screen Time passcode actually changes

Adding a passcode (Screen Time settings → Use Screen Time Passcode, entering a 4-digit code separate from your device passcode) gates two specific things: dismissing the "Ask For More Time" request beyond the default extension, and changing or deleting the limit itself from Settings. It's a real, meaningful barrier for a limit set on someone else's device where you hold the passcode and they don't — the standard Family Sharing setup. Set on your own device, for yourself, with a passcode only you know, it's a softer barrier: you can still reset it via Apple ID recovery, or simply remember the code you set five minutes ago. The honest framing is that a Screen Time passcode is strong when a second, less-motivated-in-the-moment party holds it, and comparatively weak when the same person who wants to bypass it also knows or can recover it. This asymmetry — strong when someone else holds the code, weaker when you hold it yourself — isn't a flaw specific to Apple's implementation; it reflects a genuine limit of any restriction enforced on a device the restricted person fully owns and controls. It's worth testing the recovery flow once, deliberately, right after setup — attempting a passcode reset through your own Apple ID — so you know exactly what the gap looks like in practice rather than assuming it either does or doesn't apply to your specific configuration.

A practical setup that closes the common gaps

For restricting your own device: set the App Limit, set a Screen Time passcode, and have someone else set that passcode for you if the goal is genuinely restricting your own future access — a code you know defeats much of the point. For restricting a child's device: set it up through Family Sharing (Screen Time → Family, select the child's name) so limits are managed from the parent's device and the passcode lives there, not on the child's phone at all, which also closes the Apple-ID-recovery gap that trips up passcodes set locally on the restricted device itself. It's also worth periodically checking that the passcode recovery option through Apple ID is configured the way you expect, since Apple has adjusted the exact recovery flow across iOS versions and a setup that closed a gap on one version may behave slightly differently after a major update. For couples or roommates setting this up for each other, agreeing in advance on how strict to be, and revisiting that agreement periodically, tends to produce a more sustainable setup than a one-time, unilateral decision either person might later resent. Writing down the agreement, even briefly, tends to reduce disputes later about what was actually agreed to.

Where Mr. Grummel fits

For a self-restriction setup where you don't want to hand your Screen Time passcode to someone else, Mr. Grummel offers a different kind of barrier at the unlock moment — a quiz question instead of a code — which doesn't require finding a second person willing to hold a secret for you. For someone who'd rather not involve a second person at all, this is a real, honest limitation of Screen Time's own design worth knowing before assuming a passcode alone solves the self-restriction problem. It's a reasonable trade to make consciously — a slightly less rigid technical barrier in exchange for not needing anyone else's involvement at all.