iOS 26 Broke Screen Time's Private Browsing Block — Here's the Fix
A change in iOS 26 means "Limit Adult Websites" no longer covers private tabs automatically. Most guides haven't caught up. Here's what changed and what to do.
What changed in iOS 26
In iOS 17 and iOS 18, enabling "Limit Adult Websites" under Screen Time automatically covered private browsing tabs in Safari too. Adult content was blocked whether you were in a regular tab or a private one.
As of iOS 26, this is no longer the default behavior. "Limit Adult Websites" now applies to standard browsing but leaves private browsing tabs uncovered unless you take one additional step.
This is a significant change that most guides — including older articles on this exact topic — have not updated for. If your Screen Time setup was configured before iOS 26, you may have a gap you don't know about.
How to confirm whether you're affected
- Make sure "Limit Adult Websites" is turned on (Settings → Screen Time → Content & Privacy Restrictions → Content Restrictions → Web Content)
- Open a Private browsing tab in Safari
- Try accessing a site you know is filtered in regular tabs
If it loads in private mode but is blocked in regular tabs, your setup has this gap.
The fix: enable Supervised Mode
Supervised Mode is an Apple feature typically used for managed devices (schools, companies) but available to personal users. Enabling it restores private browsing coverage under Screen Time.
How to enable it: the cleanest method is through Apple Configurator 2 (free on Mac). Connect your iPhone, put it in supervision mode, and apply a minimal configuration profile. Apple's own documentation covers the steps. The process takes about 10 minutes and is non-destructive — your apps and data stay intact.
Once Supervised Mode is enabled, "Limit Adult Websites" covers private tabs again, matching the behavior from iOS 17/18.
Why this happened
Apple made this change as part of broader privacy updates in iOS 26 that adjusted how content filtering interacts with private browsing. From a user-privacy perspective, making private browsing "more private" even from system-level filters makes sense. From a self-restriction perspective, it's a gap in what most people believe their Screen Time setup is doing.
Don't assume your old setup still works
If you configured Screen Time before iOS 26 and haven't checked since the update, your private browsing may not be covered. This is worth verifying now, not the next time you notice a problem.