How to block porn on iPhone (free)
Your iPhone has a free porn blocker built in. Here's how to switch it on in two minutes, how to make it hard to undo, and when a porn blocker app is worth it.
Block porn on iPhone with Screen Time
- Open Settings > Screen Time and tap Content & Privacy Restrictions. Switch it on.
- Tap App Store, Media, Web & Games (older iOS: Content Restrictions) > Web Content > Limit Adult Websites.
- Back in Screen Time, set a Screen Time passcode. Ask someone you trust to type it, so you don't know it.
This blocks most adult sites in Safari and in apps that use Apple's web view.
Make it hard to undo
- Someone else holds the passcode.
- Delete other browsers you don't need.
- Charge your phone outside the bedroom.
Why it matters: Urges rise, peak and fall like a wave. In one study, smokers taught to watch the urge instead of fighting it smoked less over the next week.[1] A blocker only has to last longer than the urge.
Best porn blocker app for iPhone: what to look for
- Hard to switch off in a weak moment (not one toggle in Settings).
- Private: your browsing shouldn't be sent to anyone.
- Help in the moment, not just a block page.
Quit90's blocker uses Apple's own Screen Time filter, so it works in Safari and every app's browser. Switching it off means typing a long promise word for word, and what you browse is never sent to us. See the best quit porn apps compared.
Questions
How do I block porn on my iPhone for free?
Open Settings > Screen Time > Content & Privacy Restrictions, switch it on, then go to App Store, Media, Web & Games > Web Content and choose Limit Adult Websites. Set a Screen Time passcode that someone else chooses.
Does Screen Time block porn in all apps?
It blocks most adult sites in Safari and in apps that use Apple's web view. Apps with their own browsers or content can get around it, so remove the ones you don't need.
Sources
- Bowen S, Marlatt A (2009). Surfing the urge: Brief mindfulness-based intervention for college student smokers. Psychology of Addictive Behaviors 23(4):666-671. www.semanticscholar.org