Editorial and Tool Quality Policy

Purpose

Every page should help a visitor complete a specific task. We publish instructions, examples, limitations, and privacy notes that relate to the working tool on that page—not generic text added only to attract search visits.

Testing

Before release, tools are checked with representative valid inputs, empty inputs, and common errors. Browser compatibility and accessibility are reviewed where practical. File tools are checked for output type, download behavior, size limits, and failure handling.

Content standards

Descriptions must reflect actual behavior. Security or privacy claims must distinguish browser processing from server processing. We do not fabricate authors, credentials, reviews, or usage statistics. When a page links to an external technical or policy source, we prefer the primary source.

Corrections

Functional and privacy errors receive priority. If you find an issue, email hello@freetoolbase.com with enough detail to reproduce it.