Encoding & Ciphers
Encoding converts data between representations so it survives transport — it is not security. Base64 makes binary safe for text channels, percent-encoding makes a value safe inside a URL, HTML entities make characters safe in markup, and ciphers like Caesar or Morse are historical encodings with no confidentiality left.
Base64, binary and number systems
Base64 is the right answer when binary data has to travel through something that only accepts text (JSON, an email body, a data URI). The image variant does it for whole files with a preview. Use the number-base converter when you are moving between binary, octal, decimal and hex.
Make text safe for URLs and markup
Percent-encoding is what you need when a value contains characters that would break a query string; the URL parser is the reverse view — it takes a URL apart so you can see the decoded parameters. HTML entity encoding is for text being embedded into markup.
Ciphers, codes and numerals
These are for learning, puzzles and teaching — not for protecting anything. Caesar is a fixed letter shift, Morse is a signalling code, and Roman numerals are a numeral system rather than an encoding; the converters handle all three, with the Morse tool offering audio playback.
Guides on this topic
Where this fits
These tools live under Text Tools in the main directory, and every tool page links back to this hub so you can see how it relates to the others.