Base64 Encoder / Decoder
Encode and decode Base64 text in the browser.
Sensitive data: Anything you enter is processed in your browser only. It is never uploaded or logged on a server.
Base64 encoding and decoding
Base64 represents binary data as ASCII text safe for JSON fields, email, and query parameters. It is widely used for small attachments, protobuf wrappers in logs, and embedding icons in data URLs. Base64 is not encryption; anyone can decode standard payloads.
URL-safe variants swap characters to avoid breaking URLs and JWT segments. When decoding fails, check padding, character set, and whether the source used standard or URL-safe alphabets. Some platforms wrap Base64 inside JSON with additional escaping.
Encoded data expands roughly four-thirds in size. Very large inputs can stress browser memory; chunk or sample huge files during investigation instead of pasting entire dumps when possible.
Decode and encode locally when inspecting observability payloads, Kubernetes secret data fields, or mobile crash attachments. Local processing keeps tokens and compressed diagnostics off third-party websites.
Reference Guide
Base64 encodes bytes as ASCII-safe text. It is not encryption.
| Variant | Notes |
|---|---|
| Standard | Uses + and / |
| URL-safe | Uses - and _, common in JWT segments |
Decode unknown payloads locally. Decompressed or binary output may be large.
Current mode
Operation: base64-encode
All processing runs locally in your browser. Paste input, click Run, and copy the result.
Example Input
DevPipe tools
A sample loads automatically when you open this tool. Use Load Sample to reset it.