togotools.top technical reference
Technical reference
Encode and decode URL, Base64, Base64URL, Hex, Unicode, HTML entities, and JSON strings locally in the browser, with candidate results for common automatic recognition cases.
Common encoding differences
| URL Encode | Escapes text so it can safely appear as a URI component |
|---|---|
| Base64 | Represents bytes as ASCII using +, /, and = characters |
| Base64URL | URL-safe variant using - and _, often without trailing padding |
| Hex | Represents each byte with two hexadecimal characters |
| HTML entities | Represents characters such as < and & as < and & |
Example: Base64 and Base64URL
Base64 is encoding, not encryption; anyone with the result can decode it. Base64URL is common in JWTs and URL parameters, but padding rules vary between systems.
Input: hello?
Base64: aGVsbG8/
Base64URL: aGVsbG8_Decoding limits
- Character encoding matters; Chinese and other Unicode text normally uses UTF-8 bytes for Base64 and Hex.
- Automatic detection shows candidates and does not prove that an input has one correct interpretation.
- URL Decode reports incomplete percent escapes instead of silently changing the input.
Frequently asked questions
Does Base64 protect a password or token?
No. Base64 is reversible encoding and provides no confidentiality. Use a correctly configured encryption scheme when secrecy is required.
Why are Base64 and Base64URL results different?
Base64URL replaces URL-unsafe characters and often omits padding. The decoder must use the matching variant.