Why EncodeKit
Your data stays on your device
Every tool runs with plain JavaScript in the page you are looking at. Tokens, internal URLs and customer data you paste are never sent to a server, so you can use the tools at work without worrying about leaks. You can confirm it in your browser's network tab.
One page per tool, no clutter
Each tool has its own page with live conversion, a copy button and a short explanation of the format, including code snippets for common languages.
Handles the edge cases
Unicode and emoji are handled correctly everywhere, and the URL, Base64 and Hex tools can also read legacy Japanese encodings (Shift_JIS, EUC-JP) when you need to debug old systems.
Encoding is not encryption
Encoding converts data into another format by a public rule — for example, a space becomes %20 in a URL. Decoding reverses it. Anyone can decode encoded data, so encoding (including Base64 and JWT payloads) never protects secrets. Use encryption for that, and a hash to check integrity.
| Tool | Typical use |
|---|---|
| URL encode / decode | Build query strings, read percent-encoded URLs |
| Base64 | Data URIs, Basic auth headers, binary data in JSON |
| HTML escape | Show code on a web page, check XSS escaping |
| Unicode escape | Read \uXXXX sequences in JSON and source code |
| Hex | Inspect the bytes behind a string, debug mojibake |
| JWT decoder | Check claims and expiry of an access token |
| Hash generator | Verify downloads with SHA-256 checksums |
| Unix timestamp | Read epoch times in logs and APIs |
| JSON formatter | Pretty-print and validate API responses |
| UUID generator | Primary keys and test data (v4, v7) |
| Punycode | Internationalized domain names for DNS and TLS |
| QR code generator | Share a URL on print or screen |
| Regex tester | Build and debug regular expressions |
| Character counter | Word, character and byte limits |
| Password generator | Strong random passwords |
| Color converter | HEX ⇄ RGB ⇄ HSL and WCAG contrast |