Developer tools
Everyday utilities, ad-free and local
The small tools a working developer reaches for several times a day: encode a string, plan a subnet, generate identifiers. They run locally, keep no history, and carry no advertising at all — because pasting a token or a config fragment into an ad-funded page is a bad habit the industry should not encourage.
What people use these for
- Encode or decode Base64, URL and HTML entities, including emoji and Indian scripts
- Plan IPv4 or IPv6 subnets and check the usable host range
- Generate UUIDs, ULIDs or NanoIDs in bulk
- Look up an HTTP status code or an ASCII value without leaving the tab
Frequently asked questions
- Why are there no ads on these pages?
- Because developers block them, which makes the segment unmonetizable by advertising anyway, and because pasting a config fragment or an encoded token into an ad-funded page is a habit worth discouraging. Third-party ad scripts run in the same page as whatever you paste. Removing them costs us nothing we were ever going to earn and removes a class of risk entirely, so the developer tools here carry no advertising and never will.
- Do these tools keep a history of what I paste?
- No. There is no history, no account, and no server call — the encoding, the subnet arithmetic and the identifier generation all happen in your browser. Nothing you paste is stored anywhere, including in your own browser's storage, so closing the tab is all it takes to be rid of it.
- Does the Base64 tool handle emoji and non-Latin text?
- Yes, and this is where naive implementations break. Encoding text one byte per character corrupts anything outside Latin-1 — an em dash becomes a control character and Devanagari, Gurmukhi or Arabic is destroyed outright. This tool encodes through UTF-8, so Hindi, Punjabi, Arabic and emoji all round-trip back to exactly what you typed, and malformed input is rejected rather than silently guessed at.
- Which identifier format should I generate?
- UUID v4 when you need a random identifier that anything will accept and you do not care about ordering. ULID when you want the same uniqueness but sortable by creation time, which keeps database indexes tidy and makes logs readable in order. NanoID when the identifier goes in a URL and length matters — 21 URL-safe characters instead of 36.