KillerPDF 1.8.6 saved 40,563 PDFs across the three main collections. Every file kept the same outcome and diagnostic detail as 1.8.4. All five measured passes matched, and the 80 damaged inputs produced no crashes or timeouts.

Compared with 1.8.4, median times were 18.2% shorter for regression, 3.4% shorter for stress, and 1.9% shorter for standards and color.

This measures batch opening and saving, not rendering accuracy or PDF conformance.

Source: v1.8.6 benchmark report and measured runs.

The official KillerPDF 1.8.4 release payload saved 40,563 PDFs across the three main collections. Every file kept the same outcome and diagnostic detail as 1.8.3. All five measured passes matched, and the 80 damaged inputs produced no crashes or timeouts.

Compared with the separately recorded 1.8.3 session, median times were 13.7% longer for regression, 6.4% longer for stress, and 0.5% shorter for standards and color. The 1.8.3 payload was framework-dependent, while the official 1.8.4 portable release contains a self-contained .NET 10.0.11 payload, so the difference is not isolated to application code.

This measures batch opening and saving, not rendering accuracy or PDF conformance.

Source: v1.8.4 benchmark report and measured runs.

KillerPDF 1.8.3 saved 40,563 PDFs across the three main collections, 1,485 more than 1.8.2. No previously successful input became a skip or save failure. All five measured passes matched on every file's outcome and diagnostic detail. The 80 damaged inputs produced no crashes or timeouts.

Compared with the recorded 1.8.2 baseline, median times were 8.5% longer for regression, 2.0% longer for stress, and essentially unchanged for standards and color. KillerPDF 1.8.3 completed more successful saves; both versions were not rerun in alternating passes during the same session.

This measures batch opening and saving, not rendering accuracy or PDF conformance. Nineteen previously skipped inputs now open but fail save-time checks; the cards include those failures.

Source: v1.8.3 benchmark report and measured runs.

All five measured runs returned identical outcome totals. The test completed with zero application crashes or timeouts.

The first full 47,024-file baseline. All measured runs returned identical outcome totals, with zero application crashes or timeouts.

Source: machine-readable result summaries and measured runs.