Add your keywords — a team, a show, an event — and every matching post, comment, and video on X, Reddit & YouTube is blurred until YOU click Reveal. Built for speed (scans only new content, in idle time) and privacy (keywords never leave your browser). Free up to 10 keywords; Premium is $4.99 once.
No reviews yetBe the first to leave a review for Spoiler Blur
Maker
📌
Hey Product Hunt! 👋
I built Spoiler Blur for one very specific reason: the World Cup final is this Sunday, and I can't always watch matches live. Every time I save a game for later, one stray post or a YouTube thumbnail ruins it in half a second.
So: you add keywords — a team, a show, an event — and every post, comment, and video that mentions them on X, Reddit, or YouTube gets blurred behind a "Spoiler hidden" cover. Nothing is deleted; when you've caught up, one click reveals it.
Two things I obsessed over:
⚡ Performance. The best-known spoiler blocker hasn't been updated since 2020, and its reviews are full of "it slowed my browser down". That was my list of what NOT to build. Spoiler Blur scans only newly added content, during browser idle time — no page-wide re-scans, ever. Your feed stays exactly as fast.
🔒 Privacy. Your keywords never leave your browser. No account, no analytics, no tracking. The only network request the extension can make is validating a Premium license key.
And an honest confession: I built this for sports and shows, but while using it myself I caught myself adding keywords that had nothing to do with spoilers — news topics I just didn't want in my face that day. The engine doesn't care what a keyword means: it mutes anything. So next on the roadmap are curated keyword packs — spoiler packs for shows (character and actor names included, so you don't have to think of them all), and topic packs for things like heavy news.
Pricing: free forever for 1 list / 10 keywords. Premium is $4.99 one-time(no subscription), up to 3 devices, 30-day money-back guarantee. Launch week: WORLDCUP30 gets you 30% off.
I use it every day and a few friends have been testing it, but you're the first real audience this is in front of. I'd love your feedback — and tell me which sites or features you'd want next (Firefox and Edge ports are already planned).
Enjoy the final — on your own time. ⚽
Report
Could you add a per-site toggle so I can keep spoilers blurred on Reddit but still see YouTube thumbnails? Also a quick "tap to reveal for 30 seconds" option would be great when I just want a peek without fully committing.
Report
Maker
@leventerdapyuc Both are solid, and honestly neither exists right now — it's one keyword list applied the same way across all three sites, no way to say "blur here, not there" yet. The per-site toggle makes a lot of sense too, spoiler tolerance genuinely differs by site (a Reddit thread you're deep in vs. a YouTube thumbnail you're just scrolling past are pretty different situations).
The 30-second peek is a clever middle ground I hadn't thought of — right now Reveal is all-or-nothing per item, no timed re-blur. That one's probably the smaller build of the two.
Really appreciate you thinking this through, noted both down.
Report
Maker
A few questions I expect, answered up front:
Q:Will it slow down my feed?
A: No — that fear is why this exists. It never re-scans the page; it watches only newly added content and does the matching when the browser is idle. If you ever measure a slowdown, I want to hear about it.
Q:What exactly can it see / send?
A: It reads post text locally to decide what to blur. Nothing about your browsing ever leaves the machine — keywords are stored in Chrome's own sync storage, and the extension works fully offline. The single allowed network call is Premium license validation with Polar (our payment provider).
Q: Why not 100% free?
A: Solo developer, no VC, no ads, no data selling — the $4.99 one-time Premium is the whole business model. Free tier (10 keywords) stays free forever, and there's a 30-day money-back guarantee.
Q: Does it catch images with no text?
A: Matching runs on the text platforms attach to content — titles, captions, comments, channel names. A bare screenshot with no matching text can slip through; the upcoming keyword packs help by covering the names people actually use around an event.
Q: Mobile?
A: Desktop Chrome today. The native X/Reddit/YouTube apps are closed to extensions, so the realistic paths are Firefox for Android and iOS Safari extensions — both under consideration right after the Firefox port.
Q:Other browsers?
A: Firefox and Edge are next on the roadmap (same codebase, small porting work).
Report
Set this up with a few show names and it actually works exactly as described, blurring posts in my feed until I tap reveal. The fact that nothing leaves the browser makes it feel way less sketchy than most "AI" tools.
Report
Maker
@ezgiimq3 Really glad it just... worked, honestly that's the best kind of feedback. And yeah, the "nothing leaves the browser" thing was a deliberate choice, not just a privacy line for the listing — it's literally just keyword matching against text that's already on your screen, no API calls, no server. Felt important to me too, especially compared to a lot of "AI-powered" tools that quietly ship your data somewhere to do the same job a simple string match could do.
Curious, are you using it mainly on X, or did you try it on Reddit/YouTube too? Trying to get a feel for which site people lean on most.
Could you add a per-site toggle so I can keep spoilers blurred on Reddit but still see YouTube thumbnails? Also a quick "tap to reveal for 30 seconds" option would be great when I just want a peek without fully committing.
@leventerdapyuc Both are solid, and honestly neither exists right now — it's one keyword list applied the same way across all three sites, no way to say "blur here, not there" yet. The per-site toggle makes a lot of sense too, spoiler tolerance genuinely differs by site (a Reddit thread you're deep in vs. a YouTube thumbnail you're just scrolling past are pretty different situations).
The 30-second peek is a clever middle ground I hadn't thought of — right now Reveal is all-or-nothing per item, no timed re-blur. That one's probably the smaller build of the two.
Really appreciate you thinking this through, noted both down.
A few questions I expect, answered up front:
Q: Will it slow down my feed?
A: No — that fear is why this exists. It never re-scans the page; it watches only newly added content and does the matching when the browser is idle. If you ever measure a slowdown, I want to hear about it.
Q: What exactly can it see / send?
A: It reads post text locally to decide what to blur. Nothing about your browsing ever leaves the machine — keywords are stored in Chrome's own sync storage, and the extension works fully offline. The single allowed network call is Premium license validation with Polar (our payment provider).
Q: Why not 100% free?
A: Solo developer, no VC, no ads, no data selling — the $4.99 one-time Premium is the whole business model. Free tier (10 keywords) stays free forever, and there's a 30-day money-back guarantee.
Q: Does it catch images with no text?
A: Matching runs on the text platforms attach to content — titles, captions, comments, channel names. A bare screenshot with no matching text can slip through; the upcoming keyword packs help by covering the names people actually use around an event.
Q: Mobile?
A: Desktop Chrome today. The native X/Reddit/YouTube apps are closed to extensions, so the realistic paths are Firefox for Android and iOS Safari extensions — both under consideration right after the Firefox port.
Q: Other browsers?
A: Firefox and Edge are next on the roadmap (same codebase, small porting work).
Set this up with a few show names and it actually works exactly as described, blurring posts in my feed until I tap reveal. The fact that nothing leaves the browser makes it feel way less sketchy than most "AI" tools.
@ezgiimq3 Really glad it just... worked, honestly that's the best kind of feedback. And yeah, the "nothing leaves the browser" thing was a deliberate choice, not just a privacy line for the listing — it's literally just keyword matching against text that's already on your screen, no API calls, no server. Felt important to me too, especially compared to a lot of "AI-powered" tools that quietly ship your data somewhere to do the same job a simple string match could do.
Curious, are you using it mainly on X, or did you try it on Reddit/YouTube too? Trying to get a feel for which site people lean on most.