I built a free extension that
hides AI-labelled posts.
A number of people said they'd pay for something that clears AI-generated content out of their feed. So I built the simplest version that could actually work — one that uses the AI-content labels Facebook, Instagram, Google, and LinkedIn already apply, and just hides what they've already flagged.
I kept seeing the same comment on Facebook — people saying they'd genuinely pay for a tool that cleared AI-generated images, video, and text out of their feed. Not because they're against AI, but because they can't always tell the difference anymore, and that uncertainty bothers them more than the content itself.
I didn't want to build this as a business. It costs me time, not money, and if someone wants to send a few rand my way for the effort, that's a bonus, not the point. So the brief I set myself was: build the simplest version that actually works, ship it, and see if there's real demand before building anything more complicated.
What it actually catches
// Platform coverage, version 1Each platform signals AI content differently, and none of them documents it publicly, so this came from directly testing each one and combing through what worked on one to check against the next.
Why I didn't build a custom AI detector
// The actual trade-offA proper AI-image classifier, OCR pass, and text-pattern model is a real piece of engineering — and a real ongoing cost to run. Before spending that time, I wanted to know whether people would actually use a free version long enough to tell me what they want from a better one.
That's what the feedback box in the extension's popup is for. It asks, in effect: is this useful as it is, what's missing, and would you pay for a version that catches more? Every submission goes straight into a database I can review — anonymously, no account or identity attached. If enough people say yes, a paid version with real detection is the obvious next step. If they don't, I've learned that for the cost of a weekend, not a quarter.
No ads, no pay-to-remove-ads
// How it's fundedThe extension carries a small "Built by Forge Vertical" credit in its popup, with a link back here for anyone who wants something similar built for them. There's also an optional support link for anyone who wants to buy me a coffee for the time it took. Neither is required, neither is removable for a fee, and there are no ads anywhere in it. If it ever grows into a paid tier, that will be a genuinely better product — OCR, image classification, broader coverage — not the free version held hostage.
Install it now, before the Chrome Web Store listing goes live
// Manual install, works todayThe extension is awaiting review on the Chrome Web Store. If you don't want to wait, the source is public on GitHub, and you can load it manually in any Chromium-based browser — that covers Chrome, Microsoft Edge, Brave, and Opera. It will not work in Firefox or Safari, which use a different extension system.
- Download it. Go to github.com/Jotto1988/ai-content-filter, click the green Code button, then Download ZIP. Unzip it anywhere on your computer.
- Open your browser's extensions page. Chrome:
chrome://extensions. Edge:edge://extensions. Brave:brave://extensions. Opera:opera://extensions. - Turn on Developer mode. There's a toggle for it, usually in the top-right corner of that page.
- Click "Load unpacked" and select the unzipped folder (the one containing
manifest.json). - Done. The extension's icon will appear in your toolbar, and it'll start hiding AI-labelled posts as you browse.
Browsers will show a small "Developer mode extensions" warning for anything installed this way — that's normal for any unpacked extension, not a sign something's wrong. Once the Chrome Web Store listing is live, you can switch to the store version and remove the manual one if you'd rather not see that notice.