glunty 17 tools in this category. Each runs in your browser.
Working with text formats means moving values between systems that have different rules about what is safe to include. Encoders translate values into safe forms; decoders reverse the translation; validators check that an input matches a format rules without modifying it.
The tools below cover the encoding systems that matter most in everyday work: URL percent-encoding for query parameters, Base64 for binary-in-text transport, HTML entities for safe markup, JSON for structured data, JWT for signed tokens, IP and CIDR for network identifiers, Kubernetes manifests for cluster config, TOML for hand-written config files, and ROT13 (which is not encryption but is the historical convention for spoiler hiding on text-only forums).
The common thread: each one runs entirely in your browser. Nothing is uploaded, nothing is logged, nothing is sent to a server you do not control. Even cryptography-adjacent tools (hashes, JWT decoding, ROT13) keep your input on your machine. The result: you can paste sensitive values, reload the page, or close the tab and your input is gone forever.
Pick a tool below to start. If you are decoding a value you copied from somewhere, the decoder is usually the right starting point. If you are preparing a value to put somewhere, the encoder is. When a tool flags an error, the message tells you which character or which structure violated the format rules.
The ideas behind these tools, in plain English.
Encoding reversibly reshapes data into another format using a public, keyless scheme, while encryption scrambles data so only a key can recover it.
Base64 or URL encoding provides zero secrecy, so treating encoded data as protected is a common and dangerous mistake.
Percent-encoding replaces reserved or unsafe characters in a URL with a percent sign followed by their hexadecimal byte value, such as a space becoming %20.
Without it, characters like &, ?, and spaces break query strings and paths, corrupting links and API requests.
Base64 maps arbitrary binary data onto 64 printable ASCII characters, expanding size by roughly one third.
It lets you carry images, keys, or binary blobs through text-only channels like JSON, email, and data URIs without corruption.
A character set assigns numbers to characters, and an encoding like UTF-8 defines how those numbers become bytes, with Unicode being the universal character set.
Mismatched encodings produce mojibake and broken text, so knowing that a string is really UTF-8 bytes prevents corruption across systems.
Percent-encode strings for URLs.
Standard or URL-safe base64.
Named or numeric entities.
Format, validate, minify JSON.
Decode JWTs and explain standard claims.
Validate addresses and compute CIDR subnets.
Quick structural pre-check for k8s YAML.
Validate and reformat TOML.
Adjustable shift cipher (toy, not security).
Test a regex live with match highlighting and capture groups.
Break a URL into parts and decode its query-string parameters.
Beautify, minify, and check well-formedness.
Format SQL with dialect, keyword case, and indent options.
Two-way: text to binary and binary to text, UTF-8 correct.
Strip HTML tags to clean plain text; keeps line breaks, decodes entities.
Text to Morse and Morse to text, International code, one-click copy.
Check the Luhn checksum, detect the card brand, and verify length.