Skip to main content
Concept

Why this matters:A short explanation you can quote back when a child, teacher or relative asks why this rule exists at all.

Device
Any device
Age band
Ages 10–12, Ages 13–15, Ages 16+
Jurisdiction
global
Software version
App-dependent (verified against help pages retrieved 2026-08-16)
Last checked
2026-08-19

A parent blocks the YouTube app. The child is still watching YouTube, inside a game. A parent blocks TikTok. The child is still watching TikTok videos, inside a chat app.

The conclusion the parent draws is the block did not work.

The block did not work, but the reason is not the one parents usually suspect.

The reason is that the YouTube the child is watching is not the YouTube app. The TikTok the child is watching is not the TikTok app.

The video player is embedded in another app. The block on the YouTube or TikTok icon does not reach it.

This page explains the shapes of video that arrive without the named app being open, and the four documented reasons a YouTube or TikTok block does not catch them.

The article is verified against help pages retrieved on 2026-08-16 [source: google-yt-supervised] [source: google-youtube-options] [source: tiktok-family-pairing].

The article on why blocking an app does not block a service, more generally, is Why Roblox, Discord and YouTube are hard to block. This page is the same idea, applied specifically to video.

Definition

Embedded video is a video that plays inside another app or on another website, using a player that is not the original service’s own app.

A signed-out web view is a video on a service’s website. It is reached through a browser. No account is signed in.

A short-video feed is a vertically-scrolling feed of short videos that lives inside a service that is not primarily a video service.

Examples: a chat app, a social app, a learning app, a game, a fitness app.

The three shapes are the three documented ways a video block on a named app fails to reach the video the child is actually watching.

A block on the YouTube or TikTok icon prevents the named app from running on the device.

It does not reach an embedded YouTube or TikTok video in another app. It does not reach a YouTube or TikTok video on the web with no account signed in. It does not reach a short-video feed in a service the household has not blocked.

Scope

This article covers the four documented shapes a video block misses.

It covers YouTube, TikTok, and the short-video feeds in the services this wiki covers.

Those services are Snapchat, Instagram, Messenger, WhatsApp.

It does not cover the per-service setup. For setup, see Settings inside the apps, which is the step-by-step companion.

It does not cover the iOS or Android device layer. For that, see Reading your child’s Screen Time report.

It is not a circumvention guide. The wiki’s trick database documents the specific shapes of bypass in a way that does not instruct.

Why this matters

The first reason this matters is volume.

In Germany, 73% of 6- to 13-year-olds use WhatsApp weekly [source: mpfs-kim2024]. 42% of the same age group use TikTok regularly.

This is despite TikTok’s 13+ terms of service.

Among 12- to 19-year-olds in Germany, TikTok is regular use for 53% [source: mpfs-jim2025].

In the US, 73% of 13- to 17-year-olds report daily YouTube use, the highest of any platform tested [source: www-pew-teens-2024].

The volume makes the question of which YouTube a household has blocked worth asking.

The second reason is that the household’s mental model of a video block usually assumes the named app. That model is increasingly wrong, because video is increasingly embedded.

Independent testing notes that once a child has downloaded an app, the parent has “no control, insight, or management of what your child sees or experiences” inside it [source: wirecutter-parental-controls].

That statement is most consequential for video, because video is the content type most often embedded in non-video apps.

The third reason is that the eSafety Commissioner in Australia explicitly notes that under-16s in Australia may still see publicly available social-media content.

This content does not require login. It specifically names most YouTube videos [source: esafety-2025].

A YouTube block on the YouTube app does not reach that material.

The four shapes named below are the documented reasons.

Shape one: the YouTube player embedded in another app

YouTube maintains a public embed API. Any app or website can use it to show a YouTube video inside its own interface.

