ℹ️ About Bubble Babble Encoding
Bubble Babble Encoding is a reversible binary-to-text encoding that turns bytes into pronounceable pseudo-words. It was designed by Antti Huima for human comparison of security fingerprints, where a long hexadecimal digest is hard to read aloud, remember, or copy without mistakes.
Fingerprint and readability use cases:
- Compare SSH host key or public key fingerprints in a form that is easier to read aloud than hex.
- Share a digest over a phone, chat, ticket, radio, or incident bridge where transcription errors matter.
- Display hashes, certificate thumbprints, signatures, or other random-looking byte strings for manual verification.
- Turn binary, hexadecimal, or text input into a compact pronounceable string for documentation or test vectors.
Algorithm details: Bubble Babble wraps output in literal x delimiters and uses the vowels
a e i o u y plus the consonants b c d f g h k l m n p r s t v z x.
Each full two-byte tuple becomes five letters arranged around alternating vowel/consonant positions, with hyphens between
word groups for scanning. A rolling modulo-36 checksum changes the vowel choices, so many mistyped encodings can be rejected
during decoding without making the encoded string longer.
Examples: Empty input encodes as xexax, Pineapple encodes as
xigak-nyryk-humil-bosek-sonax, and 1234567890 encodes as
xesef-disof-gytuf-katof-movif-baxux. Hex input 50696E656170706C65 is the same byte sequence
as Pineapple, so it produces the same Bubble Babble text.
Limitations: Bubble Babble is an encoding, not encryption, signing, hashing, or authentication. It does not hide the original data and should not be used as a secret format. The checksum helps catch some transcription errors, but it is not a cryptographic integrity check; verify important data with the original hash, signature, certificate, or SSH key fingerprint too.
Privacy note: Treat fingerprints, keys, tokens, and sample payloads as sensitive operational data. This page is intended for local conversion in your browser UI, but avoid pasting private keys, credentials, or production secrets into any web tool unless you are certain how that specific workflow processes the input.
Sources:
The Bubble Babble Binary Data Encoding draft
describes the original algorithm and test vectors, and the
OpenBSD ssh-keygen manual
documents the -B Bubble Babble fingerprint option.
API Usage Example:
POST /api/tools/encoding-decoding/bubble-babble
Content-Type: application/json
{
"text": "Pineapple",
"operation": "encode",
"format": "text"
}