Saltar al contenido
uencoder

Decodificador Base64

Decode Base64 data back to readable text online. Gratis, privado y 100% del lado del cliente.

Probar un ejemplo:
Local only

Historial reciente

Sin historial aún

Uso

  1. Paste the Base64 string into the input box.
  2. Select the target character set.
  3. Lea el texto decodificado en la salida.

Tareas que usan esta herramienta

Fix común Base64 decodificación errores
Por qué un Base64 cadena fails a decodificar — missing padding, URL-seguro alphabets, stray whitespace — y el exact pasos a repair cada case.
TAREA
Convertir hexadecimal string to Base64 and back
Translate entre hex dumps y Base64 representations de el mismo binary datos sin losing bytes o introducing padding errores.
TAREA
Decodificar Base64 text and handle missing or corrupted padding
Decodificar Base64 payloads that arrive without trailing '=' padding or with URL-safe alphabet, and recover the original bytes safely.
TAREA
Leer credenciales de un Basic Auth encabezado
Un Base64 decodificar, un colon dividir, y un limpiar-eyed look at por qué Basic Auth credenciales deserve careful handling.
TAREA
Analizar a multipart MIME message and extract each part
Break un multipart/form-datos o multipart/mixed MIME mensaje en its constituent headers y bodies para inspección o reprocessing.
TAREA
Detectar the encoding of unknown text and decode it correctly
Tomar un cadena de mojibake o raw bytes, identificar whether it es UTF-8, Latin-1, Base64, o URL-encoded, y decodificar it a readable texto.
TAREA
Codificar binary data into a JSON-safe string
Convertir raw bytes (images, encrypted blobs, file contents) into a Base64 string that can be embedded inside a JSON field without breaking the structure.
TAREA
Inspeccionar un JWT token: decodificar encabezado y payload sin verifying
Leer el estructura de un JSON Web Token a see its algoritmo, claims, y expiry — purely cliente-side, no servidor validation.
TAREA
Analizar OAuth 2.0 token responses
OAuth 2.0 returns access_token, token_type, expires_in, y optionally refresh_token. Aprender a analizar y usar el token respuesta correctly.
TAREA
Decodificar nested URL-encoded parameters (Base64 JSON in a query string)
Unwrap el común API patrón donde un URL parameter carries URL-encoded Base64 JSON — one chain, three herramientas, zero copy-pasting entre páginas.
TAREA
Usar HTTP Basic Authentication
Basic Auth sends credenciales como Base64-encoded username:contraseña en el Authorization encabezado. Aprender el formatear, seguridad requirements, y alternatives.
TAREA
Usar CBOR codificación para compact binary JSON
CBOR (Concise Binary Objeto Representation, RFC 8949) es un binary serialization formatear para JSON-como datos, smaller y faster than JSON.
TAREA
Usar MessagePack para efficient binary serialization
MessagePack packs JSON-como datos en un compact binary formatear, reducing tamaño y parsing time. Popular en high-performance APIs y IoT.
TAREA
Verificar ese codificar-decodificar round-trips losslessly
Confirm ese decodificación luego re-codificación (o vice versa) returns el exact original entrada, catching silent datos corruption de wrong alphabets o padding.
TAREA

Pipelines que usan esta herramienta

Preguntas frecuentes

What can I decode with this tool?
Any standard Base64 string, including data found in emails (MIME), APIs, JWT payloads, data URIs, and Basic auth headers.
What happens with invalid Base64?
The tool reports an explicit 'Invalid Base64 input' error instead of silently producing garbage. Common causes are truncated strings, whitespace inside the payload, or non-Base64 characters.
Does the tool strip whitespace and newlines?
Yes. Whitespace and CRLF newlines are removed before decoding, so pasted PEM-style blocks or wrapped MIME content decode correctly.
Which character sets are supported?
UTF-8 (default), ASCII, Latin1, and UTF-16LE. Choose UTF-8 for multilingual text; Latin1 for legacy Western European data; UTF-16LE for Windows-native content.
Can I decode a data URI prefix?
Yes, but strip the 'data:...;base64,' prefix first. The decoder expects the raw Base64 payload without the MIME type header.
Why does decoded text show replacement characters (�)?
This usually means the wrong character set was selected. If the original was UTF-8 but you decode as Latin1, multibyte sequences become individual Latin1 characters. Switch the charset to UTF-8.

Herramientas relacionadas