02 / Questions
Plain answers.
What the app does, where the boundaries are, and what happens on your computer.
Does recognised text leave my device?
No. OCR runs on your device. The only app network request is an optional update check, default off; its GET carries no version, platform or install identifier, but GitHub sees your IP address. The request follows HTTPS redirects only within GitHub and GitHub release-asset hosts.
Does ClipOCR work offline?
Yes. Capture and OCR work offline. An optional update check cannot run while offline; a failed check is reported separately and does not affect OCR.
Why does Gatekeeper warn on macOS?
The public macOS builds are signed but not notarized, so Gatekeeper may warn on first launch. See the macOS setup notes →
Does it keep capture history?
No. ClipOCR does not keep OCR or capture history or export screenshots.
Does it sync copied text?
No. ClipOCR has no sync feature. OS clipboard sync or clipboard managers you enable may retain or sync copied text; ClipOCR does not control them.
What does the update check do?
It checks for a newer release; it is not an updater. Nothing is downloaded, installed or restarted. If a newer release exists, you can click to open its GitHub release page. Automatic checks are opt-in, off by default, at most once daily after success, deferred during capture, with 6/12/24-hour backoff after failures.
Which systems are supported?
macOS 12+ (system region picker and Apple Vision), Windows 11 (native crosshair overlay and Windows.Media.Ocr), and Linux on wlroots/Wayland compositors such as Hyprland, Sway and River (slurp, grim and Tesseract). GNOME/KDE Wayland are not claimed. Read platform setup →