The three levels

iOS 27 puts web control in one place: Settings → Family → [Child's Name] → Apps & Websites → Restrictions → Filtering. Three levels, in increasing order of freedom:

  • Approved Websites Only — the child visits exactly what you've allowed, nothing else. For the youngest kids.
  • Ask to Browse — the open web, one request at a time: your child asks to visit a new site, you approve or decline from your phone, and approval lasts unless you revoke it. On by default for children under 13.
  • Limit Adult Websites — the filter runs, known adult sites are blocked, everything else passes. On by default for children under 18.

Pick the level that matches the kid in front of you, not the scariest story you've read.

Blocking one specific site

For the site that's fine for adults and wrong for your kid — or the one that ate last weekend:

  1. Settings → Family → [Child's Name] → Apps & Websites
  2. Find the site among the entries (or open the Blocked list).
  3. Block Website, confirm.

The site stops loading in Safari and other supported browsers on the child's device. Unblocking is the same path backwards, which matters: a block you can't reverse is a block you'll be reluctant to set.

Everything you've approved or blocked lands in the Allowed and Blocked lists inside Apps & Websites — one screen, the whole policy, reviewable in two minutes.

Allow lists: approving ahead of time

The same lists work in the other direction. Before the school project starts, allow the five sites it needs — then the requests your child sends are the interesting ones, not "can I visit wikipedia.com" for the ninth time. Pre-approving the homework layer and request-gating the rest is the combination that keeps Ask to Browse livable for both of you.

Ask to Browse in practice

The request lands on your phone with the site's name. Approve, and it's available from then on; decline, and it isn't. The system's real feature is the record: over a month of requests, you learn exactly where your child's curiosity lives — and the requests become conversations instead of settings.

Expect the volume to be the signal. When a twelve-year-old sends fifteen requests a day, the gate is the bottleneck and you should graduate them to Limit Adult Websites. When a nine-year-old sends three, stay put.

Which browsers the filter covers

Apple's filtering works in Safari and other supported browser apps — the phrase to remember. Some apps carry built-in webviews that never pass through the filter, which is why the second line of defense is on the App Store side: age ratings and app approvals. The full picture of where Apple's restrictions end is in iPhone restrictions for children.

What web filtering can't do

Honest boundaries, stated once and remembered:

  • It's not exhaustive. New sites appear faster than any filter classifies them.
  • It judges sites, not moments — a site that's fine at 3 p.m. may not be what your kid needs at 10 p.m., and no filter makes that call.
  • It doesn't reach inside apps. Social feeds, in-app browsers, and chat links live outside its jurisdiction.

A filter is a seatbelt, not a wall. It reduces the odds of the bad afternoon; it doesn't repeal probability. The thing that actually closes the gaps is the child who tells you what they saw — and that child exists only if reporting feels safe, a topic with no settings screen attached.

Removing blocks as they grow

The graduation path runs in order: Approved Websites Only → Ask to Browse → Limit Adult Websites → off, replaced by conversations. Walk down the levels deliberately, one school year at a time, and say so out loud when you do — a filter that disappears silently teaches nothing, but a filter that gets earned off is a lesson in trust that pays for itself.

The reference for where web filtering sits among all the other settings is parental control settings for iPhone, and the complete first-configuration walkthrough is our parental controls guide.

Review the lists monthly

The Allowed and Blocked lists are the one screen where your whole web policy is visible — and they tell a story if you read them: what the child requested, what got approved in a hurry, what's been blocked since the phone was new and nobody remembers why. Once a month, two minutes: walk both lists, prune the stale entries, and notice the patterns. A blocked list that keeps growing in one direction is a map of where your child's curiosity is heading — and a far better prompt for a conversation than any usage report.

A list maintained this way stays proportionate. A list that's only ever added to becomes a fence nobody remembers building, and fences without reasons are the first thing teenagers dismantle.