What gets published
A tool ships only when it performs a complete task without an account and can explain what changes, what stays unchanged, and when the result needs human review. The catalog covers text cleanup, counting and slugs; JSON, YAML, CSV, Base64, hashes and Markdown; plus URL encoding and campaign-link construction.
How tools are checked
Transformation logic is exercised with automated examples, including empty input, Unicode, malformed values, and known edge cases. Every release also passes Astro type/build checks, generated-route and sitemap guards, and an axe-based static accessibility check. Keyboard, status, and narrow-screen behavior remain part of manual review.
How guidance is written
Supporting copy follows the shipped implementation and tests. It names defaults, irreversible transformations, unsupported formats, and cases where a dedicated validator or project-aware tool is safer. The site avoids invented numeric promises and does not publish placeholder pages to make the catalog look larger.
Browser-local boundary
Current tool input is processed by code running in the page rather than an upload endpoint. The site still loads normal web assets, and copying a result into another service transfers it to that service. Each tool repeats the boundary and any format-specific privacy caution beside its controls.
Corrections and updates
Behavior notes are updated when the implementation changes. Reports of a reproducible error, unclear limitation, inaccessible control, or misleading explanation are reviewed against the code and a minimal test case before the public copy is changed.
Contact
Site questions, correction reports, privacy questions, and domain inquiries can be sent to [email protected].