How to Block Apps on a Kid's iPhone: Parental Controls Explained
Managing what your child can access on their iPhone isn't just about setting rules — it's about using the right built-in tools to enforce them consistently. Apple provides a robust set of native controls through Screen Time, which handles everything from blocking specific apps to restricting entire content categories. Here's how it works, and what affects how well it works for your family.
What Is Screen Time and Why It Matters
Screen Time is Apple's built-in parental control system, available on iPhones running iOS 12 and later. It lets a parent or guardian set limits, block apps, restrict content, and — critically — lock those settings behind a separate passcode so a child can't undo them.
Screen Time is not a third-party add-on. It's built directly into iOS, which means it operates at the system level. Apps can't simply "run around" it the way they might with some software-based filters.
How to Set Up Screen Time on a Child's iPhone
To get started:
- Open Settings on the iPhone
- Tap Screen Time
- Tap Turn On Screen Time
- Select This is My Child's iPhone
- Set a Screen Time Passcode — this is separate from the device passcode and prevents your child from changing the settings
If your family uses Family Sharing, you can manage your child's Screen Time remotely from your own iPhone without touching their device. That's a meaningful advantage for families managing multiple kids or devices.
Three Main Ways to Block Apps
1. App Limits — Time-Based Blocking
App Limits let you set a daily time cap on specific apps or entire categories (like Social Networking, Games, or Entertainment). Once the limit is reached, the app grays out and becomes inaccessible for the rest of the day.
- Works across app categories or individual apps
- Resets at midnight daily
- Child can request more time, which you can approve or deny remotely
This approach is useful when you don't want to fully block an app but want to prevent hours of uninterrupted use.
2. Always Allowed — Whitelist Specific Apps
Under Always Allowed, you choose which apps remain accessible even during Downtime or after an App Limit is reached. Phone, Messages, and Maps are allowed by default, but you can customize this list.
Think of this as the exception list — everything not on it can be locked down when Downtime is active.
3. Content & Privacy Restrictions — Hard Blocks
This is the most direct way to block apps entirely. Under Content & Privacy Restrictions, you can:
- Block specific apps by age rating (4+, 9+, 12+, 17+, or none)
- Disable built-in Apple apps entirely (Safari, Camera, FaceTime, Siri, AirDrop, and others)
- Prevent installing new apps or making in-app purchases
- Block deleting apps
To access this:
- Go to Settings → Screen Time → Content & Privacy Restrictions
- Toggle it on
- Tap Allowed Apps to disable specific built-in apps
- Tap Content Restrictions → Apps to set an age rating cap
For third-party apps like TikTok, YouTube, or games, you primarily control access through the age rating filter — any app rated above your chosen threshold won't appear or will be blocked.
Downtime: Scheduling No-Phone Hours
Downtime lets you define a schedule during which only the apps on your Always Allowed list are accessible. Common uses include:
- Overnight (e.g., 9 PM to 7 AM)
- During school hours
- Homework time
When Downtime is active, apps show a small hourglass icon and can't be opened without your passcode override.
Key Variables That Affect How This Works
Not every setup produces the same result. Several factors shape what's actually enforceable:
| Variable | Why It Matters |
|---|---|
| iOS version | Screen Time features have expanded significantly since iOS 12; older versions have fewer options |
| Family Sharing setup | Remote management requires Family Sharing to be configured correctly with the child's Apple ID |
| Child's tech literacy | Older kids may find workarounds — like using a browser instead of a blocked app |
| Apple ID ownership | A child's Apple ID must be set up as a child account (under 13 in the US) for full parental controls |
| Whether a Screen Time passcode is set | Without it, settings can be changed directly on the device |
What Screen Time Doesn't Cover 📱
Screen Time is powerful, but it has limitations worth knowing:
- Web-based workarounds: Blocking YouTube the app doesn't automatically block YouTube in Safari unless you also restrict web content
- iMessage and communication: You can limit who a child contacts under Communication Limits, but it requires contacts to be set up carefully
- VPNs: A determined older child could potentially use a VPN to circumvent some restrictions — disabling VPN configuration under Content & Privacy Restrictions helps here
- Third-party browsers: If Safari isn't blocked and other browsers aren't restricted, content filters may be bypassed
For each of these gaps, Screen Time has a corresponding control — but they're not all enabled by default.
The Age and Setup Spectrum
A parent setting up controls for a 7-year-old will likely use a very different configuration than one managing a phone for a 14-year-old:
- Younger children typically benefit from strict whitelists, Downtime schedules, and no Safari access
- Tweens often need more nuanced App Limits rather than hard blocks, plus Communication Limits
- Teenagers present a different challenge — where technical restrictions may work less reliably, and Screen Time becomes one layer of a broader conversation
🔒 The right balance of restriction vs. access depends on your child's age, maturity, and which specific apps or behaviors are the actual concern.
Screen Time Passcode Is Non-Negotiable
One detail that's easy to skip but critical: always set a Screen Time passcode that's different from the device unlock passcode. If both use the same code — or no Screen Time passcode is set — the restrictions offer no real protection. A child who knows the device passcode could simply turn Screen Time off.
What works well for one family's setup may be too restrictive or too lenient for another. The tools are consistent; the configuration that fits depends entirely on the child, the devices in use, and what you're actually trying to prevent.