Accuracy comes first
Everything we say about a tool is checked against what that tool actually does. When we describe a file format or a standard, we rely on the primary source where one exists, such as the PDF specification, IETF RFCs, or the W3C and WHATWG standards.
Examples are real
Worked examples on tool pages and in guides come from running the tool, not from guessing what the output would look like. If a tool's behavior changes, the example has to change too.
We write down the limits
A tool that fails quietly costs you more time than one that tells you what it cannot do. Tool pages list known limitations, and guides say when you would be better off with different software, including paid software, if that is the honest answer.
Advertising stays separate
Ads pay for the site, but they do not decide what we write. Advertisers have no say over our content and we do not publish paid reviews. Tools are recommended because they fit the job. When we recommend our own tools, the context makes that clear.
Keeping pages current
Each guide shows when it was last updated. We update pages when tools, formats or browser behavior change.
Corrections
If you spot a mistake, please tell us or email [email protected]. We check every report and fix confirmed errors. Significant changes to how a tool works are recorded in the changelog.