How we work

Editorial standards

We test browser-based text and developer utilities with concrete inputs, boundary cases, and expected outputs. Searchable pages must explain what changes, what remains unchanged, and where encoding or formatting can lose information.

Input/output tests

Examples include empty, multiline, Unicode, and malformed input where relevant.

Privacy checks

Core transformations run in the browser unless a page says otherwise.

Focused inventory

Search emphasizes text, writing, and developer utilities.

Human review

Generic pages are held out of search and advertising until improved.

Review and correction process

Every indexable page must answer a specific user question, explain important assumptions, and offer more than a generic definition. Interactive tools are tested with boundary values and at least one hand-calculated example. Material corrections are made in place; pages that do not meet the standard are removed from search and advertising until they are improved.

Content is educational. It is not legal, tax, insurance, medical, or investment advice. Users should verify decisions with the relevant provider or qualified professional.

Primary references we prefer

Last reviewed: July 11, 2026