—

Standard Base64 (RFC 4648). Used for embedding binary data in text, email attachments, and data URIs.

—

URL-safe Base64 — replaces + with -, / with _, strips = padding. Used in JWTs and OAuth tokens.

—

RFC 4648 Base32 — 32-character alphabet (A-Z, 2-7). Case-insensitive and safe for case-insensitive systems.

—

Percent-encoding for URL query parameters. Encodes all characters except unreserved ones (-_.~).

—

Escapes HTML special characters (&, <, >, ", ') so they render as text rather than markup.

—

Each UTF-8 byte as a two-digit hex number separated by spaces. Standard byte-level hex dump.

—

Each UTF-8 byte as 8 binary digits separated by spaces. Useful for bit-level inspection.

—

Each UTF-8 byte as a decimal number (0–255) separated by spaces.

—

Non-ASCII characters as \uXXXX JS escape sequences. ASCII passes through unchanged.

—

Rotates each letter 13 positions in the alphabet. Self-inverse: encoding and decoding are identical.

—

160-bit (40 hex char) one-way hash. Deprecated for security use — collisions are known. Useful for checksums.

—

256-bit (64 hex char) one-way cryptographic hash. Standard for data integrity verification.

—

512-bit (128 hex char) one-way hash. Stronger than SHA-256, preferred for password hashing pipelines.