Editorial Policy

FreeWebTools publishes 286 tools in 10 languages. This page describes who writes them, how a tool page is put together, what the byline and the "updated" date on each page actually mean, and what to do when you find something wrong. It is a description of current practice, not a promise about the future.

Who publishes these pages

Tool pages carry the byline FreeWebTools Editorial Team. That is a group credit for the people who build and maintain the site, not a pen name for one writer, and we do not attach an invented author or invented credentials to a page. Where a tool touches a regulated subject — health measurements, tax, loan repayment — the page states what the calculation does and does not do rather than claiming professional authority it does not have. Nothing here is medical, legal or financial advice.

What runs where

Most tools on this site are JavaScript that runs inside your own browser. Calculators, converters, text tools, generators, timers and games compute locally: the numbers, text and images you enter are processed on your device and are not uploaded. The image converters, for example, use the browser canvas, so a photo you drop in never reaches our server.

Some tools cannot work that way, and those pages say so. Network diagnostics — redirect checker, website status, header checker, DNS and WHOIS lookups, SSL checks — send the address you type to our server, because a browser is not allowed to read another site's response headers. Live counters query public APIs for the channel you name. The AI writing tools send your text to a language-model provider to be processed. If a tool needs to send your input somewhere, that is a property of the tool, not a choice we made to collect data.

How a tool page is built and checked

1. The tool comes first. Each page is built around a working tool, not around an article with a widget attached, and we measure where the tool lands on the screen so it is reachable without scrolling on a phone.
2. The rule is stated, not just applied. Where a tool implements a formula or a standard — HTTP status codes, unit definitions, payroll decimal rounding, BMI — the page states the rule it uses so you can check the output by hand.
3. Output is verified against a reference. Conversions and calculations are checked against published values from the relevant authority rather than against another converter website.
4. Pages are tested in a real browser. Pages are rendered at desktop and mobile widths and checked for text contrast against the WCAG AA threshold in both the light and dark themes, and for JavaScript errors in the console.
5. Corrections are made in place. When we find or are told about an error, we fix the tool or the text and the page's updated date moves. We do not silently delete pages that were wrong.

What the "updated" date means

The date in the byline is the date that page's own template last changed in our source repository — the commit date of the file, or the file's modification time when it is newer than the last commit. It is not the current date, and it does not roll forward on its own. If a page says it was updated in August, nothing on it has been edited since August. A page with an older date is not stale by default: a unit conversion that was correct two years ago is still correct.

Money and independence

The site is free to use and carries no sign-up, no account and no paywall — there is nothing to register for. It is funded by advertising: pages display Google AdSense units, which are marked as ads and are not editorial content. Advertisers have no say in which tools we build, what a page says, or how a tool calculates. We do not take payment to recommend a product, and the tools do not rank or endorse commercial services.

Languages

Tools are published in 10 languages: English, French, German, Spanish, Portuguese, Italian, Russian, Turkish, Polish and Chinese. Each language has its own URL and its own text; translated pages are not machine-translated on the fly in your browser. Coverage is not identical across languages — some explanatory text exists only in English so far, and where a translation is missing the page falls back to English rather than showing a broken key.

Reporting an error

If a tool gives a wrong answer, a page contradicts itself, or a translation is wrong, tell us and we will fix it. Include the page address and what you expected instead — that is usually enough to reproduce the problem. Write to [email protected], or use the Contact page.

See also: About · Privacy · Terms