¿Es Base64 un cifrado?

No. Base64 es codificación, no cifrado. Cualquiera puede decodificarlo. Nunca lo uses para proteger datos sensibles.

¿Se envían mis datos a un servidor?

No. Todo el procesamiento ocurre localmente en tu navegador.

¿Es compatible con Unicode?

Sí. El codificador usa UTF-8 internamente, por lo que todos los caracteres Unicode se manejan correctamente.

¿Para qué sirve el botón de intercambio?

Mueve la salida a la entrada y cambia el modo — útil para verificar datos rápidamente de ida y vuelta.

Is Base64 the same as encryption?

No. Base64 only re-represents bytes as text with no key or secret involved, so it provides zero confidentiality — anyone can decode it instantly.

Why is my JWT or URL token not decoding correctly here?

Many tokens use Base64url encoding, which replaces + with -, / with _, and often omits padding — if standard decoding fails, try the URL-safe variant.

Why does encoded text look longer than the original?

Base64 converts every 3 bytes of binary input into 4 ASCII characters, inflating size by roughly 33%, plus padding characters at the end.

Can I Base64-encode an entire image file here?

This tool works on text and Base64 strings; for a raw file you'd typically convert it to Base64 first using a file-to-base64 step, then paste the resulting string here to inspect or manipulate it.

tools / developer

Codificador / Decodificador Base64

Codifica y decodifica cadenas Base64 al instante — pega cualquier texto para codificarlo, o pega Base64 para decodificarlo a texto plano.

TEXTO PLANO

BASE64

el resultado aparece aquí...

Acerca de Base64

Base64 es un esquema de codificación que convierte datos binarios en texto ASCII. Se usa habitualmente para incrustar recursos binarios en JSON, codificar datos en URL y transmitir datos a través de protocolos basados en texto. Esta herramienta maneja texto Unicode completo mediante codificación UTF-8.

Preguntas frecuentes

¿Es Base64 un cifrado?: No. Base64 es codificación, no cifrado. Cualquiera puede decodificarlo. Nunca lo uses para proteger datos sensibles.
¿Se envían mis datos a un servidor?: No. Todo el procesamiento ocurre localmente en tu navegador.
¿Es compatible con Unicode?: Sí. El codificador usa UTF-8 internamente, por lo que todos los caracteres Unicode se manejan correctamente.
¿Para qué sirve el botón de intercambio?: Mueve la salida a la entrada y cambia el modo — útil para verificar datos rápidamente de ida y vuelta.

ACERCA DE ESTA HERRAMIENTA

Paste any text to encode it into Base64, or paste a Base64 string to decode it back to plain text. Base64 represents binary data using 64 printable ASCII characters (A–Z, a–z, 0–9, + and /, with = padding), which is why it's the standard way to embed images, fonts, or files inside text-based formats like JSON, HTML, or email. Because it encodes 3 bytes as 4 characters, encoded output is always roughly 33% larger than the original. Commonly used when working with email attachments, authentication tokens, or embedding binary data in JSON and HTML — this tool runs entirely client-side, so sensitive tokens never leave your browser.

CÓMO USARLO

Choose Encode or Decode mode.
Paste your plain text (to encode) or Base64 string (to decode) into the input box.
Click convert, or let it convert automatically as you type.
Review the output — decoding invalid Base64 shows an error instead of garbled text.
Copy the result to your clipboard.
For files or images, convert them to a Base64 string elsewhere first, then paste here to inspect or re-encode.

CASOS DE USO COMUNES

A developer embedding a small icon as a data URI in CSS needs to Base64-encode the image file's bytes.
Someone inspecting the payload of a Basic Auth header decodes the "Authorization: Basic xxxx" string to see the username and password.
An engineer debugging an email system decodes a Base64-encoded attachment or body part from raw MIME.
A developer storing binary blobs in a JSON field encodes them first since JSON has no native binary type.
A student verifying how much larger encoded output gets compares byte counts before and after encoding.

CONSEJOS Y ERRORES COMUNES

Base64 is encoding, not encryption — anyone can decode it, so never use it as a way to protect secrets or passwords.
Standard Base64 uses + and / characters, which aren't URL-safe; if you're decoding a token from a URL, look for "Base64url" variants that use - and _ instead.
Decoding fails or produces garbage if the input has incorrect padding (=) or contains characters outside the Base64 alphabet.
Expect encoded text to be about 33% larger than the original, since every 3 bytes of input becomes 4 characters of output.

MÁS PREGUNTAS

Is Base64 the same as encryption?: No. Base64 only re-represents bytes as text with no key or secret involved, so it provides zero confidentiality — anyone can decode it instantly.
Why is my JWT or URL token not decoding correctly here?: Many tokens use Base64url encoding, which replaces + with -, / with _, and often omits padding — if standard decoding fails, try the URL-safe variant.
Why does encoded text look longer than the original?: Base64 converts every 3 bytes of binary input into 4 ASCII characters, inflating size by roughly 33%, plus padding characters at the end.
Can I Base64-encode an entire image file here?: This tool works on text and Base64 strings; for a raw file you'd typically convert it to Base64 first using a file-to-base64 step, then paste the resulting string here to inspect or manipulate it.