Testing and corrections

How each tool is tested

Before a tool goes live it is run against a fixed set of test files: a text report, a scanned document, a photo-heavy brochure, a slide export, a form with fields, and large files built to find memory limits. Automated tests check the output of the PDF engine, such as page counts, page order and rotation, every time the site is built.

Each tool is then tried by hand on a phone-sized screen and on a laptop. The test results shown on tool pages come from the same code the tool runs, so a page cannot claim a result the tool does not produce.

How limits are stated

When a tool cannot do something well, the page says so, for example when a layout may shift during conversion or a feature does not survive a merge. Numbers such as file sizes and times always name the device and the date they were measured.

Corrections

Report a mistake on the contact page. Confirmed mistakes are fixed, and the fix is listed below with the date.

Correction log

No corrections yet.