How Omitly updates work
Updated 6 Nov 2026 · Applies to Omitly 2.5.0+ · macOS & Windows
Omitly makes no network request on its own, and that includes checking for updates. You decide when to check.
Getting updates
Check any time from More ▾ → About Omitly → Check for updates. Every 14 days the app shows a local reminder that it does not check for you; the reminder itself uses no network. Installing is always a separate, explicit action: Omitly never installs an update without you clicking to confirm it. If installing in-app doesn’t work, the check also offers a manual-download link.
Your licence carries over — updating doesn’t require re-activating. A Pro licence is the exception after its 12 months of updates: on a version released later, without a renewal, redaction and OCR still work, output carries an evaluation mark, and signing, Bates and batch are off. Versions released within the 12 months stay fully Pro, so you can stay on one or reinstall it. Personal is not affected. Each update is cryptographically signed, and Omitly verifies that signature before installing it — a separate signature from the one on the installer itself, but the same idea: nothing installs unless it’s provably from us.
What the update check sends
The update check asks our servers whether a newer version exists and, if so, fetches the signed release. It never sends your documents, their contents, or their filenames — the only thing travelling is the software itself. This is separate from anything to do with your files; see Where does your PDF go?
Managed deployments
In a firm that deploys software centrally, updates can be distributed through your own deployment tools instead of each machine fetching them directly. See Deploying Omitly with Group Policy for what the shipped Windows build supports, or contact support and we’ll help you work through it.
Related
Still stuck?
Tell us what's not working — include your Omitly version (More ▾ → About Omitly) and your operating system, and we'll usually reply within one business day.
Report a problem with this article