Developer encoding utility

Base64 encoder and decoder

Base64 encoding converts binary data into ASCII text so it can travel safely through systems that handle text only — email attachments, JSON payloads, data URIs, and HTTP headers all rely on it.

Encode and decode Base64

Base64 processing runs locally in your browser tab.

Plain text to Base64

Why this tool works well

  • UTF-8-safe conversion for modern text content.
  • Fast toggle between encode and decode modes.
  • All processing runs in your browser tab.
  • When embedding small images or icons directly into CSS or HTML as data URIs, use the encoder to convert the binary to Base64 first. This eliminates one HTTP request per asset.
  • JWT tokens use Base64URL encoding for their header and payload segments. Decode the middle segment of any JWT here to inspect the claims without using a separate tool.

Use cases

API payload checks

Inspect encoded values in test payloads quickly.

Auth workflows

Decode segments used in token diagnostics.

Snippet handling

Convert small text blobs for transport-safe usage.

Practical examples

Encode sample

Input: plain-text

Output: cGxhaW4tdGV4dA==

Decode sample

Input: SGVsbG8gd29ybGQ=

Output: Hello world

Suggested workflow

FAQ

Is Base64 encryption?

No, Base64 is an encoding format, not encryption.

Is my input uploaded?

No, encoding and decoding happen locally in your browser.

What is the difference between Base64 and Base64URL?

Base64URL replaces + with - and / with _ to make the output safe for URLs and filenames. Standard Base64 uses + and / which can break URL parsing. Both variants are supported.

Can I encode binary files with this tool?

This tool works with text input. For binary files, you would need to read the file as bytes first. For text content, strings, and small data URIs it works directly.

Related tools

Continue with closely related tools for faster multi-step workflows.

Recommended next actions

High-utility picks across categories based on current intent.