Building a privacy overlay that never reads your screen
How Smudge frosts what's on a Mac screen without Screen Recording permission, why the frost shows in screen shares, how we measured that text can't be read through it, and how a finger and a mouse share one screen.
The obvious way to blur part of a screen is to capture the screen, blur the pixels you want hidden, and draw the result back on top. It works, and it means your privacy tool can see everything you were trying to hide. It also needs Screen Recording permission, which is exactly the permission you’d rather not hand to a utility that sits on your Mac all day.
Smudge does it the other way. It never reads a single pixel of your screen. This is how that works, how we checked that the frost really hides text, and the part that took longest: letting a finger and a mouse share one screen.
Letting macOS do the blurring
macOS already knows how to blur whatever is behind a window. It’s the frosted look of sidebars, menus and Control Center. In AppKit that’s NSVisualEffectView in behind-window mode. When a window uses it, WindowServer blurs the content underneath on the GPU while it composites the screen.
The app that owns the window never sees that content. Smudge asks for a frosted rectangle and macOS fills it in. So Smudge needs no Screen Recording permission, and no Accessibility or Input Monitoring permission either. There’s nothing to leak because Smudge never has it.
Stacking for strength
One behind-window blur is designed for sidebars, not for hiding secrets, so Smudge stacks them. A frosted window blurs everything below it, including another frosted window, so each extra layer blurs the previous layer’s result again.
That’s how the strength settings work. Standard is one layer, Strong is two and Maximum is three.
Shapes that follow a finger
A patch doesn’t have to be a rectangle. When you swipe, Smudge builds the path of your stroke and uses it as a CAShapeLayer mask on the blur view, so the frost appears exactly where your finger went.
Why viewers see it
Because the frost is part of the composited display, anything that captures the display captures it too. Screen-sharing apps on macOS use ScreenCaptureKit, so we checked with ScreenCaptureKit directly: a full-display capture includes the frost.
The flip side is window shares. A single-window capture asks for that one window’s pixels, and Smudge’s window isn’t part of it. We’d rather say so plainly than have someone find out mid-call.
Measured, not eyeballed
“Looks blurry to me” isn’t a test. Smudge’s self-test draws a fake dashboard, takes a screenshot, frosts it and takes another. Then it compares the sum of luminance gradients inside each text area before and after. Sharp text has lots of hard edges and scores high. Blur flattens them, so the score drops towards zero.
The API key line scored 32.71 unfrosted. Under the six frost styles it scored between 0.00 and 0.12, so at most 0.4% of its detail survived. Under the panic frost (⌃⌥F, every display at once), the dashboard’s title kept 0.1% of its detail and its biggest number 0.9%.
The test earned its keep early on. An early Solid style was a plain colour block, and at 50% opacity it leaked readable text: the key could be read through the half-transparent box. Now every style keeps a frost layer underneath, so no colour or opacity setting makes the text readable again.
Sharing the screen between a finger and a mouse
This took the longest. On macOS 27, AppKit turns a single-finger tap or drag into ordinary mouse events, and an app gets individual touches only through gesture recognizers attached to its views. For a recognizer to see a touch anywhere on screen, Smudge needs a window covering the screen. A window covering the screen also catches every click, which would break the demo you’re trying to protect.
The fix is a hole. In touch mode, Smudge tiles the screen with four transparent windows arranged around a 44-point square that follows the pointer. Your finger lands on one of the four windows wherever you touch, and Smudge sees it. The pointer always sits in the hole, so clicks, scrolls and hover go straight to the app underneath.
A one-time Touch Check measures whether the Mac routes touches independently of the pointer. If it does, the hole isn’t needed and Smudge drops it.
Patches and ink never take clicks in either mode.
What it costs
About 22 MB of memory and 0% CPU while idle, measured on an M1 Pro. There are no timers running in the background, and the overlay windows exist only while something is drawn. When the screen is clean, Smudge is a menu-bar icon and nothing else.
How we test it
Smudge has 66 unit tests and 82 end-to-end checks that run against real screenshots, including the text-detail measurements above.
If you’re curious how the touch side looks from a user’s point of view, we wrote about what touch does on the new MacBook Pro, and apps built for it.