How to use it 01 Paste text into the input and pick an operation; the output updates live. 02 Accept the detection chip's suggested decode, or chain the output back into the input with the arrows button. 03 Set the Caesar shift for the cipher operation, or open the code-point table for the first 128 characters. 04 Read the stats bar for characters, code points, UTF-8 bytes, words, lines and unique characters.
Worked readouts
Base64 of CalcX 2026 → Q2FsY1ggMjAyNg== ; URL-safe Base64 of user:pass → dXNlcjpwYXNz .
Hex of café → 63 61 66 C3 A9 — five UTF-8 bytes for four characters.
URL component encode of q=hello world&lang=zh → q%3Dhello%20world%26lang%3Dzh ; full-URL encode of https://example.com/a b?c=1&d=2 → https://example.com/a%20b?c=1&d=2 .
ROT13 of Vendor Portal → Iraqbe Cbegny ; Morse of SOS → ... --- ... ; JSON string escape of a"b + newline + c → a"b\nc ; é as a Unicode escape → \u00E9 .
The detector labels Q2FsY1ggMjAyNg== as Base64 and a JWT-shaped string as JWT; encoding the Base64 output again gives UTJGc1kxZ2dNakF5Tmc9PQ== .
Bytes, not characters Hex, binary, octal and decimal conversions work on UTF-8 bytes, so a non-ASCII character becomes several values: café is 63 61 66 C3 A9 , while its last character is the single code point U+00E9. Standard and URL-safe Base64 differ only in the alphabet (+ and / become - and _) and in padding.
Limits
Not encryption. Every operation is reversible encoding or substitution; nothing here protects a secret.
Detection is a guess. The chip suggests the most likely format, and ambiguous strings can be misread — check the decoded output. What it does not do. It does not hash, validate JSON or test regular expressions; those live in Hashing and JSON . Morse covers letters, digits and punctuation, not arbitrary Unicode.
Double encoding is the classic trap Encoding an already-encoded string returns a valid-looking result: Base64 of CalcX 2026 is Q2FsY1ggMjAyNg== , and encoding that again yields UTJGc1kxZ2dNakF5Tmc9PQ== . Both decode without error, so a payload that "does not decode to the expected text" is often double-encoded. The URL component and full-URL operations also differ: component encoding escapes = and &, while full-URL encoding keeps the URL structure and escapes only spaces and unsafe characters.
Where it is used Debugging an API payload Paste a Base64URL blob, accept the suggested decode, and chain the result into a second operation when the payload holds another layer.
Escaping text for code Use the JSON, CSV, regex, shell or SQL escape operations to quote a string for the language you are about to paste it into.
Privacy All conversions run inside your browser; the input, output and any chained value are never uploaded or stored.
References
IETF, RFC 4648: The Base16, Base32, and Base64 Data Encodings , rfc-editor.org (访问日期:2026-10-07)— Base64 alphabets and padding.
IETF, RFC 3986: URI Generic Syntax , rfc-editor.org (访问日期:2026-10-07)— percent-encoding rules.
WHATWG, HTML named character references , html.spec.whatwg.org (访问日期:2026-10-07)— entity names.
Wikipedia, Morse code , en.wikipedia.org (访问日期:2026-10-07)— the Morse alphabet.
Calculators in this hub
Hand-picked tools, one click away. The mini versions compute live and carry your values into the full calculator.
Sources & review
Reviewed by CalcX Editorial Team
Updated 2026-10-07