Editorial standards

These standards apply to every piece of written content published on ToolNest: the guides in our blog, the editorial introductions on each tool category page, the documentation on individual tool pages, and the answers in our FAQs.

They do not apply to the raw output of a tool — a converted file, a formatted string or a calculated number. Tool output is deterministic and is covered by our disclaimer.

Every article is written by a named member of the ToolNest editorial team and reviewed by a second person before publication. The reviewer checks three things: that the claims are accurate, that the steps actually work when followed on a clean machine, and that the article answers the question in its title.

Where a topic needs specialist knowledge — tax treatment in a loan calculator, for example, or the accessibility implications of a colour converter — we say so in the article and point readers to a qualified professional rather than implying we are one.

We prefer primary sources over secondary ones. In practice that means:

• Specifications and standards come from the body that publishes them — the W3C for HTML and CSS, the IETF for RFCs, the Unicode Consortium for character encoding, ISO for units.
• Legal and regulatory statements come from the legislation itself or the regulator's own guidance — the ICO for UK data protection, the European Commission for GDPR, the FTC for US advertising rules.
• Product behaviour is verified by using the product, not by repeating a vendor's marketing page.

We link to the source so you can check it yourself. If a claim cannot be traced to a source we can point at, we do not publish it as fact.

A tool is not described as working until it has been tested against known-good inputs and edge cases: empty input, very large input, non-Latin characters, malformed data and the boundary values of any calculation. Where a tool has a documented limit, the limit is stated on the page rather than discovered by the reader.

Guides that describe a process are walked through end to end on a fresh browser profile before publication, so that a step which only works because of a cached setting or an existing login does not slip through.

We use AI tools the way we use a spell-checker or a search engine: as an aid, not as an author. AI may help us draft an outline, suggest a phrasing or catch a typo. It does not decide what we publish.

Every factual claim, every code sample and every step in a guide is verified by a human against a primary source before it goes live. We do not publish AI-generated articles at scale, and we do not use AI to fabricate reviews, author bios or testimonials.

Articles carry a visible publication date and, where they have been revised, an updated date. We review evergreen guides at least once a year and re-check them sooner when the underlying product, standard or regulation changes.

When a change makes part of an article wrong, we correct the article rather than quietly deleting it, and we note the change in the article itself.

If you find an error, tell us and we will fix it. Email hello@toolsnest.me with the page URL and what you believe is wrong.

We aim to acknowledge every correction report within 2 business days. Factual errors are corrected as soon as they are confirmed. Where a correction is substantive, we add a dated note to the article so readers can see what changed and when.

Editorial decisions are made independently of advertising. Advertisers cannot buy a place in an article, a favourable review, or a mention in a guide. Advertisements on the site are served by Google AdSense and are labelled as advertisements; they are not endorsements by ToolNest.

How the site is funded is set out in full on the About page.

If you have a question about how we work, or you would like to see the sourcing behind a specific claim, write to hello@toolsnest.me or use the contact form.