Can you block AI-generated videos on YouTube?
Partly. There is no setting in YouTube that hides AI-generated videos as a category, and no tool can detect them perfectly. What does work is filtering on the words in a video's title, description, and channel name, which catches the large share of AI content that announces itself in text.
That is a real limitation rather than a temporary one, and it is worth understanding before you install anything — including ours.
What can YouTube do about AI videos on its own?
Not much directly. You can pick Don't recommend channel on a video's menu, which suppresses one channel at a time, and creators are asked to disclose synthetic media, though that label is self-reported and inconsistently applied. Neither gives you a switch for the category as a whole.
Don't recommend channel
Open the three-dot menu on any video card and choose it. This works, and it is free, and it is worth using on the worst repeat offenders. The catch is that AI content tends to come from a long tail of channels rather than a few, so you are playing whack-a-mole.
The disclosure label
YouTube asks creators to flag realistic synthetic content. When it is applied you will see a note in the description or on the player. Because it depends on the uploader being both aware of the rule and willing to follow it, you cannot treat its absence as evidence that a video is human-made.
Not interested
Marking individual videos as Not interested nudges recommendations over time. It is slow and indirect, and it only affects suggestions rather than search results.
How does a keyword filter catch AI videos?
It reads the text YouTube already shows next to each video — the title, the channel name, and any description text on the card — and hides the card when that text matches a list of AI-related words and phrases. It runs on the video card, before you watch anything, so nothing has to be analysed or uploaded.
This works better than it sounds, because a lot of AI-generated content is actively marketed as AI-generated. Titles naming the model used, channels built entirely around generated content, and descriptions listing the tools involved are all plain text a filter can match.
It is also fast and private in a way that video analysis could never be. Nothing about your viewing is sent anywhere, because the only thing being examined is text that was already on the page in front of you.
What will a keyword filter miss?
Anything that does not say so in text. A fully AI-generated video with an ordinary human-sounding title will pass straight through, because the filter reads words rather than pixels or audio. No consumer tool reliably detects AI generation from the video itself, and anyone claiming otherwise is overstating it.
The honest way to think about a keyword filter is that it thins out the obvious cases rather than guaranteeing a clean feed. For most people that is the difference between a Home page that feels overrun and one that feels normal again, which is a worthwhile result even though it is not a complete one.
A note on tools that promise more: some extensions claim to detect AI video directly, and some use a shared community blocklist where users label channels. Crowdsourced lists genuinely help, and they also inherit whatever the crowd got wrong. Neither approach is magic, and it is fair to be sceptical of any product that says otherwise.
How Zenfeed handles it
Zenfeed's Rest from AI feature matches AI-related keywords and phrases in a video's text and blurs the matching cards on Home, Subscriptions, and search results. On YouTube it works as a timer rather than a permanent switch — you start it for a set number of minutes, and everything comes back automatically when it ends.
YouTube support is off until you turn it on, in the Sites section of the popup, because it needs a separate permission. There is also an optional toggle for the Shorts shelf, and custom keyword blocking if you want to hide something specific that has nothing to do with AI.
It reads text, not images or audio, so everything in the section above applies to it too. If you want the reasoning behind making it a countdown instead of a permanent block, that is written up in why Rest from AI is a timer, not a permanent block.