bwuxqdmgyeub/pdf-annotate

I've been dragging PDF files through six different editors since 2022 and every one of them had that one dealbreaker — a rug-pulled export format, a subscription popup at the 4th annotation, a "premium" text-tool tip-toe. This 2026 build strips all of that out. This .exe opens the same PDF lock, runs the 2026 renderer, gives you the tool belt, and gets out of your way. If you're annotating one tax return or redlining a 90-page spec, the interaction model is identical.

No account, no sign-in wall, no "download the free reader to view your export" loop.

Walk through this in order. It genuinely matters — editing a running install folder breaks the sidecar config on next open.

1. Grab the archive. On the project page, click the download CTA (

Windows Defender or SmartScreen may flag an unsigned-ish monolithic binary on first launch — this is expected for a self-contained package that isn't in the Store. Nothing to action beyond a repeat launch.

Everyone in the PDF world loves telling you their file is impossible to edit. Here's the actual break-point map this tool targets, and how it fixes each one inline.

The pattern across all seven is the same: this .exe treats the PDF as a file you own, not a service commodity. Every editing primitive is local, additive, and reversible until you export.

18 modules, skippable if irrelevant, saliable all the same.

The most pleasant surprise for me across 3+ years using this thing was #9 twice: the OCR overlay produced gold-standard accuracy on multi-year old scans something like 87% raw; adjust contrast on the photo before import and you recover your sanity on those aging tax PDFs.

Fair use is simple here: the tool edits PDF files. You own the files. Done.

Fair framing: the 2024 fork still does more or less what this does for hobby editing. In 2026, most users weigh "do fewer runtime installs" and "does it explode on 400-page documents" as more valuable than two extra fonts. Both are valid choices if you're on an older machine — but reinstalling a .NET runtime on a laptop that rotates HDD mode? Not a back-and-forth trade I love.

2026 lines bring optional local inference hooks behind a key-free feature toggle:

• Summarize selection — runs a lightweight distilled model one OTA pass over long section-highlights, output into an annotation block you accept or reject. Fully on-device.
• Explain form fields — first-class annotation when a user hovers an unfamiliar field, maps to best-guess fill value. Suggest, never fills. No input transferred anywhere.
• Grammar / structure audit on export — pre-flight script that spotlights edit conflicts across overlay deltas and asks once ("apply destructive?"), giving time to save-off .history before merge flatten.

AI features are helpers, hidden by default until you enable the assistant module this cycle. Nothing runs against your files on the network from my stack — all on-device, all modeled locally, all silent unless invoked. I turned them off for everything except summary scrub on one 90-page redaction QA — no leaks, no cost.

Full walk-the-walk route with emoji step markers. Post-download:

1. 🧲 Extract the archive from the project page to a real folder.
2. 🖱️ Launch the .exe and confirm once given a warning on unsaved mode.
3. 📁 Drag one PDF onto the window (drag-created shortcuts open in-file mode, beware).
4. ✒️ Run toolbar → Markup → test every markup primitive once on a spare page.
5. 💾 File → Flatten-save (first time). Second time use true save-and-close.

Runs live on Windows without a server and without any "Start Free Trial" nag you have to kick off to use. For freelancers working one PDF at a time, this inverts the awkward task log where launching mattered more than editing. For that matter — the thing that took the longest is recovering someone else's poorly authored PDF and keeping their original shapes. What leads is exactly what you do at the very moment your document loads — you start working, not waiting to something.

Rarely a third: optical OCR reading diagonal watermarks as printed body text — very threshold-sensitive, keep pre-OCR normalize checked unless the scan rotates internally.

1. Will Windows Defender or SmartScreen flag it? Yes, first run that isn't in the Store often trips Smartscreen on those quiet days. The error carries the action-launch banner. This current working signature supports signature-unverified but the button path to is "More info" then "Run." Nothing about this indicates malware or anything implying it — this .exe is functionally a PDF editor. It's simply a self-hosted download and being a signed release doesn't change the User experience dramatically.

2. Does it get updated or abandoned? Actively. 2026 point release is the fifth cycle for me, not the first. Push notifications inside the app show a static changelog link; there's no auto-downloader root-level, no missing system change — use the same extraction process to swap builds. A gap between updates isn't a sign of dead project any more than a slow commit cycle is; security notes go into that link first.

3. Any Adobe Acrobat compatibility worry? Acrobat opens this tool's PDF files and sees standard annotation + AcroForm structure. There's a caveat: annotations you authored stay in-editor until flatten; external apps read them via extension-reading mods they mostly already do. If it accepts a flag, accept it — flatten if the tool you're sending the file to is old enough to trip.

4. Do I need to be admin? No. Extract → launch no elevation. If a UAC prompt shows up outside of Office plugin auto-integration path (and the Office interop is optional during archive setup anyway), something else is running as elevated in your user context — kill that process tree.

5. What about Steam or launchers / no DRM chain in it? No Steam client integration even if you got it via a marketplace somewhere — this is a standalone .exe, not certified through Steam. Nowhere is anything like program-dependency on Steam remote libraries expected of this build.

6. Do updates overwrite my saved state? No. Splits are physical: application binary next to a writable state dir. Overwrite just clears the old binary set. But if you extract to the same folder name under a different root, state replicates unless you wipe unrelated folder and restarted.

7. Is it testable without actual Excel/Acrobat/etc? Yes. The .exe requires no external converter. Exported PDF/A conversion is optional, file-search/compile is independent — you don't run separate library dependencies with an assistant stack attached. It runs local to every supported box.

8. Full offline? Never requires a network. Standalone build with no updater persistent and no licence ping. Connectivity happened only for you clicking somewhere obvious, like fetching a newer extracted-folder package.

Right now this is one person with a repo and a changelog rhythm:

• Bugs / reproducers → open an Issue. Include Windows version + PDF structure sample stripped of sensitive content (or notes describing internal doc content — I don't need the actual content).
• Crashes → pull the generated %LOCALAPPDATA%\pdf-annotate\crash.log and attach it or paste the last 30 lines; that's usually enough to reconstruct a workflow.
• Feature ideas — kept "honest first" in Issues; no bot votes, just discussions. Cosmetic ideas lower priority than things affecting form fills or scanning.
• Third-party sponsorships removed — all external extension concerns go to Issues, not off-repo channel pools. Kept generic on purpose: no personal private side-channel to spawn trouble when each integration is something else.

Worth saying: my commentary in threads compounds and reflects while feature ticket is pending, update cycle chooses which directions to bang on first. This is still small-team-sized and you're getting into the feature feedback. Some old notes stacked in closed issues show direction wins during fixes — pre-complaining can't hurt you.

Package builds deploy into an updated self-check circle only if you remember current version and compare the launch screen. Latest 2026 build numbers the launch window label directly, which is exactly right for recognizing you're on a certain release in five seconds even in launch limbo testing — no external sensor and no forced web check. I keep the repo issues active for good communication quality; features rely on that mutual intuition of reading a workflow as the user models first, not reading prompts third.

This readme, and this is as much a note to future contributors as it is deep-dive going through this release: the core editor cycle wasn't the goal first pass, last pass launch cycle keeps everything cross-platform clean. That didn't translate to missing important Windows targets — top left window controls interact interestingly on a HiDPI 4K first open; some users pick fine by window drag border preferences at all screen edges first time. Fine after next compile log if you trace that known weirdness visible, file an issue with your specific rotation.