KillerPDF 1.8.71 for Windows 10/11: Annotation Fixes, CLI Tools and .NET 10 Requirements

This piece covers what 1.8.70 changes, what the follow-up release adds, and one out-of-date claim in the long-running product blurb that you shouldn't believe.

What 1.8.70 actually changes​

The developer's own GitHub release notes describe 1.8.70 as the release that introduces KillerPDF's four-digit version numbering, hardens releases, repairs difficult PDF editing and saving cases, and polishes comparison, tabs, localization, and other interface behavior. Here are the changes, grouped by what they mean for you:

Keeping your annotations safe​

These are the fixes most likely to matter if you mark up documents for a living:

• Deleting pages no longer strips markup from the pages you keep. The release preserved shapes and other annotations on retained pages when deleting PDF pages (#429). If you've ever cut three pages from a contract and found your highlights missing from the other twenty, this is the fix.
• Annotations stay where you put them after saving. The update preserved annotation position and orientation when saving PDFs whose page content leaves a transform active. Put simply, some PDFs leave a coordinate transformation (a rotation, scale or offset) active in the page content. Without handling for that, annotations can come out shifted or rotated when the file is saved.
• Merging PDFs with unusual structures. KillerPDF now allowed PDFs with recursive Form XObject resources to be combined (#421). Form XObjects are reusable blocks of content inside a PDF. When their resource references loop back on themselves, a merge tool can get stuck. The changelog doesn't say how common these files are, so this is a targeted fix, not a sweeping one.

Editing and interaction reliability​

The release also kept text editing, selection feedback, and touchpad zoom reliable, including font changes, multiline entry, and region selection (#428). Inline text editing is one of KillerPDF's main features, so fixes here have a direct effect on everyday use.

Hardening, with limited detail​

One line reads hardened native library loading and release artifact verification. That's a good sign. Native DLL loading is a well-known weak spot for Windows apps, and verified release artifacts help guard against tampered downloads. But the changelog doesn't mention a specific vulnerability, threat model or CVE, so don't read this as a security patch for a known exploit. It's defensive work on how the app loads libraries and how releases are checked.

Interface polish​

• The PDF comparison bar is now docked below the documents and connected to the split divider. Its accent-colored controls were cleaned up, and selected toolbar tools stay sharp.
• Split-view state is restored properly. Document tabs, flyouts, shortcut colors, footer and sidebar controls, and the retro "98SE" theme all got polished.
• Localized toolbar captions and the key names on the website's Help page now appear in full (issue #230).

Section summary: 1.8.70 is about reliability. It's less likely to lose or shift your markup, handles some tricky merges better, and fixes rough edges in comparison and split-view.

Don't stop at 1.8.70: 1.8.71 is already out​

Neowin's listing went up on September 27, but the developer had already moved on. The official KillerPDF site lists version KillerPDF v1.8.71 · released 2026-09-26 · size ~9.6 MB exe · platform Windows 10/11 x64. The matching GitHub release is timestamped early on September 27, which is likely just a time-zone difference. The developer's summary says 1.8.71 expands automation, improves printing, and makes installation more reliable.

What's new in 1.8.71:

• More command-line power: the developer added CLI commands for page rotation, deletion, reordering, blank-page insertion, duplication, document details, and text search. This is useful for admins who script document handling in PowerShell.
• Smarter printing: KillerPDF now chose the print dialog's initial orientation from the PDF while keeping the manual override (#432).
• More reliable upgrades: the installer retried installation when Windows briefly keeps the previous version's files open (#434). Anyone who has seen an update fail because a file was still locked will recognize the problem.

A 1.8.71 package has also gone through Microsoft's winget community repository. The pull request shows the validation pipeline passed, so winget install killerpdf should get the current build once the manifest is live. In short, install 1.8.71. It includes everything in 1.8.70.

Fact check: the ".NET Framework 4.8, single EXE" claim is out of date​

Neowin's listing still carries the product description it has used for months. It says no runtimes are installed and that everything runs from one executable targeting .NET Framework 4.8. That wording goes back at least to Neowin's KillerPDF 1.7.0 listing, which said everything needed is inside the EXE (targets .NET Framework 4.8, which ships with every supported Windows release). MajorGeeks' 1.8.70 page repeats the same claim.

It isn't true for the 1.8 series. The developer's README says both the reusable engine and the Windows application target .NET 10, with the application using net10.0-windows. It also says the release pipeline builds KillerPDF.exe, a compact framework-dependent installer, and KillerPDF-Portable.exe, a self-contained offline edition. That explains the two download sizes Neowin lists: about 9.6 MB for the standard build and 69.7 MB for the portable one. The portable edition carries its own .NET runtime. The small one depends on the .NET 10 Desktop Runtime.

The change dates back to 1.8.0. Its release notes say KillerPDF 1.8 replaces its legacy PdfSharpCore document pipeline with an independently authored .NET 10 PDF document engine. Rendering didn't change: PDFium remains KillerPDF's rendering and display backend, while PdfPig continues to handle text extraction.

What this means for you:

Privacy: "no telemetry" is not the same as "never goes online"​

The official site says no telemetry is sent and no ads... ever. That fits the developer's anti-bloat pitch. Two things are worth knowing if you're in an air-gapped or strictly firewalled environment:

1. The developer's site says KillerPDF checks GitHub for newer stable versions at startup by default and asks before installing anything. You can turn the check off. The site says there's no separate background service.
2. OCR runs locally on Tesseract, but extra language models downloaded only on demand so the base download stays small.

Neither is telemetry. Still, anyone writing firewall rules or approving software for a sensitive network should know the app can reach GitHub unless you disable the check.

A note on the test numbers​

The developer's site reports that 1.8.70 saved 40,563 PDFs from the same 47,024-file test set used for 1.8.6, with identical outcomes and no crashes or timeouts. It's an impressive regression suite for a free project, and the corpus is described as open and versioned. Keep in mind these are the developer's own numbers, not an independent audit.

Bottom line​

KillerPDF 1.8.70 is a solid, unflashy fix release. If you edit, prune and merge marked-up PDFs, the fixes for annotation loss and misplacement are the reason to update. The hardening work is welcome, even if the changelog says little about it. Now that 1.8.71 is out with more CLI commands, better print orientation and fewer failed installs, it's the version to get. When you pick a package, go by the developer's current documentation. The ".NET Framework 4.8, no runtime" line that still shows up on download sites describes the old 1.7-era app, not this one.