FileTools Kit · Guides · About · Contact

How FileTools Kit tools and guides are tested

This page explains what I check before a tool, a fix, or a guide goes live, and what happens when something turns out to be wrong. I am one person, so this is a practical routine rather than a lab. It is written down so you can judge how much to rely on the site.

Before a tool or a fix ships

• Real files. PDF tools are run on several kinds of PDF: a text PDF exported from a word processor, a scanned PDF, a multi-page document with mixed page sizes, and a password-protected file to confirm it is refused with a clear message rather than failing silently.
• Open the output. Every download is opened in a second program, such as the browser's PDF viewer or an image viewer, to check that the pages, order, rotation, and text are what the tool says they will be.
• Phone width. Pages are checked at phone width as well as on a desktop, including that buttons can be reached and nothing runs off the screen.
• Edge cases. Empty inputs, very large inputs, and inputs in the wrong format, such as WebP where only JPEG or PNG is accepted, should give a plain message rather than a broken page.
• The production build. Changes are built with the same command the live site uses, and checked in a preview deployment before they are merged.

Before a guide is published

• Button names match the tool. Steps use the exact labels on the page, checked against the tool's source code.
• Claims are checked against the code. If a guide says a tool does something, the code has to do it. If a tool has a limit, such as no OCR, no target-size box, or no Roman numerals, the guide says so.
• No invented numbers. Guides do not quote compression percentages, user counts, or success rates I cannot show. Where a published figure is used, such as WHO BMI bands, the source is named.
• Health and money topics carry a clear note that they are general information, not medical or financial advice.
• A last-updated date appears on every guide and changes when the content changes.

What I do not test

I cannot test every browser version, every phone, or every PDF ever made. Very old browsers, unusual PDF features such as digital signatures and forms, and very large files are the most likely to cause trouble. The guide When browser PDF tools fail lists the known cases.

Corrections

If a tool gives a wrong result or a guide does not match what you see, email support@filetoolskit.com with the page address, your browser and device, and what happened. Please describe the file rather than attaching a private document. Fixes are listed on the What's new page with their date.

Last updated 10 October 2026. Souren Das, Bengaluru.