What is Base64 Encoder & Decoder?
The Base64 Encoder and Decoder handles UTF-8 text used in API fields, data fragments, and cross-system transfer. Chinese text, emoji, and other Unicode characters are converted to bytes before encoding. Decoding strictly checks the Base64 form and UTF-8 result so damaged data is not presented as valid text. Common workflows include the following. Create Base64 text fields for an API example. Check whether received Base64 restores to valid UTF-8. Inspect ordinary text wrapped in Base64 inside configuration or logs. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Create Base64 text fields for an API example.
- Check whether received Base64 restores to valid UTF-8.
- Inspect ordinary text wrapped in Base64 inside configuration or logs.
How to use it
- Enter UTF-8 text or Base64 content.
- Choose encode or decode.
- Review and copy the result.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
JSONLane release check: Unicode, emoji 🚀, and a newline
are encoded as UTF-8.Example 2
eyJwcm9qZWN0IjoiSlNPTkxhbmUiLCJ0b29scyI6MjAsInJlYWR5Ijp0cnVlfQ==Input rules
- Encoding input is interpreted as UTF-8 text.
- Decoding requires valid Base64 characters and padding.
- Base64 is not encryption and should not be treated as confidential storage.
- Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- Base64 is not encryption or secure storage.
Output rules
- Encoding uses the standard Base64 alphabet.
- Decoded bytes must be valid UTF-8 or an error is shown.
- Results are always displayed as plain text and never executed.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Invalid characters, padding, or non-UTF-8 output cause an error.
Limitations and cautions
- Base64 is not encryption or secure storage.
- Invalid characters, padding, or non-UTF-8 output cause an error.
How your data is handled
Byte conversion and Base64 operations happen locally in the browser, with no network transmission.