What is the base64 decode command in Linux?

The base64 decode command in Linux is base64 -d or base64 --decode . You pipe or redirect the encoded data to it, and it outputs the decoded text or binary. For example: echo -n "SGVsbG8=" | base64 -d decodes to "Hello".

Can I decode Base64 without a terminal?

Yes, you can decode Base64 without a terminal using browser-based tools like Base64 Encode / Decode. These tools run entirely in your browser, support full UTF-8 (emoji and accents), and update results instantly as you paste or type.

Why does my Base64 decode output look garbled?

Garbled output usually happens because the terminal or tool isn’t set to UTF-8 encoding, or the input includes line breaks or non-Base64 characters. Browser tools handle these issues automatically, while terminal commands may require flags like -w 0 or -i .

How do I decode Base64 in Windows?

In Windows PowerShell, use [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String("encoded_string")) . For files, read the content first with Get-Content and pipe it to the same method.

Can I decode Base64 on my phone?

Yes, browser-based tools like Base64 Encode / Decode work on any modern smartphone or tablet. Open the tool in your browser, paste the Base64 string, and the decoded output appears instantly—no app or terminal required.

What’s the difference between Base64 and URL encoding?

Base64 encodes binary data into a 64-character set (A-Z, a-z, 0-9, +, /), while URL encoding replaces unsafe characters with percent signs and hex values (e.g., %20 for space). Use URL Decoder

Decode Base64 from the Command Line Without Installing Anything

The base64 decode command is a standard utility available in Linux, macOS, and Windows PowerShell that converts Base64-encoded text back to its original form. In Linux and macOS, the command is simply base64 -d or base64 --decode; in Windows PowerShell, it’s [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($encoded)). While these commands are powerful, they require a terminal, correct syntax, and often manual handling of line breaks, non-ASCII characters, and file inputs. For users who need a faster, more visual, or more forgiving way to decode Base64—especially when working with emoji, accents, or large files—a browser-based tool like Base64 Encode / Decode offers a simpler alternative. It runs entirely in your browser, supports full UTF-8, and updates results instantly as you type or paste.

Base64 encoding is commonly used to safely transmit binary data (like images, PDFs, or JSON payloads) over text-based protocols such as email, URLs, or APIs. When you receive a Base64 string—whether from an API response, a configuration file, or a colleague—you need a reliable way to decode it back to readable text or usable binary. Terminal commands work, but they can be error-prone: forgetting the -d flag, miscounting line breaks, or accidentally corrupting non-ASCII characters are common pitfalls. Browser tools eliminate these issues by handling the decoding logic for you, while keeping all data local and secure. This makes them ideal for quick tasks, debugging, or situations where you don’t have terminal access—like on a shared computer or a mobile device.

When to Use a Browser Tool Instead of the Command Line

While the base64 command is efficient for automation and scripting, browser-based tools shine in scenarios where speed, accessibility, and ease of use matter more than raw power. Here’s when to consider using Base64 Encode / Decode instead of the terminal:

Scenario	Command Line	Browser Tool
Decoding short strings (e.g., API tokens, config values)	Requires typing or pasting into terminal; risk of shell escaping issues.	Instant paste-and-decode; no escaping needed.
Working with emoji, accents, or non-Latin scripts	May garble output unless terminal encoding is set correctly (e.g., `LC_ALL=en_US.UTF-8`).	Full UTF-8 support; emoji and accents decode perfectly every time.
Decoding on a mobile device or shared computer	Not practical without terminal apps or remote access.	Works in any modern browser, no install required.
Debugging or testing multiple encodings	Requires re-running the command or piping output to a file.	Instant feedback; swap direction with one click to re-encode.
Decoding large files (e.g., images, PDFs)	Requires file redirection or temporary files; output may wrap unexpectedly.	Handles large inputs smoothly; no file size limits (within browser memory).

Browser tools are also ideal for users who aren’t comfortable with the command line or who need to share results quickly. For example, if you’re collaborating with a teammate who isn’t technical, sending them a link to Base64 Encode / Decode is far simpler than explaining how to use base64 -d or PowerShell commands. Similarly, if you’re debugging an API response that includes Base64-encoded data, a browser tool lets you decode and inspect the payload without leaving your development environment.

How to Decode Base64 Without the Command Line

Decoding Base64 in your browser is straightforward with the Base64 Encode / Decode tool. Here’s how to do it step by step:

Open the tool: Go to Base64 Encode / Decode in your browser. No sign-up or download is required.
Choose decode mode: The tool defaults to "Decode" (Base64 → text). If it’s set to "Encode," click the Swap button to switch directions.
Paste your Base64 string: Copy the Base64-encoded text from your source (e.g., an email, API response, or file) and paste it into the input box. The tool updates the output instantly as you type or paste.
Review the decoded output: The decoded text appears in the output box below. If the input was valid Base64, you’ll see the original text, emoji, or binary data. If the input was malformed, the tool will show an error.
Copy or reuse the result: Click Copy to save the decoded text to your clipboard. If you need to re-encode it (e.g., for testing), click Swap to reverse the direction and feed the output back into the tool.

This workflow works for any Base64-encoded data, whether it’s a short string like SGVsbG8gV29ybGQh (which decodes to "Hello World!") or a large file like an encoded image. The tool handles line breaks automatically, so you don’t need to strip them out or worry about the -w 0 flag you’d use in the terminal. It also preserves all Unicode characters, so emoji (e.g., 8J+OiA== → 👋) and accented letters (e.g., w6nDqQ== → éè) decode correctly.

