Define the job and its limits
We keep each tool focused on one task. Before publishing, we document supported inputs, deliberate limits, and cases the tool should leave for review instead of guessing.
How we test tools
A tool should do one clear job, explain its limits, and make its output practical to review before you share it.
Our review approach
Got A Tool is an independent collection of focused browser tools. The checks below guide how we review a tool before publishing and when changing its file-handling behavior.
Use representative inputs
We test normal inputs alongside malformed files, unsupported formats, empty values, size limits, and edge cases that could otherwise create a misleading result.
Inspect the downloaded result
When a tool creates a file, we check the resulting file itself: its structure, rows, fields, or visible content as appropriate. A successful button click alone is not enough.
Keep reviewable data reviewable
If a value cannot be interpreted safely, the intended behavior is to identify it for review or preserve it unchanged. We avoid silent format guesses and silent deletion.
Check local processing claims
For tools described as processing a selected file locally, we review the processing path and browser network activity during the tested workflow. Advertising, consent, and analytics are separate site services and are described in the Privacy Policy.
Check the page people actually use
We review the live browser flow, mobile layout, accessible controls, server-rendered page details, and nearby tools that could be affected by a shared change.
What this means for you
Read each tool's instructions and warnings before downloading a result. Supported formats and limits vary by tool, and a review message is a signal to check that input rather than a failure to work around.
These checks do not make a tool a substitute for professional, legal, security, or records-management advice. Keep an original copy of important files and review output before using it in a critical workflow.
For details about cookies, advertising, analytics, and local file processing, read the Privacy Policy.
Found a problem?
Send the tool name and a short description of what happened. Do not include private files, passwords, or sensitive information.
hello@gotatool.com