Compare cipher mechanics with encoding and hashing
Run a disposable historical-cipher example, inspect the same XOR bytes as Hex or Base64, and compare the reversible result with a one-way hash without calling any of them modern encryption.
Encoding tools help convert text into transport-safe formats, decode stored values, and generate hashes for checksums or fingerprints without sending data to a server.
Compare six bounded classical and toy cipher methods locally with strict keys, exact outputs, and clear security limits.
Open toolStrictly encode UTF-8 and decode Base64, Base64URL, data URIs, and binary byte output locally.
Open toolEncode or decode exact URL components, full URLs, and form values locally.
Open toolHash UTF-8 text or exact file bytes and compare a full checksum locally.
Open toolParse bounded HTTP header blocks locally with default secret masking and protocol diagnostics.
Open toolInspect BOM, strict UTF-8, Unicode structure, ASCII compatibility, and binary clues from local file bytes.
Open toolEncode or decode 17 explicit text representations and convert verified raster images to Base64 locally.
Open toolConvert one IDN between Unicode and Punycode with strict validation and label review.
Open toolNormalize Unicode with code-point evidence and explicit compatibility-loss warnings.
Open toolWorkflow guides
Use these guides when you need a concrete workflow before opening a tool.
Isolate, redact, format, and validate an API JSON body without rewriting number text or hiding duplicate keys, then check its schema separately.
Read guideLearn how to inspect JWT headers and payload claims without treating decoded tokens as verified or sharing secrets by accident.
Read guideIdentify Base64 versus Base64URL, decode one API field strictly, distinguish UTF-8 text from binary, and redact the result before sharing it.
Read guideConvert spreadsheet CSV exports to JSON without losing quoted cells, multiline text, leading-zero IDs, duplicate headers, or empty values.
Read guideTool selection guide
| Tool | Best for |
|---|---|
| Cipher Learning Workbench | Compare Six Historical Methods | Use it to compare historical reversible methods and strict XOR byte examples for education, never to protect secrets. |
| Base64 Encoder and Decoder | UTF-8, Base64URL, and Data URIs | Use it for text-safe payloads in JSON, APIs, Data URIs, and debugging. |
| URL Encoder and Decoder | Exact Percent Encoding and Plus Rules | Use it for query parameters, nested redirect URLs, and percent-encoded UTF-8 text. |
| Hash Generator and File Checksum | SHA-256 and MD5 | Use it for checksums, content fingerprints, and non-password integrity checks. |
| Detect Text File Encoding from Byte Evidence | Use it before importing CSVs, logs, or exports that may have mojibake or unknown encoding. |
| HTTP Header Parser for Request and Response Debugging | Use it with URL decoding and token inspection when copied API responses need local debugging. |
Recommended workflows
Choose the encoding task first, then move through the tools that usually appear together in API, URL, and integrity checks.
Run a disposable historical-cipher example, inspect the same XOR bytes as Hex or Base64, and compare the reversible result with a one-way hash without calling any of them modern encryption.
Inspect Base64 values, URL-encoded values, and copied token payloads without sending pasted data to a remote decoder.
Parse copied response headers, decode encoded URL values, then hash payloads when an API log or CDN trace needs a local integrity check.
Encode only the values that need escaping, then turn the final URL into a QR code when the link needs to be shared.
Detect the source encoding, validate the converted JSON when needed, then convert CSV and JSON samples before importing files.
Generate hashes, compare copied payloads, and create UUIDs for local test records or fixtures.
FAQ
Start with Base64 Encoder and Decoder for copied tokens, JSON fields, and Data URI text. Start with URL Encoder and Decoder for query strings, redirect URLs, and percent-encoded UTF-8 values.
No. Encoding changes how data is represented so it can move through URLs, JSON, HTML, or APIs. It is reversible and should not be used to protect passwords, secrets, or private tokens.
Use the hash generator when you need a checksum, fingerprint, or local integrity check after decoding or normalizing content. It is useful for comparing copied payloads, files, logs, and API examples.
The listed encoding workflows are intended to run in your browser, so pasted values can be decoded, encoded, or hashed locally. Avoid pasting production secrets unless you are allowed to inspect them.
No. Atbash, Caesar, ROT13, ROT47, Vigenere, and repeating-key XOR are included to teach historical substitution, rotation, and byte mechanics. They provide no modern authenticated confidentiality and must not protect real data.