Three documented places this happens.

  • Games and gaming platforms. A game that has a Watch button, a tutorial section, or a community feed with a Latest videos panel can open the YouTube player without opening the YouTube app.

    The game is not a video app. The YouTube app icon is not on the screen. A YouTube video is playing.

  • Learning and tutorial apps. A learning app that has a How to clip, a Watch link, or a Related videos section can open the YouTube player inside the learning app.

    The YouTube branding is visible inside the player but not as a separate app on the device.

  • Fitness and recipe apps. A fitness app that shows a form-check video, a recipe app that shows a technique clip, and a music app that shows a lesson video all open the YouTube player the same way.

    The YouTube content is on screen. The YouTube app icon is absent from the home screen.

In each case, the YouTube content setting on the supervised YouTube account does not apply.

Google documents the supervised-account content setting as applying in the YouTube app and on the YouTube website when the supervised account is signed in [source: google-yt-supervised].

An embedded player in a third-party app is neither of those things. It is the YouTube player running inside another app, with the YouTube account signed in or signed out. The supervised-account content setting does not reach it.

The block on the YouTube app icon does not reach it either. The YouTube app is not running. The YouTube content is.

Shape two: the signed-out or public web view

A YouTube video can be watched on youtube.com, in any browser, with no account signed in.

The supervised-account content setting on YouTube applies in the YouTube app and on the YouTube website when the supervised account is signed in [source: google-yt-supervised]. The setting does not apply when no account is signed in.

This is the most common reason a household sees YouTube watch time on a child’s device that does not appear in the supervised account’s own activity.

The trick database records this shape of access as a documented entry. It has a corresponding detection rule that distinguishes “no account” from “no viewing”.

The reason a household sees YouTube watch time is not that the supervised account has been circumvented. The reason is that the watch time happened on a web view that did not involve the supervised account at all.

The remedy is a device-level block on youtube.com in any browser. Not a service-level setting on YouTube.

The YouTube help page does not offer a setting that covers the signed-out web view. The page above (google-yt-supervised) describes the supervised-account content setting only.

Shape three: the short-video feed in a non-video service

The short-video feed is the most pervasive shape of embedded video today.

The pattern is the same in every service that has adopted it.

It is a vertically-scrolling feed of short videos. It is presented inside a service that is not primarily a video service. The videos are playable in place.

Three documented places the pattern appears.

  • Snapchat. Snapchat is a chat app with a Discover surface, which is a short-video feed of publisher content.

    The Snapchat Family Center settings are about the chat surface, the My AI surface, and the privacy settings.

    The Family Center is explicit that it shows who a teen chatted with, not what they saw in the Discover feed [source: snapchat-snap-fc1].

    A block on the YouTube app does not reach the Discover feed. A Snapchat Family Center link does not reach the Discover feed either.

  • Instagram and Messenger. Instagram and Messenger are Meta products, with the Meta AI topic-categories supervision as the documented parent surface [source: meta-ai-insights].

    Instagram has a Reels surface, which is a short-video feed inside the Instagram app. Messenger has an AI surface, which can surface short-form media.

    A block on the YouTube app does not reach Reels. A Meta Family Center link does not reach Reels either.

    Reason: Reels is part of the Instagram app. The parent-side supervision is metadata, not content [source: meta-ai-insights].

  • TikTok. TikTok is a short-video service by design.

    TikTok’s Family Pairing is a parent surface on the account. It has rules on screen time, restricted mode, DM, and search discoverability [source: tiktok-family-pairing].

    A block on the YouTube app does not reach TikTok. A TikTok block on the TikTok app icon does not reach TikTok on the web.

The short-video feed is the documented reason a block on one video service does not reach a household’s concern about video in general.

Shape four: the in-app browser that opens a video

Many apps have a built-in browser, also called an in-app web view or a web sheet.

The pattern is the same. A link inside the app, when tapped, opens a browser window inside the app. The address bar is absent or hidden. The video on the destination page is playable in place.

