Screen Time limits not working? The six real fixes

You set a limit. The limit arrived. You kept scrolling. Now you are searching for why your Screen Time limits are not working.

There is usually no bug. There are five specific mechanisms, four of them documented and enabled by default, that turn a limit into a suggestion. Knowing which one you hit is worth more than another list of things to restart.

The short answer

An app limit only blocks if all of these are true: a passcode is set, "Block at End of Limit" is on, app deletion is restricted, the clock is automatic, and you do not open the site in a browser. Miss any one and the limit becomes a notification you dismiss. On Android the equivalent switch is the App limits PIN, also off by default — plus a sixth problem that is Android's alone: the manufacturer's battery manager may quietly stop enforcement software from running at all.

Why are my Screen Time limits not working?

Check these first, in this order.

If the phone says "Screen Time has been restricted"

That message is a different problem from a limit failing to fire. It usually means the restriction layer is active: a Screen Time passcode, Family Sharing role, school/work profile, or device-management setting is preventing the change you are trying to make.

If this is your own phone, check whether you set a Screen Time passcode and forgot it, or whether the phone is part of a family group. If it is a managed school or work device, the restriction may be intentional and only the administrator can change it.

The important distinction: "restricted" means the lock is holding. "Time limit reached" with an ignore button means the lock was never fully set.

1. There is no Screen Time passcode

This is the big one, and it is silent.

Without a Screen Time passcode, everything under Screen Time is a preference, not a restriction. The limit fires, the screen appears, and the button that dismisses it asks nobody for permission. You set a rule and kept the key in your pocket.

Setting a passcode is the single highest-value change available, and it comes with the obvious problem: you know the passcode. It buys you a few seconds of deliberate typing rather than a reflex tap. That is not nothing — but be honest with yourself about what it is.

2. "Block at End of Limit" is off

When the limit is reached, iOS shows a screen offering to ignore it. Depending on version, the options have included one more minute, fifteen minutes, or the rest of the day. The toggle that removes those options is called Block at End of Limit, and it lives inside each individual app limit rather than in the top-level Screen Time settings.

It is off by default. Most people who believe their limits do not work have never seen this switch.

Turn it on for each limit you actually mean. With a passcode set and this toggle on, reaching the limit produces a block that requires the passcode — which is the behaviour almost everyone assumed they were configuring in the first place.

3. Deleting the app deletes the limit

A limit tracks usage per app. Remove the app, and the accumulated usage for it can go with it; reinstall from the App Store and the counter starts fresh.

This takes about forty seconds and no passcode. It is not obscure — it is the first thing suggested in most forum threads about getting around limits.

The fix lives in a different menu than the limit does: Screen Time → Content & Privacy Restrictions → iTunes & App Store Purchases, where "Deleting Apps" and "Installing Apps" can each be set to "Don't Allow". Restricting deletion without restricting installation leaves the hole open in one direction, which is why both matter.

4. The clock is yours to change

Limits reset at midnight, and the device decides when midnight is.

If Date & Time is set manually, moving the clock forward rolls the day over and returns the full allowance. The counter-move is Settings → General → Date & Time → Set Automatically, plus restricting time-zone changes so the setting itself cannot be flipped back.

This is the one people describe as a "glitch". It is not a glitch. It is a device doing what its owner told it.

5. The web version is not the app

An app limit applies to an app bundle. Instagram, X, TikTok, YouTube, Reddit and Facebook all have perfectly usable websites, and Safari is a different app with a different limit.

Blocking the app while leaving the browser open moves the behaviour rather than stopping it, and it moves it somewhere with fewer guardrails and no usage reporting. Website limits are configured separately, under Content & Privacy Restrictions, and they need a list of domains — including the mobile subdomains and the short-link domains, which is tedious enough that most people quietly skip it.

Last Ferry has exactly the same hole, and we say so on the front page: it blocks apps, not browsers.

Android: the same problem wearing different clothes

Digital Wellbeing's app timers have a lighter version of the iOS problem and one heavier one of their own.

The light version is the same default problem in a different menu. A timer, left as it ships, can be changed or deleted in a handful of taps by whoever is holding the phone. But Android does have the switch people assume it lacks: Digital Wellbeing → App limits → App limits PIN. Turn it on, set a four-digit PIN, and limits cannot be altered or removed without it. When a timer expires the app closes and its icon dims, and timers reset at midnight.

Google's own documentation carries the trick worth knowing: set an App limits PIN and set an app's limit to zero, and that app is blocked outright.

That is genuinely better than most Android advice admits — it is the closest built-in equivalent to a passcode-protected iOS limit, and almost nobody has it switched on. Steps vary a little by manufacturer. Samsung's implementation has also had a documented interaction where adding an app to the excluded list after setting a limit removes the limit entirely.

The heavy version affects every third-party blocker on the platform. Manufacturers layer their own power management on top of Android's, and it is considerably more aggressive than Doze. Xiaomi, Samsung, Huawei, Oppo, OnePlus and others variously kill background services, revoke autostart permission, and put apps to sleep after a period of non-use — without telling the user, and sometimes resetting the permission again after a system update.

For an ordinary app this is a battery-life annoyance. For enforcement software it is fatal in a specific and nasty way: it fails silently, and it fails in your favour. The blocker does not announce that it has been killed. It simply stops blocking, on the day you most needed it to, and you notice only in the usage figures a week later.

Anything installed for this purpose on Android needs the manufacturer's autostart and battery exemptions granted by hand, in per-vendor menus that move between versions. It is worth checking those settings after every system update, because that is when they get reset.

The pattern underneath

Read those five mechanisms together and a shape appears. Each one is a door left open for a completely sensible reason: people need to reinstall apps, travel across time zones, and occasionally use a browser. None of them is a mistake.

But add them up and you get a category-wide fact, which is that the person who can lift the restriction is the person being restricted, and lifting it is free. Every fix above is really the same move — making the escape hatch cost a few more seconds, or a few more taps, or a trip into a settings menu you would rather not visit.

Seconds and taps are a real currency, and at 11pm they buy you something. At 1am they buy you almost nothing, because the whole problem is that at 1am you are willing to spend them. Friction scales badly exactly where you need it most.

This is the reason we did not build another blocker with a better lock on it. We wrote about the structural version of this argument in every app blocker becomes a parent: the failure is not tonal, and it is not a missing feature. It is what enforcement means when the enforcer answers to the enforced.

What actually helps

In rough order of how much they buy you:

1. Set the passcode and turn on Block at End of Limit. Ten minutes of setup, and it converts a notification into an actual block. Do this before anything else.
2. Restrict installing and deleting apps. Closes the reinstall reset.
3. Set the clock to automatic and restrict time-zone changes. Closes the midnight reset.
4. Decide about browsers explicitly. Either add website limits, or accept that the behaviour will move there and stop being surprised.
5. On Android, turn on the App limits PIN — it is the built-in switch that makes a timer hold, and it ships off. Then grant autostart and battery exemptions by hand, and re-check them after updates, because otherwise everything above is theatre on a device that has stopped running your blocker.
6. Put something at stake that is not willpower. Time-based friction gets cheaper the more you need it. A cost does not.

That last one is what we build. Last Ferry gives the apps that eat your day one shared daily budget, and when it runs out they lock. You can still get past the lock — but it costs real money from a balance you topped up in advance, and the price rises with each unlock you buy that day. The point is not the money. The point is that the escape hatch has a price tag that does not fall as the night gets later.

It has the same holes as everything else, and we would rather you hear that here: it does not cover browsers, and on Android nothing survives a determined uninstall. What it does not have is a free door.