YouTube Shorts Not Working? How to Tell an Outage From a Problem on Your Phone

Before you delete anything, run the cheapest test there is. Open youtube.com in a phone browser rather than the app, then try the app on a different network. If Shorts scroll in the browser but freeze in the app, the fault is local and the rest of this page applies. If they fail on every device in the house, the problem sits on YouTube's side and nothing on your phone will fix it.

YouTube announces confirmed disruptions through the @TeamYouTube account and the Known Issues pages in the Help Center. Neither updates instantly. In a real outage the first signal is a flood of identical reports on outage trackers, ahead of any official acknowledgement. Note the exact time it started. In a report, that timestamp is worth more than any description of the annoyance.

Work these in order and stop when Shorts come back.

On desktop, add one step. Disable extensions, ad blockers especially, and load the page in a private window. Extensions that rewrite the player break Shorts scrolling more often than the regular watch page, because the feed swaps players as you swipe.

Freezing is usually not a bug. The feed preloads the next video while you are still watching the current one, so a connection that handles a normal video comfortably can stutter here. More work at once. On a weak signal you get a frozen frame with audio continuing, or a black screen that clears after a swipe.

Device memory is the second common cause. Shorts decode continuously as you scroll, and on an older phone with a dozen apps resident in the background the decoder loses its slot. Close them and try again before blaming YouTube.

One setting produces symptoms people file as faults: under Settings, Data saving, capped quality makes Shorts arrive blurry and buffer oddly on cellular. A second setting gets blamed wrongly. YouTube documents Playback in feeds, under Settings then General, as covering the muted previews on the Home tab and in search results. It says nothing about the Shorts player, which starts on swipe.

Creators report a different failure: the upload succeeds and the video does not behave like a Short. YouTube sorts a video into Shorts by shape and length, so a clip longer than the three-minute cap in force as of September 2026, or one that is not vertical or square, publishes as a regular video whatever the description says. Adding #Shorts to the title does not override the file itself.

Processing is the other explanation. A fresh Short sits in processing while high-resolution versions render, and during that window it plays badly or stays missing from the Shorts tab on your channel. YouTube does not publish how long that takes, so give it a while before calling it a fault.

This is the version of the question that has nothing to do with playback. YouTube does not publish how the Shorts feed selects what to show anyone. There are no weights on record, so anybody explaining the mechanism in confident detail is guessing. What you can observe is your own data in YouTube Studio, under the Shorts labels: Shown in feed counts the times your Short appeared in the Shorts feed, and Viewed (vs. swiped away) gives the share who stayed.

That split is the honest signal. A high Shown in feed count with heavy swipe-away means the Short is being shown and rejected in the first second or two, a problem with the opening frame. A low one means it was barely shown, which editing the hook will not fix. If the feed is the real goal, what going viral on Shorts actually takes is a separate read.

The first hours are where creators go looking for meaning, and Studio is the only place holding any of it, so watch the Shown in feed line rather than reading intent into how it moves. If your channel keeps stalling there, a service that puts early views on a Short is one of the things creators buy, and the limit is worth stating: it raises the count printed on the video, and whether the feed behaves differently afterwards is not something anyone outside YouTube can tell you.

Analytics labels are where a working Short gets mistaken for a broken one. Dashboards bucket traffic under names that explain nothing. On YouTube, Shorts feed views and views from other surfaces are broken out separately, and a drop in one while the other holds is not an outage. Since 24 August 2026 a view counts from the moment playback starts, while the older definition is reported alongside it as an engaged view, so those lines can diverge without anything being broken.

Usually one number answers the question people are actually asking and gets ignored for sitting below the headline figure.

One warning about the money column. YouTube publishes no flat rate per thousand Shorts views. Shorts ad revenue goes into a monthly pool allocated by engaged views, monetizing creators keep 45 percent of their allocation, and the amount moves with your niche, your viewers' countries, the season, and advertiser demand that week. What a view is worth in practice is covered in how views on YouTube turn into money.

Some Shorts fail only for you. Restricted Mode, under Settings then General on mobile and the profile menu on desktop, filters anything flagged as mature and quietly removes Shorts from the feed. Supervised accounts behave the same way. Age-restricted Shorts will not play at all when you are signed out.

Regional availability is the other. A Short can be blocked in your country by the uploader or by a copyright claim, and the link keeps working while playback refuses. If audio has gone silent while the picture still moves, look for a claim on the soundtrack rather than a fault in the app.

If you have been through all of it and Shorts still fail, report it with details: device model, OS version, app version from the Settings screen, network type, and whether the same Short plays in a desktop browser. Most in-app reports draw no reply, so write for the one that might: those details let a stranger reproduce the failure. "Shorts not working" leaves nothing to reproduce.

Either YouTube has a disruption or the fault is on your device, and one test separates them. Open the same Short in a phone browser and on a second network. If it plays there and fails in the app, clear the app cache, update the app, and check free storage. If it fails everywhere, check the @TeamYouTube account and the Known Issues pages in the YouTube Help Center, and wait it out.

The usual causes are a stale app cache or an app build that is behind. A phone with almost no free storage does it too, because the player cannot buffer the next clip in the queue. On desktop, extensions that rewrite the player are a frequent cause, so load the page in a private window with them disabled. One popular suspect is innocent: Playback in feeds, under Settings then General, is documented as controlling the muted previews on the Home tab and in search results, and the Shorts player runs on swipe.

When one video fails and everything else scrolls normally, the video is the problem rather than the app. A Short can be age-restricted, which stops it while you are signed out, or unavailable where you are because the uploader limited it or a copyright claim landed on it. A silent picture usually means a claim on the soundtrack. A clip you uploaded yourself may still be in processing, or may have published as a regular video because its length or shape fell outside the Shorts format.