Codificar / Decodificar Base64

Codifica texto o un archivo a base64, o decodifica base64 de vuelta a texto o un archivo. Seguro con UTF-8. Todo ocurre en tu navegador — no se sube nada, sin inicio de sesión, sin rastreo.

Elige codificar o decodificar

Consejo: en modo decodificar, los espacios dentro del base64 se ignoran, así que el base64 con saltos de línea de correos o chats funciona sin limpieza.

—

About this tool

Base64 encodes and decodes text and binary data using the standard Base64 alphabet (RFC 4648 §4). It supports both the standard and URL-safe variants (using - and _ in place of + and /), with optional padding (the trailing = signs). The encode side accepts UTF-8 text and arbitrary binary (you can drop in a PNG, a PDF, or a JWT and the bytes are encoded byte-for-byte). The decode side validates the alphabet strictly and reports invalid characters with their positions, so a malformed payload is obvious rather than silently corrupted.

When to use it

  • Inspecting the contents of a Base64-encoded JWT or session cookie
  • Encoding a small image, font, or PDF for inline embedding in a CSS data: URL
  • Decoding a Base64 string from a log line or an environment variable
  • Converting between the standard and URL-safe Base64 alphabets

When not to use it

  • You need Base32, Base58, or hex — those have separate tools on the site (Base32, Base58, Hex Inspector)
  • You are encoding secrets for storage — Base64 is an encoding, not encryption. Anyone who has the encoded string has the data
  • You are working with binary files larger than a few MB — Base64 inflates the data by 33%, so it is inefficient for bulk transport

Frequently asked questions

Is Base64 encryption?

No. Base64 is a binary-to-text encoding that maps 3 bytes to 4 ASCII characters. It provides zero confidentiality. Anyone who has the Base64 string has the underlying data — Base64 is trivially reversible. Use a real cipher (AES, ChaCha20) for anything sensitive.

What is the URL-safe variant?

It substitutes - and _ for + and /, which would otherwise need to be percent-encoded inside a URL. If your payload is going into a URL parameter or a filename, URL-safe Base64 is usually the right choice. The two variants are mutually exclusive — a mixed string will not decode.

← Back to the homepage · More guides · More from the blog