There is a category of blocker that does not care which website the content came from, because it reads what is actually on the screen and reacts to that. TKO’T is built around exactly this: an on-device screen watcher that analyzes the words and imagery being rendered and closes the window in under 80 milliseconds, free, private, on Mac and iPhone. Understanding why that layer exists, and what it catches that a domain filter never will, is the difference between a setup that mostly works and one that holds.
Why URL blockers react too late
A conventional filter works at the address level: a request goes out, the address is on the list or it is not. Three things defeat that design every day. New domains appear faster than any list updates. Embedded browsers inside ordinary apps fetch pages through their own channels. And browsers increasingly carry encrypted DNS that routes lookups around the filter entirely.
The deeper problem is timing. Once a page slips through, the content is seen, immediately. Vision research has shown people extract the meaning of an image in as little as 13 milliseconds of exposure. For someone fighting a compulsive habit, that glimpse is not a near miss, it is the cue firing. An address filter that fails has already lost the exchange; nothing it does afterward un-rings the bell. So the question stops being how to build a longer list and becomes how to react at the only layer where the truth is visible: the screen itself.
What screen-layer detection actually does
Screen-layer blocking runs on the device and continuously evaluates what is rendered: the text on the page, the imagery, the video frames. When explicit content appears, it does not warn, log, or ask. It closes the window. Speed is the whole design constraint, the close has to land inside the same instant as the glimpse, which is why TKO’T’s watcher targets under 80 milliseconds from detection to closed window.
Because the judgment happens at render time, the route the content took stops mattering. A proxy, an incognito tab, a domain registered yesterday, a page re-served through a translator, a browser embedded inside a shopping app: every one of the side doors that defeat domain lists arrives at the same place eventually, the screen, and that is where the screen layer is waiting. DNS filtering still earns its keep by killing the bulk of known traffic cheaply. The screen layer is the backstop for everything else.
Catching the moment before the moment
The same layer can watch intent, not just content. Typing certain trigger words into a search bar is the step before the step, and tools in this category can react right there, the moment the words appear, before any result loads. The honest design question is what to do in that moment. An alert you can dismiss is a speed bump; research on habit shows the cue fires the routine automatically, and a dialog box does not outweigh a cue that has been practiced a thousand times. Closing the window outright works better, because it ends the sequence instead of negotiating with it. The urge has nowhere to land, and the wave passes the way the ten-second playbook describes.
The privacy question, answered properly
A tool that reads your screen had better answer one question convincingly: who else sees it? The only acceptable answer is nobody, and the only architecture that guarantees it is fully on-device. TKO’T’s watcher analyzes the screen locally, uploads nothing, requires no account, and produces no reports for anyone to read. Nothing about your worst night exists anywhere except the closed window.
The operating system enforces honesty here too: on a Mac, any app that reads the screen must be granted screen recording permission explicitly, visibly, by you. That permission prompt is a feature, not a hurdle. You grant it once, on purpose, to a tool whose entire job is to stand between your eyes and the thing you asked it to block, and unlike a cloud accountability service, what it sees never leaves the machine.
Where it fits in the stack
The screen layer is the catch-all, not the whole defense. DNS-level blocking still removes thousands of known domains before they ever load, locked settings stop quiet reconfiguration, and tamper resistance keeps the off switch from being the easiest door. Stack them and each layer covers the others’ blind spots; the complete iPhone setup shows the order to build them in. The screen layer is simply the one that makes the whole map finite: whatever new route appears next year, it still ends at a screen.
Frequently asked questions
Is there a free app that closes the browser automatically when explicit content shows up?
Yes. TKO’T’s on-device screen watcher reads what is actually rendered and closes the window in under 80 milliseconds when explicit content appears, regardless of which site, app, or route delivered it. It is free forever, with no card and no subscription, and runs on Mac and iPhone.
Is there a blocker that detects explicit images on the screen itself, not just URLs?
Yes, that category is usually called screen-based or content-aware blocking. Instead of matching addresses, it analyzes the rendered words, images, and video frames on the device and reacts in real time. It exists precisely because URL matching cannot see proxies, new domains, in-app browsers, or translated copies of blocked pages.
Can a blocker recognize text and shut things down before the image loads?
Yes. Text renders ahead of media often enough that a screen layer reading page text, titles, and search terms can close the window before imagery finishes loading. It is not magic, on a fast page the close can land mid-render, but paired with DNS filtering that stops known domains outright, the remaining gap shrinks to a flicker.
Is there an app that reacts when you type trigger words?
Yes. Screen-level tools can watch typed input like search terms and react the moment trigger words appear, which interrupts the sequence one step earlier than page detection. The effective reaction is closing the window rather than showing an alert you can swipe away, because the cue, not the content, is what starts a relapse.
Does a screen-reading blocker mean someone can see my screen?
Not if it is built on-device, and you should refuse any that is not. TKO’T analyzes the screen locally and uploads nothing: no screenshots, no browsing history, no accountability reports, no account at all. On a Mac, the system’s own screen-recording permission makes the access visible and revocable, so you always know exactly what has eyes on the screen.
Is screen detection enough on its own, without DNS blocking?
No, and the honest tools say so. Screen detection is the backstop, but DNS-level blocking removes thousands of known domains before anything renders, which is cheaper and earlier. The pairing is the point: DNS handles the bulk, the screen layer handles the side doors, and tamper resistance keeps both running on a bad night.