Block YouTube Shorts & Reels on Android (Keep the App)

You don't have an Instagram problem. You have a Reels problem. You opened the app to reply to one DM, and 40 minutes later you're watching a guy power-wash a driveway. The DM is still unanswered. That's why the real fix isn't deleting anything. It's learning how to block YouTube Shorts and Instagram Reels on Android without blocking the whole app.

Because "just delete the app" doesn't work when you actually need it. You need Instagram for the group chat. You need YouTube for the tutorial you saved. You need TikTok open because a client posts there. The infinite feed is the part that costs you the hour, not the whole app. Kill the feed, keep the inbox.

Most app blockers can't do that. They block by package name, all or nothing. This walks through the one mechanism that actually targets the feed surface itself, and how to set it up for free with no root.

The problem: you need the app, not the Shorts and Reels feed

Think about what you actually open these apps to do.

Instagram: reply to DMs, check a specific account, post a story. None of that is Reels. Reels is the tab you tap by accident, or the suggested clip that autoplays when you close a conversation.

YouTube: a how-to video, a podcast, a saved playlist, your subscriptions. Shorts is the bar that hijacks the home feed and the swipe-up gesture that drops you into an endless vertical scroll.

TikTok is the one app where the feed is the product, but plenty of people keep it for the messages, the Following tab, or because they post and need to check comments. The For You page is the part that swallows an hour.

In every case there's a useful core and a slot-machine wrapper bolted on top. Blocking the whole app throws out the core to kill the wrapper. That's why people uninstall, reinstall three days later, and feel like they failed. They didn't fail. The tool was too blunt.

Why blocking the whole app fails

There are two reasons this fails, and they feed each other.

The first is rebound. When you hard-block an app you actually depend on, you create friction you can't sustain. You miss a message. A coworker asks why you didn't see the tag. So you unblock "just for a minute," and the block is dead. App blockers that go all-or-nothing have a short half-life for exactly that reason.

The second is work. For a lot of people now, Instagram and TikTok are part of the job. Creators, marketers, small business owners, anyone who posts. Telling them to delete the app is telling them to quit their side income. They won't, and they shouldn't. The rebound and the work reason compound: the people who most need these apps open are the ones a blunt block punishes hardest, so they're the first to switch it off.

The fix isn't more willpower or a harsher block. It's a sharper one. Cut the specific surface that's costing you time and leave the rest alone.

How in-app feed blocking works on Android (no root)

Here's the part nobody explains clearly.

Android has a system feature called the Accessibility API. It was built so screen readers and assistive apps can see what's on screen and act on it for people who can't tap or see normally. It's a legitimate, documented part of the OS. Apps that use it have to declare it, and you have to switch it on by hand in Settings.

A feed blocker uses that same API to read the structure of the screen, not the pixels and not the content. Every Android view has an ID. When Instagram renders the Reels player, that view has a resource ID. Nudge, the open-source blocker this article walks through, watches for specific IDs like reel_recycler and reel_player_page_container. When one of those appears on screen, it means you're looking at the Reels surface. Nudge throws up a block overlay and bounces you out. The DM screen has different IDs, so it's left untouched.

Same idea for YouTube Shorts and the TikTok For You feed. The blocker isn't reading what the video is about. It's detecting which screen you landed on by its layout fingerprint, then blocking only that screen.

No root required. Root is for low-level system access, and this needs none of it. It runs on a stock phone with one permission toggle.

The honest tradeoffs: this is Android only, because iOS doesn't expose an equivalent screen-reading Accessibility API to third-party apps. And resource IDs can change when an app ships a redesign, so a feed blocker occasionally needs an update to keep matching. That's the nature of the approach. Anyone who tells you their feed blocker will never break is overselling.

