Base64 string encoder/decoder

Simply encode and decode strings into their base64 representation.

Enable JavaScript to use the interactive tool. The guide below explains how it works.

Base64 String Converter: Technical Documentation and Deep Dive

1. What the Tool Does

The Base64 String Converter is a high-performance, browser-based utility designed to encode plain text into Base64 format and decode Base64-encoded strings back into their original textual representation. It supports standard Base64 (RFC 4648) as well as the URL-safe variant, which replaces characters that are problematic in URLs (like + and /) with - and _.

At its core, the tool performs a binary-to-text encoding. Base64 represents binary data in an ASCII string format by translating it into a radix-64 representation. This tool specifically focuses on string-to-string conversion, handling UTF-8 character encoding to ensure that special characters and emojis are preserved during the transformation.

2. Why Someone Uses It

Base64 encoding is a fundamental part of modern web infrastructure. Engineers and developers use this tool for several critical reasons:

• Data Transmission: Binary data (like images or encrypted blocks) often needs to be sent over protocols that only support text (like JSON, XML, or HTML). Base64 ensures the data remains intact without being corrupted by control characters or protocol-specific delimiters.
• Data URIs: Developers often embed small assets (like icons or small CSS fonts) directly into stylesheets or HTML using data:image/png;base64,... strings to reduce HTTP requests.
• URL Parameters: When passing complex data in a URL, standard Base64 can break the URL structure due to the use of / and +. The URL-safe mode in this tool is essential for creating safe tokens, state parameters, or deep-linking data.
• Debugging and Inspection: When working with JWTs (JSON Web Tokens), webhooks, or API responses, developers frequently encounter Base64-encoded payloads. This tool allows for instant "sanity checks" to see the underlying JSON or text.
• Legacy Systems: Many older systems or specific protocols (like Basic Auth or SMTP) require data to be Base64 encoded for compatibility.

3. Step-by-Step Instructions

Encoding (String to Base64)

1. Input: Type or paste your plain text into the "String to encode" text area.
2. Configuration: If you intend to use the result in a URL or as a filename, toggle the "Encode URL safe" switch. This will replace + with - and / with _, and remove trailing = padding.
3. Output: The "Base64 of string" field will update in real-time.
4. Finalize: Click the "Copy base64" button to copy the encoded string to your clipboard.

Decoding (Base64 to String)

1. Input: Paste your Base64 string into the "Base64 string to decode" field.
2. Configuration: If the input string uses the URL-safe alphabet (e.g., it contains - or _), ensure the "Decode URL safe" switch is enabled.
3. Validation: The tool will automatically validate the input. If the string is not valid Base64, an error message "Invalid base64 string" will appear.
4. Output: The "Decoded string" field will display the original text.
5. Finalize: Click "Copy decoded string" to retrieve your plain text.

4. Examples

Standard Encoding

• Input: Hello World!
• Output: SGVsbG8gV29ybGQh

URL-Safe Encoding

• Input: subjects?_id=1
• Standard Output: c3ViamVjdHM/X2lkPTE=
• URL-Safe Output: c3ViamVjdHM_X2lkPTE (Note the change from ? logic in the source and how / or + would be handled if present).

Complex Character Encoding (UTF-8)

• Input: 🚀 Gemini CLI
• Output: 8J+agCBHZW1pbmkgQ0xJ

5. FAQs

Q: Does this tool store my data? A: No. All conversions happen entirely within your browser's JavaScript engine. Your data never leaves your machine and is never sent to a server.

Q: What is the difference between Base64 and Encryption? A: Base64 is not encryption. It is an encoding scheme. Anyone can decode a Base64 string without a key. Never use Base64 to secure sensitive information like passwords unless it is part of a larger encrypted pipeline.

Q: Why does the output sometimes end with =? A: The = character is used for padding. Since Base64 processes data in 3-byte blocks, if the input is not a multiple of 3 bytes, padding characters are added to ensure the output length is a multiple of 4.

Q: Why is my decoded text showing garbled characters? A: This usually happens if the original data was not text (e.g., it was a binary image file) or if it used a different character encoding (like Latin-1) instead of UTF-8.

6. Common Mistakes

• Treating Base64 as Security: A common mistake is "hiding" data in Base64 thinking it's safe from prying eyes. It's merely a format change, like changing a font.
• Mismatched URL-Safe Settings: Attempting to decode a standard Base64 string with the "URL-safe" toggle ON (or vice versa) can lead to decoding errors if the string contains characters like +, /, -, or _.
• Copying the Data URI Prefix: When decoding, ensure you don't include the data:image/png;base64, prefix. Only the actual Base64 string should be pasted into the tool.
• Ignoring Whitespace: Sometimes Base64 strings are copied with newlines or spaces (especially from emails). This tool trims whitespace, but large blocks of non-Base64 text will cause validation failures.

7. Use Cases

• Webhook Integration: When integrating with services like Stripe or GitHub, payloads are sometimes Base64 encoded. Use this tool to inspect those payloads during development.
• Front-end Optimization: Quickly converting a small SVG icon to Base64 to inline it in your Vue or React component's CSS.
• JWT Debugging: JWTs consist of three parts separated by dots. Each part is a URL-safe Base64 string. You can paste the header or payload section here to read the JSON metadata.
• API Development: When testing an API that expects a Basic auth header or a Base64-encoded blob, use this to generate the required string.

8. Related Tools

• Base64 File Converter: Use this when you need to convert actual files (PNG, PDF, etc.) to Base64 rather than just text strings.
• Basic Auth Generator: A specialized tool that automates the username:password Base64 encoding required for HTTP headers.
• JWT Decoder: Specifically designed to split and decode the three parts of a JSON Web Token.
• String Case Converter: Useful for prepping strings before encoding them for specific naming conventions in APIs.