Developer & Text Tools (142)
Developer friction is mostly small and frequent: inspect a JSON blob, diff two CSVs, decode that base64 in a JWT, count words in a draft, convert a color to hex. The right tool is one that opens instantly and never phones home.
Every tool here runs entirely client-side — your code, keys and text never leave the browser. The parsers follow the actual specs where it matters: CSV quoting per RFC 4180, UTF-8-aware counting, exact base64 alphabet and padding.
Bottom line: bookmark this page next to your editor. When the task is 'turn this into that' or 'count what's in here', the answer is two clicks away and stays on your machine.
Calculators (3)
Converters (32)
Text Tools (95)
Generators (10)
Toolbox (2)
Frequently asked questions
Is my code or text uploaded anywhere?
No. All parsing and conversion runs in your browser with JavaScript — the page never transmits your input, which is why it also works offline once loaded.
Which CSV rules does the CSV parser follow?
RFC 4180: quoted fields, escaped double quotes, embedded commas and CRLF line breaks. That is the dialect most exports claim and the one that breaks naive split(',') code.
Does Base64 encoding handle Unicode?
Yes — text is UTF-8 encoded before the base64 alphabet is applied, which is the correct pipeline for emoji, CJK and any non-ASCII content.
Are the text tools good for SEO and writing work?
The counters are character-accurate (UTF-8 aware, not byte counts), which is what metadata limits and platform caps actually measure.