Everyday and developer utilities
These small tools cover text cleanup, structured-data checks, unit and date calculations, and common generators. Each page separates the expected input from the copyable or downloadable result.
- Browser-based tools
- Data handling is disclosed on each tool
- No signup; device limits apply
Text and developer data
JSON, XML, YAML, and CSV tools handle syntax and structure, not the business meaning of fields. Verify field names, string-versus-number types, and character encoding before importing output elsewhere.
URL, HTML, and regular-expression tools interpret or escape input. Check the data policy before pasting credentials or personal information, and never leave a sensitive result in a public log.
Units, time, and everyday calculations
Conversions follow the displayed definitions and rounding. Region-dependent measures such as cups need an explicit US customary or metric basis.
Date and time results depend on zones, leap years, and endpoint choices. A weekday counter that excludes only weekends is not a Korean statutory or banking calendar unless holidays are explicitly included.
Use generated values safely
UUIDs, random test data, and passwords need settings appropriate to their purpose. Keep synthetic records in test systems and avoid making them resemble identifiable real people.
One automated accessibility measurement is not a complete audit. Combine contrast figures with keyboard, zoom, and assistive-technology checks on the real interface.
Sources
Frequently asked questions
Is pasted text stored?
A standard local utility processes it in the page. Exceptions such as a persistent browser notepad declare storage in their data notice.
Does formatting validate business rules?
No. It can catch syntax problems but cannot know the domain meaning or downstream system requirements.