Decoding Base64 in the Terminal: A Quick Reference

If you prefer using the command line, here’s how to decode Base64 in Linux, macOS, and Windows PowerShell. These commands assume you have a Base64-encoded string or file; for large files, redirect the output to a new file to avoid terminal display issues.

Linux and macOS

The base64 command is included by default in most Linux distributions and macOS. To decode a string:

echo -n "SGVsbG8gV29ybGQh" | base64 --decode

To decode a file (e.g., encoded.txt) and save the result to decoded.txt:

base64 --decode < encoded.txt > decoded.txt

Key options:

-d or --decode: Decode mode (required for decoding).
-i or --ignore-garbage: Skip non-Base64 characters (useful for malformed input).
-w 0 or --wrap=0: Disable line wrapping (useful for binary data).

Windows PowerShell

PowerShell doesn’t include a native base64 command, but you can use .NET methods to decode Base64:

[System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String("SGVsbG8gV29ybGQh"))

To decode a file, read its contents first:

$encoded = Get-Content -Path "encoded.txt" -Raw
[System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($encoded)) | Out-File -FilePath "decoded.txt"

Note that PowerShell’s Get-Content may add line breaks, so use -Raw to read the file as a single string.

Common Pitfalls in the Terminal

Line breaks: Base64-encoded data is often wrapped at 76 characters for readability. The base64 command in Linux/macOS preserves these by default, which can corrupt binary data. Use -w 0 to disable wrapping when decoding files.
Non-ASCII characters: If your terminal’s encoding isn’t set to UTF-8, emoji and accented letters may appear garbled. Run export LC_ALL=en_US.UTF-8 (Linux/macOS) before decoding to ensure correct output.
Shell escaping: If your Base64 string contains special characters (e.g., $, !), they may be interpreted by the shell. Wrap the string in single quotes (e.g., echo -n 'SGVsbG8hJCQ=' | base64 -d) to avoid this.
File permissions: When decoding files, ensure you have read access to the input file and write access to the output location. Use chmod or sudo if necessary.

While these commands are powerful, they require attention to detail. For quick, error-free decoding—especially with Unicode or large files—browser tools like Base64 Encode / Decode are often the better choice.

Beyond Decoding: When You Might Need to Re-Encode

Decoding Base64 is often just one step in a larger workflow. For example, you might decode a JSON Web Token (JWT) to inspect its payload, then re-encode it to test an API. Or you might decode an image, modify it, and re-encode it for upload. The Base64 Encode / Decode tool makes this easy with its Swap feature, which lets you toggle between encoding and decoding with one click. Here’s how it works:

Decode your Base64 string as usual (e.g., 8J+OiA== → 👋).
Click Swap to switch to encode mode.
The decoded text (👋) is automatically copied to the input box, ready to be re-encoded.
Click Copy to save the new Base64 string (8J+OiA==).

This is particularly useful for debugging or testing. For instance, if you’re working with an API that expects Base64-encoded data, you can decode the response, make changes, and re-encode it to see how the API behaves. The tool’s instant feedback loop saves time and reduces errors compared to running terminal commands repeatedly.

Another common use case is handling binary data like images or PDFs. While the terminal can decode these, browser tools provide a more visual way to verify the output. For example, if you decode a Base64-encoded PNG, the tool won’t display the image directly, but you can copy the binary data and paste it into a file with the correct extension (e.g., image.png). This is especially helpful when working with encoded files in web applications or configuration files.

Alternatives for Advanced Use Cases

While browser tools and terminal commands cover most Base64 decoding needs, some scenarios require more specialized approaches. Here are a few alternatives and when to consider them:

Programming languages: If you’re writing code, most languages include Base64 libraries. For example:
- Python: import base64; base64.b64decode("SGVsbG8=").decode("utf-8")
- JavaScript: atob("SGVsbG8=") (note: atob doesn’t support UTF-8; use a library like TextDecoder for non-ASCII characters)
- PHP: base64_decode("SGVsbG8=")
These are ideal for automation or integrating Base64 decoding into larger scripts or applications.
Online APIs: Some APIs (e.g., Web Crypto API) provide Base64 encoding/decoding as part of their functionality. These are useful for web apps that need to handle Base64 data without server-side processing.
Text editors with plugins: Editors like VS Code or Sublime Text offer plugins for Base64 encoding/decoding. These are handy for developers who want to decode strings directly in their code without switching to a browser or terminal.
Mobile apps: Apps like Termux (Android) or a-Shell (iOS) bring terminal commands to mobile devices, allowing you to use base64 -d on the go. However, browser tools are often more convenient for quick tasks.

For most users, though, the combination of terminal commands and browser tools like Base64 Encode / Decode covers all the bases. The terminal is best for scripting and automation, while browser tools excel at speed, accessibility, and handling Unicode. If you’re unsure which to use, start with the browser tool—it’s the fastest way to get results without memorizing syntax or troubleshooting terminal quirks.

If you’re working with other encoding formats, our site offers tools for related tasks. For example, Morse Code Translator lets you convert text to Morse code and back, while Binary To Text handles binary-to-text conversions with full Unicode support. For secure password generation, try Password Generator, which creates strong passwords locally in your browser.