What "blocking an app" actually means

Four verbs, and parents use them interchangeably. iOS doesn't:

  • Block — the app stays installed but is dimmed on the Home Screen and won't open. Reversible with a tap.
  • Restrict — apps above a chosen age rating can't be installed or, if already present, won't open. This is a class of apps, not a name.
  • Limit — the app works, until the daily allowance runs out. Time is the gate, not the door.
  • Hide — removing an icon from the Home Screen is an organizational gesture, not a control. It hides nothing from a child who can search.

This article is about the first three. If you came here for the fourth, no judgement — just know that the app is still on the phone, four swipes from the Home Screen.

Blocking an installed app

In iOS 27, managed from your device:

  1. Settings → Family → [Child's Name] → Apps & Websites
  2. Find the app in the list (or tap through Allowed and Blocked lists).
  3. Block App, confirm. The app dims on the child's Home Screen and won't launch.

Unblocking is the same path backwards. Data stays intact either way — blocking doesn't delete the app or its contents, which is the point: a reversible decision you can actually reverse.

Blocking by age rating

For classes of apps rather than names: in the child's Apps & Websites → App Store settings, set the rating ceiling (9+, 12+, 17+). Nothing above the ceiling installs, and if something above it is already installed, it won't open. This covers the apps you don't know exist yet — which, if history is any guide, is most of them.

Regional note: in the EU, apps distributed outside the App Store can appear as "unrated" — decide whether unrated means blocked, and check what your child's device allows.

Stopping downloads entirely

The strongest form: Apps & Websites → App Store → Installing Apps → Blocked. Nothing installs from the child's device at all; if the phone needs a new app, you install it. This is the right setting for the youngest kids and a heavy-handed one for everyone else — for a nine-year-old, silence is golden; for a twelve-year-old, Ask to Buy (leave installs allowed, approve each download on your phone) is the same safety with none of the bottleneck. The install-side mechanics are in our parental controls guide.

When a limit beats a block

The question to ask before blocking: is the problem what the app is, or how much it's used?

  • What it is — a messaging app full of strangers, a 17+ game on a 9+ kid — block it.
  • How much it's used — the puzzle game that ate August — limit it. Time Allowances exist for exactly this: how to set app limits on a child's iPhone covers them in full.

Blocks for time problems teach the wrong lesson: that the fix for a habit is the removal of a thing. The habit relocates. It always relocates.

What you cannot do

Honest boundaries, because pretending otherwise gets parents burned:

  • You can't block a feature inside an app. The chat inside the racing game, the DMs inside the social app — the app is all-or-nothing. If the chat is the problem, the app is the unit.
  • You can't block what isn't installed. Pre-emptive blocking isn't a thing; the rating ceiling and Ask to Buy cover the future instead.
  • You can't block apps on someone else's phone. The borrowed device at a friend's house runs whatever runs there — which is why the conversation matters more than the block list over time.

The full map of what iOS can and can't restrict is in iPhone restrictions for children, and the reference for every related setting is our parental controls guide.

After the block: the conversation

A block without a word attached is a locked door with no note. Say why, briefly, once: "that app's chat isn't for twelve-year-olds; here's what I saw." The block holds longer when it comes with a reason the child can repeat to their friends — because they will be asked, and "my parents are insane" is a worse answer than "it had an open chat."