Skip to main content
Encoders

Base64 Text Encoder

Encode browser text as UTF-8 bytes and RFC 4648 standard Base64, with exact Unicode handling, byte count, copy, text-file import, and download. Ideal for developers preparing payloads for APIs, data URIs, email attachments, and authentication headers. Handles full Unicode range with transparent byte counting.

Base64 tools

In brief

Turn text into standard padded Base64 using UTF-8 before RFC 4648 encoding; verify Unicode with a known vector and remember that encoding is reversible, not encryption.

What this tool supports

  • UTF-8 encoding through TextEncoder before Base64 conversion, so non-ASCII text is handled as bytes rather than truncated code units.
  • RFC 4648 standard Base64 alphabet with +, /, and = padding; this workspace does not emit the Base64URL alphabet.
  • Typed or pasted text, the built-in Unicode sample, and text loaded from a user-selected local file.
  • Immediate output, source UTF-8 byte count, clipboard copy, and a base64.txt download.
  • Exact round-trip verification with Base64 Decoder for text that is valid UTF-8.

How to use Base64 Text Encoder

Complete a verifiable Base64 Text Encoder workflow in this browser.

  1. 1

    Step 1

    Enter the source text

    Type, paste, or import a text file. The editor treats the value as browser text and encodes it as UTF-8.

  2. 2

    Step 2

    Check the intended variant

    Use this tool only when the receiver expects standard padded Base64, not Base64URL or hexadecimal.

  3. 3

    Step 3

    Review the live output

    The right pane updates from the current input and reports how many UTF-8 source bytes were encoded.

  4. 4

    Step 4

    Verify sensitive integrations

    Decode the result back to text and compare the exact Unicode code points before placing it in an API or configuration.

  5. 5

    Step 5

    Export deliberately

    Copy the reviewed string or download base64.txt; do not mistake the output for protected data.

Common mistakes

Treating Base64 as encryption

Consequence: Anyone who receives the string can reverse it without a key.

Fix: Use encryption or an authenticated protocol for confidentiality; use Base64 only as a binary-to-text representation.

Sending standard Base64 where Base64URL is required

Consequence: Characters +, /, and = may be rejected in URL-safe token fields.

Fix: Confirm the receiver’s alphabet and padding rules; this encoder emits RFC 4648 standard Base64 only.

Comparing JavaScript character count with encoded byte count

Consequence: Emoji and many non-Latin characters occupy multiple UTF-8 bytes, so expected output lengths do not match character counts.

Fix: Verify the displayed UTF-8 byte count and test with a known Unicode vector.

Best practices

  • Use the canonical vector “Hello ✓” → “SGVsbG8g4pyT” when checking UTF-8 behavior.
  • Record whether an integration expects standard Base64 or Base64URL, including whether padding is required.
  • Keep the unencoded source until the receiving system has accepted and decoded the value.
  • Do not place secrets in Base64 merely to make them look opaque.

Connected workflows

Encode and round-trip API fixture

Base64 Text EncoderBase64 UTF-8 Decoder

Encode the exact UTF-8 fixture, pass the Base64 string to Base64 Decoder, and compare the decoded text before committing the fixture.

  1. Enter the source text
  2. Copy the Base64 result
  3. Open Base64 Decoder
  4. Decode and compare every character

Choose text or file encoding

Base64 Text EncoderFile to Base64 Data URL Converter

Use this text encoder for Unicode strings; hand arbitrary binary input to Base64 File Converter so byte values are not changed by text decoding.

  1. Identify whether the input is text or binary
  2. Use the matching encoder
  3. Verify the receiver’s alphabet and MIME expectations

Browser limitations

  • The whole input, UTF-8 byte array, and output string reside in tab memory; very large text files can stall or exhaust a mobile tab.
  • Clipboard read/write commonly requires HTTPS, localhost, permission, or a direct user gesture; manual paste and selection remain available.
  • The text-file import path decodes through FileReader.readAsText and is not appropriate for arbitrary binary bytes.

Authoritative resources

RFC 4648: Base-N EncodingsPublisher: RFC Editor · Reviewed: 2026-07-26Encoding Standard: UTF-8Publisher: WHATWG · Reviewed: 2026-07-26MDN: TextEncoderPublisher: MDN Web Docs · Reviewed: 2026-07-26

Concrete examples

Input
Hello ✓
Result
SGVsbG8g4pyT

The check mark is first encoded as UTF-8 bytes E2 9C 93; standard RFC 4648 Base64 for the complete byte sequence is exactly SGVsbG8g4pyT.

Frequently asked questions

Why does an emoji make the Base64 string longer than expected?

The encoder works on UTF-8 bytes. An emoji normally requires four bytes even though JavaScript may display it as one grapheme.

Does this output use Base64URL?

No. It uses the standard RFC 4648 alphabet and keeps = padding.

Can I encode a PNG by importing it here?

No. This workspace imports files as text. Use Base64 File Converter to preserve arbitrary file bytes in a data URL.

Can Base64 hide an API key?

No. Base64 is reversible encoding and supplies neither secrecy nor integrity.

How can I prove the Unicode result is correct?

Decode the output with Base64 Decoder and compare the resulting text, or compare against the documented “Hello ✓” vector.

Does the text leave the browser?

No tool payload is sent to an application server; only an explicit browser clipboard, file, or download action touches the corresponding local capability.

Privacy and offline behavior

Text is converted by TextEncoder, btoa, and browser memory on this device. TetraBrain Desk does not upload the source or result. Offline use works after the static application assets have been cached; clipboard and local-file selection still follow browser security rules.

Related tools