LazyTools

🔒 Every tool runs in your browser, the files and values you enter are never uploaded to any server. How it works

Developer Tools

Encode, decode, hash and test, with the browser's own engines, so results match your code exactly. Tokens, payloads and secrets are exactly what shouldn't touch third-party servers: here they never do.

Developer utilities that keep secrets local

These are the small, sharp tools you reach for a dozen times a day: Base64 and URL encoding, JSON and other formatters, hashes (SHA family via the browser's Web Crypto), JWT decoding, regex testing, an exact LLM token counter, and Ethereum helpers (BigInt-exact wei⇄ether, Keccak-256, EIP-55 checksums). Each does one job cleanly and shows its working.

Crucially, they run entirely in your browser, so pasting an API key, a private JWT, a config file or a wallet address never sends it to a server. That's the difference between a convenient tool and a liability: your secrets stay on your machine, and the tools keep working offline.

Frequently asked questions

Why does client-side matter especially for developer tools?

Because the inputs are secrets: JWTs are live credentials, Base64 blobs are often API payloads, and hashed strings can be keys. Pasting those into a server-backed tool hands them to that server. Every tool here runs locally, verify with the network tab or by going offline.

Do these tools match what my code does?

Yes, by construction: the regex tester runs the browser's actual RegExp engine, hashing uses the native Web Crypto implementation, and Base64/URL encoding use the platform functions with correct UTF-8 handling.

Why is there no MD5?

The Web Crypto API excludes it deliberately, MD5 collisions are practical, so it fails as a security primitive. SHA-256 is the modern default for everything MD5 used to do.