Three documented places the pattern appears.

  • A chat app with a link. A WhatsApp message that links to a YouTube video, a Snapchat message that links to a TikTok video, and a Discord message that links to a YouTube or TikTok video all open the in-app browser.

    The video plays inside the chat app.

  • A social app with a link. An Instagram post with a YouTube link, a TikTok bio with a YouTube link, and a Snapchat story with a YouTube link all open the in-app browser.

    The video plays inside the social app.

  • A game with a help link. A game with a How to play link, a Customer support link, or a Watch the trailer link can open the in-app browser and play a YouTube video.

    This happens without the YouTube app being on the device.

In each case, the in-app browser counts the time against the host app, not against the browser, on iOS Screen Time [source: wirecutter-parental-controls].

The reading-screen-time-report article documents this as the single most confusing reporting behaviour for parents.

A YouTube view inside WhatsApp shows up in the WhatsApp time on the report, not in a YouTube bucket. A YouTube block on the YouTube icon does not change this.

Why a YouTube block does not catch these four shapes

A YouTube block, in any of the four shapes this wiki covers, is a setting on the YouTube service or on the YouTube app.

The four shapes above are not the YouTube service or the YouTube app. They are other services, other apps, and other web views that show YouTube content.

A block on the YouTube app icon prevents the YouTube app from running.

It does not prevent a game from showing a YouTube clip. It does not prevent a chat app from opening a YouTube link. It does not prevent a web browser from opening youtube.com signed out.

A supervised YouTube account’s content setting prevents age-inappropriate content in the YouTube app and on the YouTube website.

This works when the supervised account is signed in [source: google-yt-supervised].

It does not prevent the YouTube player in another app from showing a video. It does not prevent the YouTube website from showing a video when no account is signed in. It does not prevent the YouTube content that arrives in an in-app browser through a link in another service.

A YouTube Restricted Mode toggle, set in the YouTube app, hides videos that YouTube has classified as restricted [source: google-youtube-options]. The toggle is a content filter inside YouTube, not a network-level filter, and it does not reach an embedded player in another app.

The YouTube Kids app is a separate, content-rated client for children. It has its own content levels and its own parent passcode [source: google-youtubekids].

The block the household wants is on the content, not on the player. The YouTube Kids content levels do not reach an embedded YouTube player in a non-YouTube app either.

This is the documented behaviour of every YouTube control this wiki has verified.

The same shape applies to TikTok. TikTok Family Pairing covers the account, not the embedded player [source: tiktok-family-pairing].

What does work for video in unexpected places

Three documented answers, in order of effectiveness.

  1. A network-level filter that blocks the video-domain hostname.

    A DNS service or a router that blocks youtube.com, youtu.be, and the YouTube embed API hostname at the network level.

    It prevents the YouTube player from loading in any app, on any device, on the network.

    The reach of a network filter ends at the network boundary [source: wirecutter-parental-controls]. The filter does not follow the child past the front door; the article on the network layer documents that limit.

  2. A device-level block on the in-app browser.

    iOS and Android both allow the household to disable in-app web views in the apps that have them. The setting is at the operating-system level, not at the app level.

    The trade-off is that the chat app no longer opens links. That can be the wrong trade-off for an older child.

  3. The household rule.

    The household conversation is the documented last line of defence [source: consumer-ftc-parental-controls] [source: saferinternet-technischer-kinderschutz].

    The eSafety Commissioner in Australia recommends the conversation as the layer that holds when the technical layer does not.

    The Commissioner explicitly notes that under-16s may still see publicly available social-media content [source: esafety-2025].

The order of effectiveness is the order above.

The network-level block is the strongest. The device rule is the most reliable. The conversation is the most flexible.

The four shapes named in this article are not solved by a single setting. Saying so honestly is more useful than naming a setting that will not hold.

What this article does not cover

This article is about video, and about the four documented shapes a video block misses.

It does not cover the per-service setup. For that, see Settings inside the apps. That page walks through the in-app controls on each service the wiki covers.

It does not cover the device-level block on creating a new account under a false birthdate. It does not cover the household rule on which devices the child is allowed to use, and at what ages.

For that, see Why Roblox, Discord and YouTube are hard to block. That page names the gaps that no setting reaches.

