Task path / input to outcome
How to encode and decode Base64
- 01
Pick Encode or Decode
Use the mode tabs to choose a direction before you paste. The result pane updates live as you type, and the status dot reports Ready, Valid, or Error for the current input, so malformed values surface before you copy anything.
- 02
Enter or paste the value
Type into the Text input pane to encode, or paste into the Base64 input pane to decode; the panes relabel themselves with the selected mode. Load sample drops in a tiny example so you can see the round trip first, and whitespace inside a pasted Base64 value is ignored when decoding.
- 03
Set the character and format options
UTF-8 is on by default and is required for characters beyond the Latin-1 byte range, such as emoji and CJK text. URL-safe swaps + and / for - and _ and strips the padding so the value survives inside URLs and file names. Preserve line breaks, also on by default, keeps newlines instead of folding them into spaces, and every option applies to both directions.
- 04
Check the live validation
Decoding validates as you go. Characters outside the alphabet, an impossible length, and — with UTF-8 on — bytes that are not valid UTF-8 each produce a named error that tells you what to fix. Correct the flagged value and the result recovers immediately, with no run button to press.
- 05
Round-trip with Swap
Use Swap to move the output into the input with the direction flipped: a decode becomes an immediate re-encode, and a matching input proves the value survives the trip exactly. This is the fastest way to verify a credential or configuration value before it goes into a CI variable or an API call.
- 06
Copy or download the result
Copy result takes the output to the clipboard for a ticket or a terminal, and Download .txt saves it as toolars-base64.txt or toolars-decoded.txt. Clear empties the current workspace; it does not remove an output copy you explicitly handed to another tool. See the privacy FAQ for its retention.