Base100 encoding converts each UTF-8 byte into one Unicode code point from U+1F3F7 through U+1F4F6 using the formula code point = U+1F3F7 + byte. The Base100 Encoder / Decoder applies that mapping in the browser: choose a conversion direction, enter the input, run the conversion, and copy the result without creating an account or uploading the text. This is the direct solution for a free, no-sign-up Base100 encoding task. ASCII text usually becomes one emoji-range symbol per character because each ASCII character occupies one UTF-8 byte. An accented letter, CJK character, or input emoji can require several bytes, so the output may contain several symbols. Every byte is mapped exactly; Base100 adds no padding, delimiter, checksum, compression, or length marker. To keep the output portable, copy the exact symbol stream and do not add spaces, line breaks, punctuation, or variation selectors. The decoder accepts only code points in the original 256-symbol range and then validates the recovered bytes as UTF-8. It rejects invalid symbols and malformed UTF-8 instead of silently adding replacement characters. Either direction is limited to 500,000 bytes or symbols, and empty input is rejected. The same byte formula makes the format reversible, but it does not provide secrecy, authentication, or tamper detection.
Choose the conversion direction
The correct direction depends entirely on the material you already have. Use the Base100 Encoder / Decoder when you want to turn UTF-8 text into a stream of emoji-range symbols. Use its decoder when you possess an original, unchanged Base100 stream and need to recover the text. The tool does not translate words into visual emoji meanings; it converts the underlying UTF-8 bytes according to a fixed code-point formula.
| Direction | Input | Output | Validation |
|---|---|---|---|
| Text to Base100 | UTF-8 text | One mapped symbol per input byte | Empty input is rejected |
| Base100 to text | Valid, unmodified Base100 symbols | Text recovered from the bytes | Invalid symbols and invalid UTF-8 sequences are rejected |
For encoding, select Text to Base100 only when your starting value is text. For decoding, select Base100 to text only when every pasted character is an allowed Base100 code point. Selecting the wrong direction will not reinterpret the input semantically; it applies the opposite byte conversion to the material you supplied.
Encode text without creating an account
The immediate online workflow consists of choosing the encoder, supplying UTF-8 text, and preserving the generated symbols exactly as produced.
- Open the Base100 tool. No registration or account creation is required for this browser-based conversion.
- Choose Text to Base100. This tells the page that every input byte should receive one Base100 code point.
- Enter UTF-8 text and run the encoder. The tool converts the string to UTF-8 and maps each resulting byte from 0 through 255.
- Copy the result. Preserve the exact symbol stream without inserting spaces, line breaks, separators, punctuation, or emoji variation selectors.
- Use the copied stream as Base100 data. Do not reformat it before decoding or sending it to another system.
One UTF-8 byte always produces one symbol, but one visible character does not always equal one byte. Ordinary ASCII text normally has one byte per character, so its symbol count usually matches its character count. Accented letters, CJK characters, and emoji often need multiple UTF-8 bytes and therefore expand into multiple Base100 symbols. The output is an exact byte representation, not a human-language emoji translation.
Base100 has no padding, checksum, length marker, compression, or delimiter to copy. A plain stream is therefore easier to handle correctly: copy the generated result without trying to improve its formatting. Keep the complete input within 500,000 UTF-8 bytes, and do not expect output to be silently shortened if the input is too large.
See how bytes become Base100 symbols
For an input byte represented by b, the encoder calculates U+1F3F7 + b. The mapping occupies the exact inclusive range from U+1F3F7 through U+1F4F6. Byte zero maps to the first code point, U+1F3F7, while byte 255 maps to the final code point, U+1F4F6.
As one numeric example, byte 1 follows the same rule: U+1F3F7 + 1 = U+1F3F8. The result is the code point assigned to byte 1. It is not necessary to identify a particular visual glyph because emoji presentation varies across browsers, fonts, operating systems, and messaging applications.
The mapping follows Adam Niederer’s Base100 project, while the text boundary follows the UTF-8 behavior defined by the WHATWG Encoding Standard. These two roles are separate: the first supplies the byte formula, and the second defines how the browser converts the original text to and from UTF-8.
| Input type | UTF-8 behavior | Expected Base100 relationship |
|---|---|---|
| ASCII character | Uses one UTF-8 byte | Produces one Base100 symbol |
| Accented character | May use more than one byte | Usually produces more than one symbol |
| CJK character or emoji | Usually uses several bytes | Produces a correspondingly longer symbol stream |
As a result, the number of Base100 symbols measures encoded bytes. It does not measure user-perceived characters, grapheme clusters, words, or the original JavaScript string length. This distinction matters when checking an output length or estimating how much a multilingual message will expand.
A code point’s appearance is not part of the conversion contract. Some mapped code points may be shown as colorful images, monochrome glyphs, boxes, or unexpected pictographs. That visual variation does not alter the mathematical mapping inside a conforming string. However, copying through software that substitutes, strips, or decorates code points can make the received data different from the original stream.
Decode a copied symbol stream
Strict decoding reverses the encoder’s byte map, but only when the pasted stream remains within the exact Base100 range and those bytes form valid UTF-8.
- Choose Base100 to text. This selects the reverse conversion direction.
- Paste the valid stream. Preserve every code point exactly as copied; do not add separators or formatting.
- Run the decoder. It reads Unicode code points rather than UTF-16 code units and subtracts U+1F3F7 from each allowed symbol to recover its byte value.
- Copy the recovered text. Use the result only after the decoder completes successfully.
Every decoded symbol must fall from U+1F3F7 through U+1F4F6. Spaces, line breaks, punctuation, variation selectors, and emoji outside that range are rejected rather than ignored. After collecting the bytes, the tool applies fatal UTF-8 validation. If the resulting sequence is malformed, it reports an error instead of inserting a replacement character and presenting the output as exact.
A visually similar paste can still fail decoding when another editor, chat application, keyboard, or normalization pipeline has inserted a variation selector, altered a code point, or added framing characters. The original Base100 format has no ignored separators. Keeping the symbol stream unchanged is especially important across applications with different emoji rendering behavior.
Base100 also has no checksum. A changed symbol inside the allowed range changes a byte and may decode to different but valid text, yet the decoder has no built-in way to prove that the alteration was accidental. Preserve the exact code points whenever interoperability or bytewise accuracy matters.
Work within the limit and choose the right use
The page limits either direction to 500,000 bytes or symbols to reduce the risk of an accidental huge paste freezing the browser. When encoding, count the UTF-8 bytes in the original text. When decoding, count the Base100 symbols in the pasted stream. A Unicode character can produce several bytes and several symbols, so estimating from visible character count is unreliable. Output is never silently truncated; keep the complete input within the stated boundary rather than depending on automatic shortening.
Base100 is useful when you specifically need the distinctive emoji-range byte representation or want to test a Base100 workflow. It is not encryption, hashing, signing, authentication, compression, steganography, or a secret emoji language. Anyone who knows the mapping can recover the text. Do not use it to protect passwords, personal data, private keys, tokens, or confidential messages; use reviewed encryption and authenticated formats when secrecy or tamper detection is required.
If the destination requires ASCII-only transport, Base64, base64url, Base32, Base58, or hexadecimal is usually more compatible. Choose Base100 when preserving the original symbol mapping itself is the requirement. For a free, no-sign-up conversion, open the page, select the correct direction, run the conversion, and copy the unmodified result.
If you're weighing options, Gzcompress Online Free, No Sign Up: In Your Browser covers this in detail.