It does not cover the network layer in detail. For that, see The network layer: router, DNS and their limits.

The article is honest about what it does not cover.

The four shapes named here are the documented ones. The gaps above are the documented gaps.

A household that knows both is in a stronger position than one that knows only the names of the services.

Sources

  • google-yt-supervised — Google Support, Parental controls & settings for supervised kid accounts on YouTube. Primary source for the supervised-account content setting and its app-and-web scope [source: google-yt-supervised].
  • google-youtube-options — Google Support, YouTube options. Primary source for the Restricted Mode toggle [source: google-youtube-options].
  • google-youtubekids — Google Support, Parental controls for YouTube Kids profiles. Primary source for the YouTube Kids content levels and the standalone-client framing [source: google-youtubekids].
  • google-chrome-child-account — Google Chrome Help, Chrome and your child’s Google Account. Primary source for the browser-side supervision and the explicit statement that website restrictions apply to Chrome, not to every browser [source: google-chrome-child-account].
  • tiktok-family-pairing — TikTok Support, Family Pairing. Primary source for the two-sided setup and the account-level scope [source: tiktok-family-pairing].
  • snapchat-snap-fc1 — Snapchat Support, What is Family Center?. Primary source for the who not what framing and the explicit no-message-content statement [source: snapchat-snap-fc1].
  • meta-teen2 — About Instagram, New Instagram Teen Accounts: Default Settings. Primary source for the default protections [source: meta-teen2].
  • meta-ai-insights — Meta Help, Parents and guardians can see insights about what their teens ask AI. Primary source for the topic-categories framing of Meta AI interactions [source: meta-ai-insights].
  • wirecutter-parental-controls — Wirecutter / NYT, 2026 parental-controls review. Independent source for the in-app browser attribution-to-host-app behaviour [source: wirecutter-parental-controls].
  • esafety-2025 — Australian eSafety Commissioner, 2025 report. Independent source for the publicly-available-content statement [source: esafety-2025].
  • consumer-ftc-parental-controls — US FTC, Parental controls. Independent source for the one-layer framing [source: consumer-ftc-parental-controls].
  • www-pew-teens-2024 — Pew Research Center, Teens, Social Media and Technology 2024. Primary source for the 73% daily YouTube figure for US teens [source: www-pew-teens-2024].
  • mpfs-jim2025 — mpfs, JIM-Studie 2025. Primary source for the 53% TikTok figure for 12- to 19-year-olds in Germany [source: mpfs-jim2025].
  • mpfs-kim2024 — mpfs, KIM-Studie 2024. Primary source for the 42% TikTok figure for 6- to 13-year-olds in Germany [source: mpfs-kim2024].
  • saferinternet-technischer-kinderschutz — Austrian Safer Internet Centre, technical child-protection guidance. Independent source for the layered-approach framing [source: saferinternet-technischer-kinderschutz].

[source: google-yt-supervised] [source: google-youtube-options] [source: google-youtubekids] [source: google-chrome-child-account] [source: tiktok-family-pairing] [source: snapchat-snap-fc1] [source: meta-teen2] [source: meta-ai-insights] [source: wirecutter-parental-controls] [source: esafety-2025] [source: consumer-ftc-parental-controls] [source: www-pew-teens-2024] [source: mpfs-jim2025] [source: mpfs-kim2024] [source: saferinternet-technischer-kinderschutz]

Why trust this page?

Belief-disclosure in plain language. Everything the page claims is sourced; instructions are tested against the software version stated above; nothing is bought or affiliate-linked.

Standing of evidence
Primary (first-hand or regulatory source)
Tested against
App-dependent (verified against help pages retrieved 2026-08-16)
Last verified
2026-08-19

Sources used on this page, in the order they appear:

Statements quoted from a manufacturer that are still checked against independent sources are marked [claim]. They describe what the vendor says, not what is independently verified.

Next useful step

  1. Content
  2. Contact
  3. Any device