How we check
A PDF editor earns trust one saved file at a time. This page says how FreePDFEdit is tested, what a date on our pages means, and what we do not check, so you can judge for yourself how far to rely on it.
The rule behind everything
A file you save is checked by opening it again, not by trusting the code that wrote it. When you change or remove text, the editor itself reads the new PDF back after saving, looks inside the area you changed, and tells you whether the old words are gone and the new ones are there. That check runs on your device, for your file, every time. The tests below do the same thing on a larger set of files.
What is tested, and on which files
The tests use real PDF files, not files written to pass. They include documents from word processors and invoice programs, a published tax form with a fillable form, bookmarks and accessibility tags, documents in right to left scripts, files locked with a password, pages stored sideways, fonts of every common kind (TrueType, OpenType, Type 1 and Type 3), and pictures of pages made the way a scanner or a phone camera makes them: tinted, grainy, tilted and soft.
| What is tested | How | How much |
|---|---|---|
| The PDF engine | Automatic tests that open real PDF files, change them, save them and read the result back. | 118 tests in 16 groups |
| Changing text in typed PDFs | A real browser opens the editor, changes a line in each file, saves, and the saved file is read by other programs. | 11 kinds of PDF |
| Text in other scripts | The same, for Arabic, Persian, Urdu, Hebrew, Greek, Cyrillic, Hindi, Thai, Chinese, Japanese, Korean and accented Latin. | 16 cases |
| Text in scans and photos | Pictures of pages are opened, read, changed and saved, and the saved page is compared with the original picture. | 13 kinds of page |
| Making files smaller | Files with photos, tags and fillable forms are shrunk, and the result is checked for what it kept. | 3 kinds of file |
| Every saved file | Opened in three other PDF readers: Poppler, Ghostscript and pypdf in its strict mode. Any complaint fails the run. | All files the tests save |
Counts as of 18 November 2026. They grow when a new kind of file shows a problem.
What a passing test means
A change to text passes only when all of these hold for the saved file:
- The new words can be found and copied from the saved PDF by another program.
- The old words are no longer in the changed area, not even hidden under something.
- Every line that was not changed reads exactly as before.
- The page still opens in three other PDF readers without a warning.
- Where a picture is involved, the saved page is compared with the original picture by eye and by pixel.
What a last checked date means
Each guide and tool page shows the date it was last checked. On that date the page was read against the editor as it was that day: every step was followed, every button name compared, every limit read from the code that sets it. The date is set by hand. It never moves by itself, and it is never set to a day before the check or after it.
Facts about PDF files in general, such as how fonts are stored or why a black box is not a redaction, come from the PDF standard itself (ISO 32000) and from testing real files. When a page names an outside source, it names it in the sentence where the fact is used.
What is not checked
- Every PDF in the world. PDFs are made by thousands of programs, some of them careless. A file that none of our tests resembles can still trip the editor up.
- Every scan. Words in pictures are read by a program, and a blurred, tiny or handwritten word can be misread. Always read a changed line from a scan before you send the file.
- Every browser. The automatic tests use Chrome. The site is built for Safari, Firefox and Edge as well, but they are not part of the automatic tests.
- Whether a change is allowed. We check that the editor does what you ask. We cannot check whether you should ask it.
- The answers of the AI assistant. The assistant suggests changes; we check that they are applied as shown, not that the content it writes is right. Read what it changed.
When something goes wrong
Most of the tests above began as a file that went wrong. When a kind of file shows a fault, a file that fails the same way is added to the tests and the editor is fixed until it passes. The test stays, so the same fault cannot come back unnoticed.
How to report a mistake
If the editor got something wrong, or a page on this site says something that is not true, write to info@freepdfedit.org. Say which page or which kind of file, what you expected and what happened. Please do not send a document with private details; the contact page says how to show us a problem safely. A mistake on a page is corrected on that page, and the last checked date moves when it is.
Last updated: 18 November 2026