Developer Tools

Base64 Encode & Decode

Encode and decode Base64 online for text, files, API payloads, JWT segments, configuration values, and developer workflows.

Base64 encode and decode online

Use this tool to encode text to Base64, decode Base64 back to readable text, convert Base64URL values, and encode local files as text output.

Base64 encoder online

Use the encoder when you need to convert plain text, UTF-8 strings, configuration values, or local file bytes into a Base64 string.

The encoder supports standard Base64 and Base64URL output, which is useful for URLs, filenames, JWT-related values, and systems that do not accept + or / characters.

Base64 decoder online

Use the decoder when you need to convert a Base64 string back to readable UTF-8 text or download decoded bytes as a file.

The decoder accepts standard Base64 and Base64URL input and ignores ordinary whitespace or line breaks so copied values are easier to inspect.

What is Base64?

Base64 converts binary data into printable ASCII characters so the value can travel through text-based systems such as JSON, headers, configuration files, and command-line workflows.

Base64 is encoding, not encryption. Anyone with the encoded value can decode it unless the original content was encrypted separately.

How to encode text to Base64

Enter text such as Hello, choose Base64, and click Encode to convert the text into SGVsbG8=.

UTF-8 text is handled correctly, including non-English characters and emoji.

How to decode Base64

Paste a value such as SGVsbG8=, choose Decode, and the tool converts the Base64 value back to Hello when the bytes are valid UTF-8 text.

Whitespace and line breaks are ignored during decoding so copied multiline values are easier to inspect.

Base64 vs Base64URL

Standard Base64 uses + and / characters and often ends with = padding.

Base64URL replaces + with - and / with _, and it commonly removes trailing = padding. JWT tokens use Base64URL for their header and payload segments.

Base64 and JWT tokens

JWT header and payload segments are Base64URL encoded JSON. Use the JWT Debugger when you need token-specific parsing, claims inspection, expiry checks, or signature verification.

This Base64 tool is useful when you want to inspect or transform a standalone Base64 or Base64URL value.

Why does Base64 end with =?

The = character is padding. It helps represent byte lengths that do not divide evenly into Base64 groups.

Base64URL values often omit padding, so this decoder restores the required padding internally before decoding.

Privacy

Base64 conversion runs in your browser with native client-side APIs. Text and files are not sent to CloudTokens for encoding or decoding.

Generic page analytics may record that the tool page was opened, but the tool does not include your encoded or decoded content in analytics events, URLs, or API calls.

How to use this tool

  1. Choose Encode or Decode.
  2. Select Standard Base64 or Base64URL.
  3. Enter text or encoded data in the input area.
  4. Use Live mode for automatic conversion, or click the main action button.
  5. Copy, swap, clear, or download the output when it is ready.
  6. Use the file tools when you need file-to-Base64 or Base64-to-file conversion.

Examples

  • Hello encodes to SGVsbG8=.
  • SGVsbG8= decodes back to Hello.
  • Base64URL is commonly used in JWT header and payload segments.

Important concepts

  • Base64 represents bytes as printable text.
  • Base64URL is safer for URLs and tokens because it avoids + and / characters.
  • UTF-8 handling is required for reliable Unicode text conversion.
  • Decoded files are downloaded as blobs and are not executed by the tool.

Common problems

  • Treating Base64 as encryption instead of encoding.
  • Using standard Base64 where a URL-safe Base64URL value is expected.
  • Forgetting that Base64URL values may omit = padding.
  • Trying to decode binary file data as readable text.

Frequently asked questions

Is Base64 encryption?

No. Base64 is encoding, not encryption. It changes how bytes are represented, but it does not protect the data.

Does CloudTokens store my data?

The Base64 tool runs locally in your browser and does not upload your text or files to a server for conversion.

Can Base64 encode Unicode text?

Yes. This tool converts text with UTF-8 first, so Unicode strings can be encoded and decoded correctly.

What is Base64URL?

Base64URL is a URL-safe variant that uses - and _ instead of + and /. It often omits trailing = padding.

Why does Base64 sometimes end with = or ==?

Those characters are padding used when the original byte length does not fit evenly into Base64 groups.

Can I encode a file to Base64?

Yes. Select a local file and encode it in the browser. Large files may require additional browser memory.

Can I decode Base64 back into a file?

Yes. Paste Base64 or Base64URL content, choose a filename and MIME type, then download the decoded blob.

Does JWT use Base64?

JWT header and payload segments use Base64URL encoding. Use the JWT Debugger for token-specific inspection.

Related tools

  • JWT Debugger

    Decode, inspect claims, verify signatures, compare payload structure, and review JWT expiry timelines.

  • JSON Formatter & Validator

    Format, beautify, minify, validate, copy, and export JSON with line-aware error feedback.

  • Secure Password Generator

    Generate strong passwords with configurable policy controls, copy actions, and text export.

  • Regex Tester & Visualizer

    Create, test, debug, and explain JavaScript regular expressions with live matches and capture groups.

  • Salesforce ID Converter

    Convert Salesforce record IDs between 15-character and 18-character formats with single and bulk browser-based conversion.