Omitly 5.0.1 is a security and correctness patch. A PDF built to expand enormously when decompressed (a compression bomb) could make Omitly use many gigabytes of memory and disk while preparing a redaction. Omitly now limits how far a document may expand while it is prepared and while images are decoded, and refuses a document that exceeds the limit, with a message saying so, instead of writing the expanded content to disk or holding it in memory. The limit is 512 MiB of decompressed content per document. An image whose encoding Omitly cannot decode within the limit is removed whole from the redacted output rather than edited in place. With Password-protect (not sealed) switched on, Replace, Replace selection, name lists and Redact a folder previously saved an unencrypted file. They now refuse before anything is written and ask you to switch Password-protect off for that action or to encrypt the result afterwards. Known limits: while such a file is checked, memory use can still rise briefly before it is refused; a further fix is planned. Save, Extract pages, PNG export, signing and Windows printing do not apply Password-protect; this is also planned.
-
Release update
Omitly 5.0.1 is a security and correctness patch. A PDF built to expand enormously when decompressed (a compression bomb) could make Omitly use many gigabytes of memory and disk while preparing a redaction. Omitly now limits how far a document may expand while it is prepared and while images are decoded, and refuses a document that exceeds the limit, with a message saying so, instead of writing the expanded content to disk or holding it in memory. The limit is 512 MiB of decompressed content per document. An image whose encoding Omitly cannot decode within the limit is removed whole from the redacted output rather than edited in place. With Password-protect (not sealed) switched on, Replace, Replace selection, name lists and Redact a folder previously saved an unencrypted file. They now refuse before anything is written and ask you to switch Password-protect off for that action or to encrypt the result afterwards. Known limits: while such a file is checked, memory use can still rise briefly before it is refused; a further fix is planned. Save, Extract pages, PNG export, signing and Windows printing do not apply Password-protect; this is also planned.
Omitly 5.0.0 makes redacted scans searchable. When a page was read with OCR during your session, Omitly now reads the redacted page image again after redaction and writes the text it recognises invisibly behind that image, so you can search the saved file and select its text. The text comes only from the redacted pages, never from the original document, and before anything is saved Omitly reads the output back and refuses to save if the invisible text does not match what it can read on the redacted pages. The layer is added by Apply & verify, auto-detect personal info, full-page redaction, Replace and name lists, and AI-proposed redactions you accept; it is not added in batch runs or when Encrypt output is on. It is on by default: switch it off in Settings, Redaction, Make scanned pages searchable. After a redaction the result shows how many words were written and on which pages, which pages had no recognisable text, and which pages were not read and why; it never shows the words themselves. The certificate and the .audit.html report state which pages carry the layer, name the recogniser, version, language and confidence floor as the producer's own statement rather than something Omitly checked, say that recognised text is not the original and may be incomplete or wrong, and say that no recognised word lies inside a redaction only when the verifier, recomputing word positions from the delivered file, found that to be so. A new verifier check, omitly.check.ocr-layer, recomputes the layer from the delivered bytes. Recognition is English only in 5.0. Find over recognised text now reads pages rotated 90 or 270 degrees in the order they are displayed, so a phrase on a rotated scan is found. Known limits: the layer is recognised text and may be wrong or missing words; batch OCR is not part of 5.0.
-
Release update
Omitly 5.0.0 makes redacted scans searchable. When a page was read with OCR during your session, Omitly now reads the redacted page image again after redaction and writes the text it recognises invisibly behind that image, so you can search the saved file and select its text. The text comes only from the redacted pages, never from the original document, and before anything is saved Omitly reads the output back and refuses to save if the invisible text does not match what it can read on the redacted pages. The layer is added by Apply & verify, auto-detect personal info, full-page redaction, Replace and name lists, and AI-proposed redactions you accept; it is not added in batch runs or when Encrypt output is on. It is on by default: switch it off in Settings, Redaction, Make scanned pages searchable. After a redaction the result shows how many words were written and on which pages, which pages had no recognisable text, and which pages were not read and why; it never shows the words themselves. The certificate and the .audit.html report state which pages carry the layer, name the recogniser, version, language and confidence floor as the producer's own statement rather than something Omitly checked, say that recognised text is not the original and may be incomplete or wrong, and say that no recognised word lies inside a redaction only when the verifier, recomputing word positions from the delivered file, found that to be so. A new verifier check, omitly.check.ocr-layer, recomputes the layer from the delivered bytes. Recognition is English only in 5.0. Find over recognised text now reads pages rotated 90 or 270 degrees in the order they are displayed, so a phrase on a rotated scan is found. Known limits: the layer is recognised text and may be wrong or missing words; batch OCR is not part of 5.0.
Omitly 4.3.0 makes the certificate say exactly what was checked. A redaction now ends Safe to Send only when Omitly's own detector, run again on the finished file, no longer finds an identifier in it; if a value is still visible, on purpose or not, the result is Needs Review and says how many remain. Safe to Send can now only be printed from a report that verified, and an output is delivered only after its report and seal verify over the final bytes. The certificate is now titled Omitly Release Check Certificate and names the seal the file carries in one line (seal v2 - hybrid ML-DSA-87 + ECDSA P-384 signatures, or Ed25519 (classical-era seal v1)); the .audit.html sidecar shows the same row, and a file with a v1 seal is labelled classical-era seal (v1) wherever its verdict appears. The sealed report now records which detection profile was used, pinned by a hash of its content, which Verify shows, and records the session itself: the operations performed, in order and with their times. The command-line verifier and the npm package check that record; the Verify window does not show it yet. Printing (including Save as PDF), files the command-line tool writes, certificate export and omitly-compare -o now remove a report or seal that no longer matches the file, closing the known limit in 4.2.0. Signing refuses an encrypted PDF instead of decrypting it and signing. Check now reads fonts that map characters through a CID table and flags a character drawn with a font's blank missing-glyph shape; invisible text, such as the OCR layer of a scanned page, is left alone. Check also notes, as information, when a file carries an Omitly report sealed by the file's own key, and names that key: compare it with one the sender published. Text imported from a PDF's comments or restored from a saved session gets the same size and covering checks as text you type. The Verify window shows the licensee name as the name the buyer gave, not as a checked identity. For connected AIs, redaction and proposal results report Safe to Send, Needs Review or Cannot Verify, showing a proposal opens the file if it is not already open, and omitly-mcp now carries Omitly's version number (4.3.0, previously 0.3.10). Known limit: 4.3 has no way to record that you kept a value visible on purpose, so such a file reads Needs Review.
-
Release update
Omitly 4.3.0 makes the certificate say exactly what was checked. A redaction now ends Safe to Send only when Omitly's own detector, run again on the finished file, no longer finds an identifier in it; if a value is still visible, on purpose or not, the result is Needs Review and says how many remain. Safe to Send can now only be printed from a report that verified, and an output is delivered only after its report and seal verify over the final bytes. The certificate is now titled Omitly Release Check Certificate and names the seal the file carries in one line (seal v2 - hybrid ML-DSA-87 + ECDSA P-384 signatures, or Ed25519 (classical-era seal v1)); the .audit.html sidecar shows the same row, and a file with a v1 seal is labelled classical-era seal (v1) wherever its verdict appears. The sealed report now records which detection profile was used, pinned by a hash of its content, which Verify shows, and records the session itself: the operations performed, in order and with their times. The command-line verifier and the npm package check that record; the Verify window does not show it yet. Printing (including Save as PDF), files the command-line tool writes, certificate export and omitly-compare -o now remove a report or seal that no longer matches the file, closing the known limit in 4.2.0. Signing refuses an encrypted PDF instead of decrypting it and signing. Check now reads fonts that map characters through a CID table and flags a character drawn with a font's blank missing-glyph shape; invisible text, such as the OCR layer of a scanned page, is left alone. Check also notes, as information, when a file carries an Omitly report sealed by the file's own key, and names that key: compare it with one the sender published. Text imported from a PDF's comments or restored from a saved session gets the same size and covering checks as text you type. The Verify window shows the licensee name as the name the buyer gave, not as a checked identity. For connected AIs, redaction and proposal results report Safe to Send, Needs Review or Cannot Verify, showing a proposal opens the file if it is not already open, and omitly-mcp now carries Omitly's version number (4.3.0, previously 0.3.10). Known limit: 4.3 has no way to record that you kept a value visible on purpose, so such a file reads Needs Review.
Omitly 4.2.0 adds batch redaction for legal production. On Pro, choose a folder of PDFs and Omitly redacts the same terms in each one, verifies every output on its own and seals it separately. A file that cannot be verified clean is never counted as done: it is listed with the reason and what to do next, and the run cannot finish green while any file is unresolved. Files with nothing to redact are recorded, not copied. Omitly never overwrites a PDF already in the output folder; the production manifest only ever gains rows, and a resumed run keeps the earlier manifest beside the new one. In batch set-up you can give a term a substitute label (Jane Citizen = Client 1): Omitly writes the label in place of every removed occurrence, in every file, and the production log counts the labels applied. Each run writes a signed production manifest that the Verify window checks, and you can export a production log (CSV) of every file, its hashes and its seal. A run that stops part-way can be resumed with the same terms: outputs already made are kept only after each is verified again. Comments and notes made in other PDF apps are now listed in a read-only Comments panel (View › Comments); click one to jump to it. Omitly keeps them when you save. You can now connect your own AI through Omitly's MCP server (Settings › Connect your AI): your AI proposes redactions, you accept them in Omitly, and Omitly removes and seals. The PDF and the engine stay on this computer; text your AI asks for goes wherever your AI runs. Check now reads text in objects nothing in the file refers to, flags fonts that draw a different character from the one they declare, and offers Show me and Redact this occurrence too when removed text is found again on another page. Replace and pseudonymised outputs now get the newer report and post-quantum seal. Redaction refuses a page where a box covers text in a Type 3 font, which it cannot remove safely. Saving, extracting or signing a sealed file no longer carries a report or seal that no longer matches it.
-
Release update
Omitly 4.2.0 adds batch redaction for legal production. On Pro, choose a folder of PDFs and Omitly redacts the same terms in each one, verifies every output on its own and seals it separately. A file that cannot be verified clean is never counted as done: it is listed with the reason and what to do next, and the run cannot finish green while any file is unresolved. Files with nothing to redact are recorded, not copied. Omitly never overwrites a PDF already in the output folder; the production manifest only ever gains rows, and a resumed run keeps the earlier manifest beside the new one. In batch set-up you can give a term a substitute label (Jane Citizen = Client 1): Omitly writes the label in place of every removed occurrence, in every file, and the production log counts the labels applied. Each run writes a signed production manifest that the Verify window checks, and you can export a production log (CSV) of every file, its hashes and its seal. A run that stops part-way can be resumed with the same terms: outputs already made are kept only after each is verified again. Comments and notes made in other PDF apps are now listed in a read-only Comments panel (View › Comments); click one to jump to it. Omitly keeps them when you save. You can now connect your own AI through Omitly's MCP server (Settings › Connect your AI): your AI proposes redactions, you accept them in Omitly, and Omitly removes and seals. The PDF and the engine stay on this computer; text your AI asks for goes wherever your AI runs. Check now reads text in objects nothing in the file refers to, flags fonts that draw a different character from the one they declare, and offers Show me and Redact this occurrence too when removed text is found again on another page. Replace and pseudonymised outputs now get the newer report and post-quantum seal. Redaction refuses a page where a box covers text in a Type 3 font, which it cannot remove safely. Saving, extracting or signing a sealed file no longer carries a report or seal that no longer matches it.
-
Known limit
Two kinds of output are not yet covered by the check that removes an out-of-date report or seal: files you print, including macOS "Save as PDF" from the print dialog, and files written by the command-line tool when it is told to publish without that check. Re-check those files in Omitly before relying on their seal or certificate. We plan to close this in 4.3.
Omitly 4.1.0 makes Check's verdict harder to fool. Check now finds a value hidden under pen, marker or ink strokes, or under an annotation, not only under a filled box, and it no longer misses a cover over text drawn inside a reusable page element. Small gaps in a complex cover shape are now measured more precisely. Earlier versions saved inside a PDF are read more thoroughly: text in an earlier version that cannot be read now makes the scan incomplete, instead of being skipped. When you redact, form fields and annotations under a redaction box are now removed when Omitly can confirm they are gone (otherwise it warns, as before), and a new option removes all bookmarks and tooltips from the redacted copy. A file you have just exported can no longer be overwritten by another save or signing step unless you pick it again. Check's own report, and password-protected exports, are now sealed with the post-quantum seal. Signing a redacted file in the app no longer makes it read as modified, and the signature check now counts signatures from earlier versions of a file. Check names the right page when removed text repeats on another page, and saving with redactions still pending now explains what to do. On macOS, if you have both Omitly and Omitly Beta installed, macOS may ask once for your login password the first time the second app seals a document. Click Always Allow and it won't ask again. Details: omitly.app/help/macos-keychain-prompt
-
Release update
Omitly 4.1.0 makes Check's verdict harder to fool. Check now finds a value hidden under pen, marker or ink strokes, or under an annotation, not only under a filled box, and it no longer misses a cover over text drawn inside a reusable page element. Small gaps in a complex cover shape are now measured more precisely. Earlier versions saved inside a PDF are read more thoroughly: text in an earlier version that cannot be read now makes the scan incomplete, instead of being skipped. When you redact, form fields and annotations under a redaction box are now removed when Omitly can confirm they are gone (otherwise it warns, as before), and a new option removes all bookmarks and tooltips from the redacted copy. A file you have just exported can no longer be overwritten by another save or signing step unless you pick it again. Check's own report, and password-protected exports, are now sealed with the post-quantum seal. Signing a redacted file in the app no longer makes it read as modified, and the signature check now counts signatures from earlier versions of a file. Check names the right page when removed text repeats on another page, and saving with redactions still pending now explains what to do. On macOS, if you have both Omitly and Omitly Beta installed, macOS may ask once for your login password the first time the second app seals a document. Click Always Allow and it won't ask again. Details: omitly.app/help/macos-keychain-prompt
Omitly 4.0.1 is a security and reliability update. Check is now strict about attachments that use Omitly's own file names: one is treated as Omitly's report only when it is a valid Omitly report bound to the file's verified seal, and anything else is flagged like any other attachment. Check also finds attachments that a duplicated or shadowed PDF structure could previously hide from it. The metadata scrub now fully empties any metadata it has to keep, so nothing linked from it reaches the redacted file. Verify now says when a seal was removed (for example, when a sealed file was re-saved in another app), and when the app has to seal with a one-time key it tells you why and what to do. PDFs now open in Edit by default; a file that does not pass Check still opens on the Check screen. Rectangle and ellipse annotations get the same redaction-lookalike safeguards when imported or restored as when drawn. The TLS library used for update checks and trusted timestamps is updated to fix four security advisories published this week.
-
Release update
Omitly 4.0.1 is a security and reliability update. Check is now strict about attachments that use Omitly's own file names: one is treated as Omitly's report only when it is a valid Omitly report bound to the file's verified seal, and anything else is flagged like any other attachment. Check also finds attachments that a duplicated or shadowed PDF structure could previously hide from it. The metadata scrub now fully empties any metadata it has to keep, so nothing linked from it reaches the redacted file. Verify now says when a seal was removed (for example, when a sealed file was re-saved in another app), and when the app has to seal with a one-time key it tells you why and what to do. PDFs now open in Edit by default; a file that does not pass Check still opens on the Check screen. Rectangle and ellipse annotations get the same redaction-lookalike safeguards when imported or restored as when drawn. The TLS library used for update checks and trusted timestamps is updated to fix four security advisories published this week.
Omitly 4.0.0 seals redacted documents with a post-quantum signature. Seal format v2 combines ECDSA P-384 with ML-DSA-87, the post-quantum algorithm standardised in FIPS 204, so a seal stays verifiable even against a future quantum computer. The app keeps one seal key per installation in your system keychain. Signing a redacted document with your certificate now adds the seal alongside the digital signature, and the redaction report stays verifiable. This release also fixes an issue since 3.0 where signing a redaction left it unsealed with an incorrect "modified" warning. Documents sealed by earlier versions (v1) still verify exactly as before.
-
Release update
Omitly 4.0.0 seals redacted documents with a post-quantum signature. Seal format v2 combines ECDSA P-384 with ML-DSA-87, the post-quantum algorithm standardised in FIPS 204, so a seal stays verifiable even against a future quantum computer. The app keeps one seal key per installation in your system keychain. Signing a redacted document with your certificate now adds the seal alongside the digital signature, and the redaction report stays verifiable. This release also fixes an issue since 3.0 where signing a redaction left it unsealed with an incorrect "modified" warning. Documents sealed by earlier versions (v1) still verify exactly as before.
New setting: Always open PDFs in Edit (Settings, General, or the checkbox on the Check screen). The check still runs and its result now shows at the top of the editor, so you can go straight to editing. The check finds more: a black box drawn inside a reusable form object, or with curved or slanted edges, is now recognised as a cover over text that is still in the file; text that exists only in an earlier saved version of the file is now scanned; data stored in compressed object streams is now decoded a second time, and the file is reported as not fully read if the two readings disagree; and a font whose own tables draw a different digit or letter than the text says is now flagged as not verified. A page Omitly could not fully read is never reported as clean: unreadable pages, cut-off compressed data and characters a font does not define are reported as incomplete by Find, Locate text and Extract text, and an encrypted file with compressed object streams is reported as not fully checked. Signature discovery is cross-checked against a second PDF reader, and a file where the two disagree is refused. Editor fixes: placed text can be moved, text added on a form line now sits on that line, and a failed certificate save now says so. Compare now flags pages that hold drawings but no text instead of treating them as blank.
-
Release update
New setting: Always open PDFs in Edit (Settings, General, or the checkbox on the Check screen). The check still runs and its result now shows at the top of the editor, so you can go straight to editing. The check finds more: a black box drawn inside a reusable form object, or with curved or slanted edges, is now recognised as a cover over text that is still in the file; text that exists only in an earlier saved version of the file is now scanned; data stored in compressed object streams is now decoded a second time, and the file is reported as not fully read if the two readings disagree; and a font whose own tables draw a different digit or letter than the text says is now flagged as not verified. A page Omitly could not fully read is never reported as clean: unreadable pages, cut-off compressed data and characters a font does not define are reported as incomplete by Find, Locate text and Extract text, and an encrypted file with compressed object streams is reported as not fully checked. Signature discovery is cross-checked against a second PDF reader, and a file where the two disagree is refused. Editor fixes: placed text can be moved, text added on a form line now sits on that line, and a failed certificate save now says so. Compare now flags pages that hold drawings but no text instead of treating them as blank.
False-clean fixes. Every scan now says whether it read the whole document before it says what it found: an incomplete scan (image-only pages, text in fonts Omitly cannot decode, unreadable pages or streams) never reads as "no personal information found" on its own. Text in simple fonts is now read the way a PDF viewer shows it, through the font's encoding and its own built-in encoding, so a remapped number is no longer missed; codes that cannot be determined are reported. Pages whose page-tree entries are written unusually are now found and scanned instead of skipped. Redaction refuses documents whose compressed data is damaged rather than certifying a page it could not fully read. A second signature hidden in an unusual form, or in an earlier saved version of the file, can no longer slip past the "more than one signature" check. A hidden-layer finding is no longer downgraded by an unrelated parse error, and redacting one page can no longer change another page that shares its content.
-
Release update
False-clean fixes. Every scan now says whether it read the whole document before it says what it found: an incomplete scan (image-only pages, text in fonts Omitly cannot decode, unreadable pages or streams) never reads as "no personal information found" on its own. Text in simple fonts is now read the way a PDF viewer shows it, through the font's encoding and its own built-in encoding, so a remapped number is no longer missed; codes that cannot be determined are reported. Pages whose page-tree entries are written unusually are now found and scanned instead of skipped. Redaction refuses documents whose compressed data is damaged rather than certifying a page it could not fully read. A second signature hidden in an unusual form, or in an earlier saved version of the file, can no longer slip past the "more than one signature" check. A hidden-layer finding is no longer downgraded by an unrelated parse error, and redacting one page can no longer change another page that shares its content.
Safe to Send. Every redaction now ends with a sealed audit report and one of three results — Safe to Send, Needs Review or Cannot Verify — checked over the exact bytes Omitly published, and a certificate that says what was checked and what could not be. Check any PDF: open a file redacted by any tool and get the same three-state result, with the pages named. Verify reads the new report. The engine now finds text left under painted boxes whatever colour space or blend the box uses, redacted text surviving in bookmarks, tooltips, labels and metadata, signature identities, and content in truncated or corrupt streams, and fails closed where it cannot look. Free checker on omitly.app and the omitly-mcp tool speak the same result. The sealed report records who decided (app, CLI or agent).
-
Release update
Safe to Send. Every redaction now ends with a sealed audit report and one of three results — Safe to Send, Needs Review or Cannot Verify — checked over the exact bytes Omitly published, and a certificate that says what was checked and what could not be. Check any PDF: open a file redacted by any tool and get the same three-state result, with the pages named. Verify reads the new report. The engine now finds text left under painted boxes whatever colour space or blend the box uses, redacted text surviving in bookmarks, tooltips, labels and metadata, signature identities, and content in truncated or corrupt streams, and fails closed where it cannot look. Free checker on omitly.app and the omitly-mcp tool speak the same result. The sealed report records who decided (app, CLI or agent).
v2.10.0
16 September 2026 Page thumbnails in the Pages panel. Annotation editing: stroke-width picker, corner resize, double-click to edit note and text content, squiggly underline. The Verify panel now reports a PDF's digital signature. Measurements follow page operations and undo. Certification no longer fails on large letterhead forms, and a repeated image is handled honestly when one copy is redacted.
-
Release update
Page thumbnails in the Pages panel. Annotation editing: stroke-width picker, corner resize, double-click to edit note and text content, squiggly underline. The Verify panel now reports a PDF's digital signature. Measurements follow page operations and undo. Certification no longer fails on large letterhead forms, and a repeated image is handled honestly when one copy is redacted.
Fixes a macOS launch crash and redaction verification failures on ruled tables and adjacent cells. Dependency security update.
Annotations: the delete handle now sits on the annotation and Delete/Backspace removes it; yellow, purple and grey added to the annotation colour palette. Print: the macOS print panel now offers Paper Size and Orientation. Dependency security updates.
The red close button, File > Close and Cmd+W close the window again (they were silently ignored since 2.6.0). Cmd+Q was unaffected.
Open several PDFs at once as tabs; each document keeps its own pending redactions and undo history. Dependency security fix (browserslist).
Intel Macs are served again — the macOS Intel build returns after 2.8.0 shipped Apple Silicon and Windows only. OCR correction now always applies to the word you picked: two detections whose boxes rounded to the same position on a page could previously share an identity, so a correction could land on the wrong one while the other kept the machine reading. Plus release-pipeline and signing hardening.
-
Release update
Intel Macs are served again — the macOS Intel build returns after 2.8.0 shipped Apple Silicon and Windows only. OCR correction now always applies to the word you picked: two detections whose boxes rounded to the same position on a page could previously share an identity, so a correction could land on the wrong one while the other kept the machine reading. Plus release-pipeline and signing hardening.
Redact-and-replace: a name-list term can now carry a replacement ("Smith" becomes "Person A"), with the mapping kept in the audit record, and you can select a single word or line in the viewer to replace just that one instance — both through the same verified remove, stamp, reseal and verify path. OCR text can now be corrected by hand, and every corrected word keeps the machine reading it replaced. Form filling handles non-Latin values and closes six AcroForm gaps. Plus signing and release-pipeline hardening.
-
Release update
Redact-and-replace: a name-list term can now carry a replacement ("Smith" becomes "Person A"), with the mapping kept in the audit record, and you can select a single word or line in the viewer to replace just that one instance — both through the same verified remove, stamp, reseal and verify path. OCR text can now be corrected by hand, and every corrected word keeps the machine reading it replaced. Form filling handles non-Latin values and closes six AcroForm gaps. Plus signing and release-pipeline hardening.
Bates numbering for legal production (Pro): the stamp is burned in before sealing, so it sits inside the sealed bytes and altering it breaks verification. Rotated scanned pages are now OCR-checked for sensitive content instead of being skipped. Plus trial and licence correctness fixes, and release-pipeline hardening.
-
Release update
Bates numbering for legal production (Pro): the stamp is burned in before sealing, so it sits inside the sealed bytes and altering it breaks verification. Rotated scanned pages are now OCR-checked for sensitive content instead of being skipped. Plus trial and licence correctness fixes, and release-pipeline hardening.
Redaction correctness fixes (wrong-rectangle regions on pages with /UserUnit scaling or non-zero MediaBox origin; several indirect-object detection gaps in the /Subtype and resource-inheritance paths), a new free PDF text-extraction MCP tool, and release-pipeline hardening.
-
Release update
Redaction correctness fixes (wrong-rectangle regions on pages with /UserUnit scaling or non-zero MediaBox origin; several indirect-object detection gaps in the /Subtype and resource-inheritance paths), a new free PDF text-extraction MCP tool, and release-pipeline hardening.
2.5.1 — Print now actually prints on macOS via the native PDFKit panel. Redaction correctness: inline semantic text is removed from Form XObjects, patterns and Type3 glyphs; mixed drags no longer drop non-text content. The verify panel now separates the verifier's own warnings from text quoted out of an unverified report. Ships the extract-zip CVE removal (CVE-2026-56876) and the orphan-page fix.
-
Release update
2.5.1 — Print now actually prints on macOS via the native PDFKit panel. Redaction correctness: inline semantic text is removed from Form XObjects, patterns and Type3 glyphs; mixed drags no longer drop non-text content. The verify panel now separates the verifier's own warnings from text quoted out of an unverified report. Ships the extract-zip CVE removal (CVE-2026-56876) and the orphan-page fix.
Redaction correctness fixes across fonts, spacing and nested page content.
-
Type 3 font handling
Improved malformed Type 3 font detection and FontMatrix handling so redaction placement remains accurate in affected PDFs.
-
CID word spacing
Corrected word-spacing calculations for CID fonts so detected text and redaction regions stay aligned.
-
Nested form resources
Corrected resource handling for nested PDF Form content, including documents whose resource names collide.
-
Cross-engine rendering checks
Expanded release checks across Windows WebView2 and two macOS WebKit environments to catch rendering differences before publication.
Base-14 font positioning fixes and desktop usability improvements.
-
Base-14 font positioning
Corrected redaction-region placement in PDFs that use Base-14 fonts without an explicit Widths table.
-
Desktop navigation and viewing
Added a native menu bar, a Settings window, fit-to-width and fit-to-page zoom, Open Recent, and drag-and-drop opening.
-
Unsaved-work prompt
Omitly now asks before discarding unsaved changes.
Native Intel support for macOS, and a more complete audit report.
-
Omitly for Intel Macs
A native Intel (x86_64) build of Omitly for macOS is now on the stable channel, signed and notarized, alongside the Apple silicon build. Pick the download matching your Mac — two separate installers, one licence.
-
Disclosures now appear in the audit report
Informational disclosures raised during a redaction (for example, a form field whose stored value has no visible widget) are now recorded in the signed audit report and its sidecar files, not just shown in the app.
-
Windows stable updated
The same release is also published for Windows.
Printing through your PDF viewer, and small fixes.
-
Printing uses your default PDF viewer
Print now opens the document in your system's default PDF viewer instead of an in-app dialog, restoring paper-size options and fixing a case where the print action could be lost.
-
Small fixes
Corrected the support email shown in the About dialog, and fixed a timing-dependent test in the sealing pipeline.
Metadata preservation option, safer page editing, and a Windows offline installer.
-
Choose to keep document metadata
Redaction can now optionally preserve the document's existing metadata (creator, producer, dates) instead of removing it, for users who need that provenance to survive. Off by default — nothing changes unless you turn it on.
-
Undo covers more of your work
Undo now reliably reverses annotation additions, moves and deletions, and no longer discards a placed signature partway through other edits.
-
Page reordering preserves bookmarks and form fields
Reordering pages no longer risks losing document bookmarks or form fields, and extracting a page range no longer includes content from pages you excluded.
-
Open PDFs and EML files directly from Finder
Double-clicking a supported file now opens it in Omitly, including when the app isn't already running.
-
Windows offline installer
A second Windows installer is now available for air-gapped machines, bundling everything needed to install without an internet connection.
-
Verification and signing hardening
Continued tightening of licence, signature and tamper-evidence-seal verification based on internal review, plus clearer certificate wording for documents whose seal doesn't validate.
Stable macOS (Apple silicon) launch, with no functional changes to the app.
-
Omitly for macOS (Apple silicon)
Omitly is now on the stable channel for macOS (Apple silicon), as a signed and notarized build. Intel Macs were not supported at this release — native Intel support arrived in 2.4.2. Nothing else about the app changed in this release.
-
Windows stable updated
The same maintenance release is also published for Windows.
Windows stable republished with detection fixes.
First stable Windows release.
-
Windows, on the stable channel
Omitly for Windows is now published on the stable channel as a signed installer. The build is Authenticode-signed, so Windows verifies the publisher and rejects a file that has been altered since it was signed.
-
Verified redaction with a tamper-evident certificate
Every redaction on this build produces the signed audit report and whole-file integrity seal, checkable offline with Verify in the toolbar.
Licensing and trial, auto-redaction beyond emails, and selectable text in the viewer.
-
Redact personal info, not just emails
Auto-detection now finds emails, SSNs, credit card numbers and phone numbers in one pass. Every match still goes through the mandatory review step before anything is removed, and each removal is tagged by category in the audit report.
-
Select and copy text in the viewer
Text in the preview is now selectable with your normal copy shortcut. Selection is redaction-aware: text covered by a redaction box is excluded from selection and copy, so what you copy matches what you see.
-
Licences and free trial
Omitly now activates offline with a licence file, and includes a built-in trial. Output produced during evaluation is marked as such in the audit report.
-
Licence-backed provenance (Pro)
Licensed output can carry a provenance claim that verifies against Omitly's vendor key, alongside the existing tamper-evident seal.
-
Accessibility improvements
Better dialog semantics, control names, live status announcements and contrast throughout the app.
-
Signing and verification hardening
PAdES digital signing and seal verification continue to tighten based on internal red-team review — including stricter whole-file coverage checks on verify.
UI refresh, auto-updater and in-app support.
-
Refreshed two-tier toolbar and About dialog
A cleaner layout that separates everyday editing from redaction tools.
-
Auto-updater
Omitly checks for updates and installs a new release only if its signature matches. Documents are never part of an update check.
-
In-app support
Send us a message from About → Support. Only the text you type, the app version and your OS are sent — never document content.