Skip to content

Guides

YouTube Embeds in a Website App: Fixing a Device and Network Abuse Rejection

Reviewers have cited YouTube background play, ads and overlays in website apps. Here are the rules, a five-step phone test and the smallest fixes before you resubmit.

10 min read

If Google Play rejected your website app under Device and Network Abuse and your site embeds YouTube videos, the likely trigger is how the video behaves inside the app: audio that keeps playing in the background, ads or overlays near the player, or autoplay where nobody can see it. Google's policy bans using a service in a way that breaks its terms, and YouTube's terms contain specific player rules. This guide lists those rules (checked on November 14, 2026), a phone test that catches the common failure, and what to change before you resubmit.

What does Device and Network Abuse mean for a YouTube video?

Google Play's Device and Network Abuse policy bans apps that interfere with a device, network or service in an unauthorized way. One of its listed examples is an app that accesses or uses a service or API in a manner that violates its terms of service. The version of the page I read on November 14, 2026 does not name YouTube. Older rejection messages quoted on developer forums did, and one told a developer not to enable background play of YouTube videos. So treat the YouTube link as how reviewers have applied the rule, not as wording on the current page.

Google does not publish reviewer notes, which means every cause below that comes from a forum thread is an anecdote, not a rule. The YouTube rules, by contrast, are written down.

Which YouTube player rules matter for a website app?

YouTube's Developer Policies and its Required Minimum Functionality page cover the embedded player. Both pages showed a last-updated date of November 6, 2026. The table below translates the parts that a website owner can actually affect.

YouTube embedded player rules and what they mean on a website that becomes an app
RuleWhat it means on your pagesWhere it comes from
No background playerFeatures that play audio or video from a player not shown on the page, tab or screen the user is viewing are prohibited. In an app, playback should stop when the user leaves the screen.Developer Policies, III.I.9
Nothing in front of the playerNo frames or other visual elements over any part of the player, controls included. Sticky bars, chat widgets and cookie banners are the places to look; applying the rule to them is our reading.Required Minimum Functionality, Overlays and frames
Autoplay limitsAutoplay may not start until more than half the player is visible, and a page or screen may not autoplay more than one YouTube player at once.Required Minimum Functionality, Autoplay
Minimum sizeThe player viewport must be at least 200 by 200 pixels. YouTube recommends at least 480 by 270 for a 16:9 player.Required Minimum Functionality, Embedded player size
Don't alter the player or its adsNo modifying, building on or blocking any part of a YouTube player, and no modifying, replacing or blocking ads YouTube serves. Injected CSS that hides part of an embed is covered by our reading of this rule.Developer Policies, III.I.5 and III.I.6
Advertising around the playerSelling ads, sponsorships or promotions placed on or within YouTube video or the player needs YouTube's written approval.Developer Policies, III.G.1

Why do website apps get caught by this?

In a browser, a tab that goes to the background is usually quieted by the browser. In an app, the page runs inside a WebView that the app controls. The documentation for WebView.onPause(), as reproduced in Microsoft's Android API reference, says it makes a best-effort attempt to pause processing such as animations and geolocation, and that it does not pause JavaScript. That is a weak guarantee for a video that is still playing.

Developers who report this rejection describe several different causes. A video in a WebView kept playing after the app moved to the background, reported on Stack Overflow, the Solar2D forum and the B4X forum. Banner ads shared the screen with an embedded video, reported on Stack Overflow and Solar2D. One app loaded a Google News page that contained YouTube videos. Another team traced it to videos it linked that were not the uploader's to share, and removed YouTube altogether. Pausing the WebView fixed some cases. Others found it was not enough, including a commenter who said audio kept playing on Android 9.

One more detail from YouTube's policy matters for your privacy answers: when the embedded player loads, it shares some basic user data with YouTube, even before anyone presses play. Reflect that in your Data safety form.

How do I test for background play before I submit?

  1. 1

    Install the release build

    Use a real phone, not only a browser preview. This is the build the reviewer will install.

  2. 2

    Start a video

    Open the page with your embedded YouTube player and press play.

  3. 3

    Press Home

    Wait ten seconds and listen. Any sound means the player is still running while the app is off screen.

  4. 4

    Lock the screen

    Listen again. Some reports describe audio that continued only after the screen turned off.

  5. 5

    Try the awkward pages

    Repeat on a page with two embeds, a page where a cookie banner or chat widget overlaps the player, and a page that shows ads.

What should I change if I've already been rejected?

Open Play Console, go to Policy and programs, then Policy status, and read the exact policy name before changing anything. Our guide to WebView rejections covers that screen and the resubmission steps. Then pick the smallest change that removes the problem:

  • Replace the embed on app-facing pages with a thumbnail that opens the video in YouTube. That moves playback outside your WebView. This is our inference; Google has not confirmed that it is exempt.
  • Turn autoplay off and keep one YouTube player per page.
  • Move ad units, chat widgets and cookie banners away from the player.
  • Remove injected CSS or scripts that change or hide any part of an embed.
  • If the videos are not yours, remove them or get permission from the owner.

Resubmit with a higher version code and a short note that says what changed. If the rejection mentions user-generated content rather than video, read Google Play's UGC policy for website apps instead.

Frequently asked questions

Does Google Play ban YouTube videos in WebView apps?
I found no blanket ban in the policy pages I read. The Device and Network Abuse policy bans using a service against its terms, and YouTube's terms restrict background players, overlays and some advertising. Most fixes reported on developer forums changed how playback behaves; one team removed YouTube entirely.
What does background play of YouTube videos mean?
It means a video or its audio keeps playing when the user is no longer looking at it, for example after pressing Home or locking the phone. YouTube's Developer Policies prohibit features that play from a player not shown on the screen the user is viewing.
Is a YouTube link safer than an embedded player?
A link that opens YouTube in its own app or browser takes playback out of your WebView, so it avoids the background-player problem in practice. I have not seen Google confirm that it is exempt, so test the build and mention the change when you resubmit.
Can banner ads next to a YouTube video cause a rejection?
YouTube requires written approval to sell ads placed on or within its video or player. Developers have reported rejections when banner ads shared a screen with an embedded video. Whether a particular layout passes is the reviewer's call.
Where do I find the exact reason for my rejection?
In Play Console, open Policy and programs, then Policy status. It names the policy and the app version it applies to. The rejection email is often vaguer than that page.