What Accessibility permission actually sees (and what it can't do)

This is the trust question, and it's a fair one to ask before you toggle anything on. So let's settle it before the setup steps, not after.

Accessibility permission is powerful. An app that has it can read a lot. So here's what Nudge does and doesn't do with it. It reads the layout structure of the screen to match those resource IDs. It does not log your DMs, your captions, your search history, or anything you type. It doesn't store screen content. It's matching IDs to decide "block this screen or not," then forgetting the rest.

You shouldn't take that on faith from any app. Here's why you don't have to.

Nudge requests zero internet permission. Not "promises not to use the internet." It doesn't request the INTERNET permission in its manifest at all. Android enforces this at the OS level. An app without that permission physically cannot open a network connection. No servers to phone home to, no analytics, no ads, no account to create.

So even with Accessibility access, there's nowhere for your data to go. Nudge can read the screen structure to do its job, and it can't transmit anything, because the operating system won't let it. That's a structural guarantee, not a privacy-policy promise.

And because Nudge is open source, you don't have to believe any of this either. The code is on GitHub. The manifest is right there. Anyone can confirm there's no internet permission and no data collection. If you want the deeper write-up on that design choice, here's the full piece on an open-source app blocker with no internet permission.

Step-by-step setup (YouTube, Instagram, TikTok)

The first step is the same for all three: install Nudge, open it, and grant the Accessibility permission when it asks. Android routes you to Settings > Accessibility > Nudge, and you flip it on. That's what lets Nudge see the screen structure. After that, each platform is a couple of toggles.

Block YouTube Shorts

In Nudge, open the in-app blocking section and pick YouTube.
Toggle on Shorts blocking.
Open YouTube and swipe into a Short. You'll hit Nudge's block screen instead of the feed. Regular videos, search, subscriptions, and your playlists all still work.

That's it. The Shorts shelf on the home page and the swipe-up-into-Shorts gesture both get caught.

Block Instagram Reels and Explore

Open Nudge's in-app blocking and pick Instagram.
Toggle on Reels blocking. Optionally toggle Explore too, since the Explore grid is the other main rabbit hole.
Open Instagram. DMs, your feed of people you follow, stories, and posting all work. Tap the Reels tab or hit a suggested Reel and you get the block screen.

The point is surgical. You keep the social graph you chose. You lose the algorithmic firehose you didn't.

Block the TikTok For You feed

In Nudge's in-app blocking, pick TikTok.
Toggle on For You feed blocking.
Open TikTok. The Following feed, your messages, and your profile stay reachable. The For You page gets blocked.

If TikTok is pure entertainment for you with no work angle, you might want to block the whole app on a schedule instead. But if you keep it for messages or posting, blocking just the For You feed is the move.

Pairing feed-blocking with a delay-to-open pause

Feed blocking handles the surface. But there's a second habit worth breaking: the reflexive open. The hand reaches for the phone, the thumb finds the icon, and you're in before you decided anything.

Nudge has a delay-to-open feature for that. When you open a chosen app, it makes you sit through a short breathing pause before the app loads. A few seconds of "do you actually want to be here." It sounds trivial. It isn't. That gap is where the autopilot breaks and you get a chance to choose.

Stack the two. Block Reels and Shorts so the worst surfaces are gone, and put a delay-to-open pause on Instagram itself so even the useful opens are deliberate. You can also set a daily time budget on an app, so after, say, 20 minutes it locks for the day. Friction where you need it, access where you need it.

Nudge vs other feed blockers

Several apps target the feed problem, and they're not all the same.

Tool	Feed-level blocking	Price	Open source	Internet permission
Nudge	Shorts, Reels, TikTok feed, Explore	Free, no tiers	Yes	None requested
ScreenZen	Yes, blocks Shorts/Reels surfaces + intervention screens	Free (donation-supported)	No	Not audited
Shortstop	Shorts, Reels, TikTok, Snapchat Spotlight, Facebook Reels	Free	No	Not audited
ScrollGuard	Blocks short-form feeds	Freemium, paid extras	No	Not audited
Betimeful	Hides feeds across apps	Freemium, paid plans	No	Not audited

A few honest notes. ScreenZen is genuinely good and popular, with polished intervention screens, broad app support, and versions across Android, iOS, macOS, and Windows. It's completely free and donation-supported, with no premium tier. Its real tradeoff against Nudge is a closed codebase you can't audit. Shortstop is a solid multi-platform feed blocker, covering YouTube Shorts, Instagram Reels, TikTok, Snapchat Spotlight, and Facebook Reels, and it's free. ScrollGuard and Betimeful both target short-form feeds and both run a freemium model where the better features sit behind a paywall.

A note on the "internet permission" column. Nudge is marked "None requested" because its open manifest is public and you can confirm the INTERNET permission is absent. The other apps are closed source, so their exact permission lists aren't independently auditable from the outside, which is why they're marked "not audited" rather than assumed to leak data. ScreenZen, Shortstop, and ScrollGuard all describe on-device or privacy-friendly designs, and several look good on privacy. The difference is that with Nudge you don't have to take it on trust.

Nudge's edge is narrow and specific. It's fully free with no pro tier, it's open source so you can read exactly what it does, it's Android only, and it requests no internet permission so your data physically can't leave the device. If you want polish and don't mind a closed app you can't inspect, the others are reasonable picks. ScreenZen in particular is a strong free option if cross-platform support matters more to you than an auditable codebase. If you want auditable and free with a verifiable privacy guarantee, that's the gap Nudge fills. For a wider look at the category, see the best free app blockers for Android in 2026.

FAQ

Can I block Shorts but keep YouTube? Yes. That's the entire point of in-app blocking. Nudge blocks the Shorts surface specifically. Regular videos, search, subscriptions, and playlists keep working.

Does this need root? No. It uses Android's Accessibility API, which works on a stock unrooted phone. You toggle one permission in Settings.

Is it free? Yes. Nudge is 100% free. No subscription, no pro tier, no paywalled features. Open source.

Will it block the feed on every app? Nudge covers YouTube Shorts, Instagram Reels and Explore, and the TikTok For You feed. Those are the big short-form surfaces. Coverage depends on the app's current layout, and an app redesign can require an update to keep matching.

Is it safe to grant Accessibility permission? Accessibility is a powerful permission, so the safe move is to only grant it to apps you can verify. Nudge is open source and requests no internet permission, so even with Accessibility access it has no way to send your data anywhere. You can read the code yourself.

Why not just use Screen Time or Digital Wellbeing? Those tools work at the app level, not the feed level. They can limit total YouTube time, but they can't let you watch a tutorial while blocking Shorts. Feed-level blocking is the missing piece.

Try it

The fastest way in today is GitHub. Nudge is open source and currently at v1.5.6, so you can read the code, check the manifest, and confirm the no-internet-permission claim before you install anything: github.com/astraedus/nudge. Build it from source and you're running in a few minutes (the Play Store and F-Droid listings are in review, so GitHub is the quickest route while those land).

Block the feed. Keep the app. Get your time back.