Base64 Encoder
Encode UTF-8 text to Base64 locally.
Read the guideRun the tool
The calculation runs in your browser. This tool does not send your input to JVR Software.
More information
Back to the toolWhat it is and when to use it
Base64 represents arbitrary bytes using printable ASCII letters, digits, plus, slash and padding. It is useful when an interface expects a text field but the underlying data is bytes, such as a small UTF-8 message in a JSON field or an integration fixture. The exact alphabet and padding rules matter at the receiving end.
How it works
The browser converts the input text to UTF-8 bytes. Every three bytes become four Base64 characters. A final group of one or two bytes is padded with equals signs. The result usually takes about one third more space than the byte input, with a slightly larger relative overhead for very short strings.
How to use it
- Paste the exact sample text, including meaningful line breaks.
- Run the encoder and copy the complete output, including trailing equals signs.
- Use the companion decoder to compare the round trip before saving the value in a fixture or sending it to an integration.
Worked example
Hello, world! becomes SGVsbG8sIHdvcmxkIQ==. A trailing newline would change the last characters. For a word such as café, UTF-8 gives the receiver enough information to reconstruct the accented character when it decodes the bytes as UTF-8 as well.
Reading the result
Four-character groups and optional terminal padding are normal. The URL-safe variant changes the symbols for plus and slash, and some protocols omit padding. Check the destination’s required encoding before assuming that the output can be pasted straight into a URL segment.
Common mistakes and limits
Base64 is reversible and offers zero secrecy. Use fictional values for examples and diagnostic sharing. A Base64 value can carry different bytes depending on the input character set. Use the Image Data URL tool when you need a media type and a data URL wrapper.
