Text tool

Base64 Encoder and Decoder

Convert regular text to Base64 or decode Base64 strings while working with API tokens, test fixtures, and encoded payloads.

Encode and decode text

Base64 shows up in API examples, data URLs, authorization headers, test fixtures, and small payloads. Encode readable text or decode Base64 back into text without uploading the input.

The converter uses TextEncoder and TextDecoder, so Unicode text works better than older ASCII-only snippets.

Common Base64 tasks

  • Encode short test strings before adding them to sample API payloads.
  • Decode Base64 values copied from logs, examples, or fixtures.
  • Check whether an encoded value is text before using it in documentation.

Best for

  • API headers, JSON examples, and webhook tests.
  • Copied values from logs, fixtures, and docs.
  • Short development notes where the original text still needs to be readable.

Base64 input and output examples

  • Hello world becomes SGVsbG8gd29ybGQ=.
  • NimbleTools becomes TmltYmxlVG9vbHM=.
  • Decode Base64 before copying values into docs so readers can inspect the original text.

Related encoding tools

Use the URL Encoder Decoder for query strings and percent-encoded values, the JSON Formatter for payloads that contain encoded fields, and the Hash Generator for one-way text digests.

FAQ

Is Base64 encryption?

No. Base64 is an encoding format, not a security feature. Anyone can decode it.

Does it support Unicode text?

Yes. The tool uses TextEncoder and TextDecoder for non-ASCII characters.

Why does decoding fail?

The input may contain invalid Base64 characters, missing padding, or bytes that cannot be decoded as text.

Can I decode API tokens with this page?

You can decode Base64 text, but do not paste private production secrets into any tool unless you are comfortable handling them on that device.

Should Base64 be used for passwords?

No. Base64 is reversible and should not be used to protect passwords or sensitive data.