True redaction removes the text and images from the file — not a black box on top. Plus real in-place text editing, fill + sign, reorder pages, and OCR.
LaunchEdit text in place, sign, redact, fill forms, and reorganize PDF files in your browser — all on your device. No upload, no subscription.
Drop two versions of a contract or drawing set. Moved notes read as moves, changed values light up digit by digit, and hidden text is named.
LaunchSide-by-side or overlay PDF diff driven by one engine that reads each file into a structured model — text, vector geometry, images, form fields, annotations — and compares the models. Moves show as moves, edits show only where they happened, and any PDF type works without picking a mode.
Drop a Gerber ZIP, an ODB++ .tgz or an IPC-2581 .xml and inspect every layer — compare revisions, snap-to-pad measure, run DRC and preview the board in 3D.
LaunchOpen Gerber, Excellon, ODB++ and IPC-2581 PCB files. Inspect layers, measure traces, run DRC, export to PNG / SVG / DXF.
Open a .step / .stp part and it measures itself: volume, thinnest wall, draft and undercuts on load, and a hole list with a BOM in one click. Measure, section, export STL.
LaunchOpen a STEP / STP part and it measures itself — volume, thinnest wall, draft and undercut checks on load, plus hole detection with a BOM. Measure, section, export STL. Rust + WASM B-rep kernel, runs in your browser.
Compress, merge, split, convert, and manipulate PDF files.
Resize, compress, convert, and transform images.
Convert, compress, and cut audio and video — MP3, WAV, MP4, WebM, Opus — all in your browser, nothing uploads.
Simulate a canning process down to its F0 sterilizing value.
Encrypt files, share encrypted notes as links, and read passport IDs and Windows event logs.
Analyze packet captures, move files between devices, and console into network gear — nothing uploads.
Scan receipts into an expense ledger — your receipts and spending stay on your device.
View, measure, and repair CAD and 3D files — STEP, STL, OBJ, PLY, GLB, 3MF, DXF, and Gerber — right in your browser. Nothing uploads.
A review is often checked by someone who was not there. Four things they cannot tell from a list of changes, and how a compare report answers each.
A document review rarely ends with the reviewer. A partner signs off on it, a contractor prices from it, and an auditor or a court may read it months later. That next reader was not there when the comparison ran. All they have is what you hand them.
A list of changes leaves four questions open. Each one is a way a careful review can be doubted, or can quietly go wrong, after it leaves your hands.
Files get renamed, saved again, and sent again. The “Final_v3.pdf” in your email may not be the “Final_v3.pdf” that was signed. A file name cannot tell the next reader which bytes you compared.
A hash can. A SHA-256 hash is a 64-character fingerprint of a file’s bytes: change one byte and the whole hash changes. Compare PDF’s report puts both files’ hashes on its cover, with their sizes and page counts, the build that ran, and the settings used.
Anyone who holds a copy can check it against the cover. On macOS or Linux:
shasum -a 256 gm-bylaws-2024.pdf
ec2503f6213c76f13db075cd70a1919f3a3ae2777d121bc9b5b6e3bda6173548 gm-bylaws-2024.pdfOn Windows, certutil -hashfile gm-bylaws-2024.pdf SHA256 prints the same value. If it matches the cover, the reader is holding the file you reviewed.
Every compare tool leaves something out of its main list, and it should: text that moved because a paragraph above it grew is not an edit. On the bylaws, 212 of 253 differences are like that: 175 layout shifts, 32 header or footer edits repeated on every page after the first, and 5 pieces of a longer edit already listed as one change.
The danger is a list that folds quietly. Forty-one rows look like a complete answer, and the next reader cannot tell that 212 were set aside, or why.
The report states the sum on its cover: 253 changes = 41 in the change table + 212 folded in the appendix. The appendix lists each folded item with its reason. The table and the appendix are built from one list, so the numbers always add up. If you excluded a region of the page on purpose, the cover counts the exclusion regions, and the appendix lists what they held.
A change table in page order puts a changed payment date at row 30 of 253, with the same weight as a moved heading. The next reader skims it, as anyone would.
The report opens with a must-see section instead: every changed number, date, amount, and dimension, any hidden content, and anything the reviewer starred or flagged. On the bylaws, that is 21 items, before the long table.
The styling follows the blackline convention: deletions struck through, insertions underlined. At least one federal court’s local rules require it for an amended filing, and it reads in black and white, which matters for a report that will be printed or photocopied. Every kind of change also carries a text tag and its own mark, so colour is never the only signal.
A review is a set of decisions: this change is fine, this one needs a follow-up, this one matters. Those decisions usually live in the reviewer’s head or in an email, and they do not travel with the file.
In Compare PDF, each change carries a review mark, a star, and a note, and the report prints them beside the change. Each change also keeps one ID in the report, the CSV, the JSON, and the marked-up copy, so “see C-B44FFADE” points everyone to the same change. Here is that change as the CSV export writes it, cut short:
schema,id,status,kind,subKind,layer,channel,tags,…,review,star,note,foldReason,engineId
loft-compare-changes/3,C-B44FFADE,shown,modify,,text,textlayer,date,…,unreviewed,,,,v4g-9-aEvery row names its format first, so a sheet cut from the file still says what it is.
The next reader also has an order of their own. A contractor reads an addendum sheet by sheet, in the order the addendum lists them, and state procurement guidance documents that convention. A lawyer wants the blackline, with the clean copy named. An HR reader wants changes by policy section, with each version’s effective date.
A hash proves which bytes were compared, not that every change in them was caught. A report supports a careful review of the documents; it does not replace one. Its cover also states one limit of its own: the PDF report is not tagged for screen readers, and the HTML report made from the same compare is the accessible version.
You can make a report with a hashed cover, a must-see section, and a folded-items appendix from your own files in Compare PDF.