Base100 encodes text by mapping every UTF-8 byte 0–255 to exactly one code point from U+1F3F7 through U+1F4F6, and on Android this mapping runs entirely inside the phone's browser tab — no APK, no Play Store install, no terminal emulator required. Because the Base100 Encoder / Decoder operates locally in JavaScript, your text never leaves the device: the conversion happens in the same Chrome, Firefox, Edge, or Samsung Internet tab where you opened the page. That browser-based approach is also why Base100 works the same way on a Samsung Galaxy, a Pixel, or a cheaper Android tablet running an older OS, as long as the browser supports modern Unicode and UTF-8. The 256 symbols live in the Supplementary Multilingual Plane just above U+1F3F7, which means every Android keyboard that supports emoji can already render the output stream in apps, notes, and chat windows. This guide walks through the exact mobile workflow for encoding and decoding Base100 on Android, what can go wrong when a keyboard or chat app injects a variation selector, and where Base100 stops being the right tool.
Why Android Is a Natural Fit for Base100
The Base100 mapping was introduced by Adam Niederer and represents each input byte with a single emoji-range Unicode symbol. That choice has practical consequences on a mobile device. Android keyboards are already tuned to render emoji, so the output stream looks visually consistent in messaging apps, Notes, Gmail drafts, and clipboard managers — provided the destination app also targets modern Unicode. Because the entire conversion happens in the browser tab via JavaScript, the same Base100 Encoder / Decoder page works on Android 9, 10, 11, 12, 13, 14, and 15, on Chrome and on Firefox, and on tablets as well as phones. No offline binary, no Termux session, and no rooting are required.
Running the mapping locally also means the input never travels to a server. For people who want to share a short binary blob — a Wi-Fi password hint, a short token, a CTF challenge flag — through a chat app on Android, this is the practical sweet spot. The page accepts UTF-8 text, converts it byte by byte using the rule code_point = U+1F3F7 + byte, and gives you a stream you can paste into WhatsApp, Signal, Telegram, Discord, or any other app that handles emoji.
How to Base100 Encode Text on Android
Encoding on a phone follows the same three steps you would use on a desktop. The mobile part is mostly about what happens to the symbols after you copy them, not how the tool itself works.
- Open the Base100 Encoder / Decoder in your Android browser (Chrome, Firefox, or Samsung Internet all work) and tap Text to Base100.
- Type or paste your UTF-8 text into the input box. For multi-line text, paste it as a single block — the encoder treats every byte the same way and does not insert any separators.
- Tap the encode action and wait for the symbol stream to appear. Each UTF-8 byte in the input produces exactly one symbol, so plain ASCII text yields one emoji per character and accented or CJK text yields more symbols per visible character.
- Long-press the output and choose Copy. Avoid tapping Share directly to a chat app at this stage, because some share targets silently add a variation selector (U+FE0F) to emoji-looking code points, and strict decoding will then reject the stream.
- Paste the stream into your target Android app — Notes, Gmail, a chat thread, a file — and send or save it as usual.
How to Decode Base100 Symbols Back to Text on Android
Decoding reverses the same formula and is just as quick. Open the Base100 to text mode on the Base100 Encoder / Decoder page, paste the symbol stream you received, and run the decode action. The page walks every Unicode code point in the paste, checks that each one falls strictly inside U+1F3F7 through U+1F4F6, subtracts U+1F3F7 from each to recover a byte value, and runs a fatal UTF-8 decoder over the resulting byte sequence. If the input contains a variation selector, a space, a line break, a regular emoji from outside the range, or any byte sequence that is not valid UTF-8, the tool reports an error rather than silently inserting replacement characters. That strict behavior is what you want on a phone, where one stray invisible character is enough to corrupt the round trip.
For example, the two-letter string Hi encodes to the byte sequence 0x48 0x69. Adding U+1F3F7 to each byte produces the symbols U+1F43F and U+1F460. Pasting those two symbols back into the decoder must yield the original Hi, with no variation selector and no trailing newline. If the result looks wrong on the first try, paste into a plain Notes document first to strip formatting, then copy again from Notes into the decoder.
What Can Break the Stream on Android
Three mobile-specific failure modes show up over and over. The first is the variation selector: many Android keyboards and chat clients automatically attach U+FE0F to emoji-looking code points, which turns a valid Base100 symbol into a two-code-point sequence that the strict decoder rejects. The second is invisible whitespace: chat apps occasionally inject zero-width spaces, non-breaking spaces, or paragraph marks when copying long emoji sequences, especially if the stream wraps in the input field. The third is substitution: some apps or older browsers cannot render code points in the U+1F400–U+1F4F0 range and replace them with placeholder boxes or a "missing glyph" indicator before the copy completes. In every case the visual result looks close to correct, but the underlying code points have changed and strict decoding fails. The fix is always the same — preserve the exact code points, ideally by copying through a plain text editor on the phone rather than through a styled chat composer.
The page guards against these problems at the boundary by reading symbols by Unicode code point rather than UTF-16 code unit, using fatal UTF-8 validation, and rejecting spaces, line breaks, variation selectors, and any emoji outside the 256-symbol range. Empty input is rejected too, so an accidental paste of an empty selection never produces a confusing "success" on the small mobile screen.
Base100 and Other Encodings on Mobile
Base100 is one of several byte-to-symbol encodings you can run in an Android browser. The table below compares them on the criteria that matter on a phone: whether the symbol set renders in any messaging app, how compact the result is, and how human-readable the output looks. Exact size ratios depend on the input text, so the table describes direction and rough magnitude rather than precise ratios.
| Encoding | Symbol set | Renders in Android chat apps | Looks readable to humans | Built-in error detection |
|---|---|---|---|---|
| Base100 | U+1F3F7–U+1F4F6 (emoji-range symbols) | Usually, on modern Android | No — one emoji stream | No |
| Base64 | A–Z, a–z, 0–9, +, /, = | Yes, plain ASCII | No | No |
| Hexadecimal | 0–9, A–F | Yes, plain ASCII | Partly — two chars per byte | No |
| Base58 | 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz | Yes, plain ASCII | No | Optional checksum |
| Base32 | A–Z, 2–7, = | Yes, plain ASCII | No | No |
If your destination app on Android strips emoji or substitutes code points outside the BMP, fall back to Base64 Encode / Decode, Base58 Encode / Decode, or Hex to Text Converter instead. Those three produce plain ASCII output that survives every messaging client and every clipboard manager on Android.
Limits and What Base100 Is Not For
The page caps either direction at 500,000 bytes or symbols so that an accidental paste of a giant log file cannot freeze your phone's browser. Past that point the input is refused with a clear error, never silently truncated. The encoder never adds padding, length markers, checksums, or framing characters, and the decoder never normalizes or silently substitutes characters. For UTF-8 behavior the tool follows the WHATWG Encoding Standard used by every modern browser, so a sequence that decodes on Android Chrome will also decode on desktop Chrome, Firefox, or Safari without any mobile-specific quirks.
Base100 is an encoding, not encryption. Anyone with the mapping — and the mapping is documented in Adam Niederer's original Base100 project — can recover the original text. There is no built-in checksum, so a single accidentally changed symbol produces a different byte but still decodes without warning. Do not use Base100 to protect passwords, personal data, tokens, private keys, or any other confidential material on Android or anywhere else. For those cases, use reviewed encryption with authenticated formats such as AES-GCM, or a password manager, not a reversible emoji mapping. For a quick, on-device way to encode or decode any UTF-8 string on Android, the Base100 Encoder / Decoder stays in your browser tab and never uploads your input.
Related reading: BCC Checksum Example: A Step-by-Step XOR-8 Walkthrough.
Related reading: Gzcompress Online on Android: A Mobile Browser Guide.