How we build and check our tools

1. Start with a defined user task

Each tool begins with a specific task, such as estimating concrete volume, comparing a mortgage payment, resizing an image, validating JSON, or counting words. We define the inputs, expected output, supported units, and important failure cases before treating a tool as ready for public use. We do not consider a page valuable merely because it targets a search phrase.

Tools that are too shallow, redundant, or not yet documented to this standard can remain available for direct use while being excluded from search indexing until they are improved.

2. Use explicit formulas and conversions

Deterministic calculators use formulas implemented in JavaScript. Unit conversions use declared conversion factors; loan tools use standard amortization equations; geometry tools calculate area or volume before applying user-selected coverage, waste, or cost assumptions. Where rounding affects the result, the displayed result is an estimate rather than a quote.

3. Explain assumptions and limitations

Every priority tool is reviewed for hidden assumptions. A paint estimate depends on surface area, coats, openings, and manufacturer coverage. A mortgage estimate does not include every lender fee or local tax rule. An image conversion can change metadata, color profiles, transparency, or perceived quality. Tool pages should explain these limitations near the calculation rather than burying them in a sitewide disclaimer.

Financial, health, legal, construction, tax, and safety-related results are informational estimates. They are not professional advice, diagnoses, bids, approvals, or guarantees. Visitors should confirm important decisions with current official information or an appropriately qualified professional.

4. Prefer primary and authoritative sources

When a tool depends on an outside standard or factual threshold, we link to a primary or authoritative reference where practical. Examples include the National Institute of Standards and Technology for SI units, RFC 4648 for Base64, the JSON specification, OWASP password guidance, the U.S. Energy Information Administration for electricity terminology, and the Consumer Financial Protection Bureau for mortgage concepts.

Sources support the explanation; they do not transfer responsibility for our implementation. We still test the calculation and identify when the source describes a general rule rather than a universal requirement.

5. Test the real page, not only the formula

Automated checks cover the tool registry, route integrity, prerendered metadata, canonical URLs, structured data, keyboard behavior, responsive navigation, and representative calculations. Browser tests open every tool route and fail when a page does not render or produces unexpected console errors. File tools also enforce browser-side size, page-count, or image-dimension limits to reduce crashes and excessive memory use.

Automated checks cannot prove that every real-world result is appropriate. We combine them with manual review of copy, assumptions, source links, mobile behavior, and worked examples. A passing build is a minimum release condition, not evidence of professional certification.

6. Keep private data in the browser where practical

Free Toolset is designed around client-side processing. Calculator inputs, pasted text, and selected files are processed by browser code whenever the tool allows it. Some browser features or third-party libraries may behave differently by device, and advertising or basic site infrastructure can make their own network requests as described in our Privacy Policy. A tool page should never imply that all internet activity stops simply because its calculation is local.

7. Corrections and review dates

Priority pages display a review date and are revisited when formulas, standards, browser support, source material, or user reports indicate a change is needed. Corrections should update both the tool behavior and the explanation. Material changes are tested before release.

If you find a calculation, source, accessibility, or privacy problem, email contact@freetoolset.com with the tool URL, the inputs used, the result you expected, and the result you received. Do not include confidential financial, medical, or account information.