- Result
- SGVsbG8sIEZpbmZsbyE=
About this result
Base64 is an encoding, not encryption. Processing stays in this browser. Legacy text conversions require a lossless round trip; arbitrary binary data belongs in the file tool.
ASCII and ISO-8859-1 use their strict byte meanings. GBK includes GB2312-compatible characters; ISO-8859-8-I shares the Hebrew byte map with logical text ordering.
Loading local file tools…
How it works
Encoding usually makes data larger
Standard padded Base64 turns 1,000 input bytes into 1,336 characters before any surrounding markup. Use the byte count, not the visible text length, when estimating encoded size; non-ASCII text can occupy several bytes per character.
Understanding what Base64 changes
Base64 represents bytes using a text-friendly alphabet; it is an encoding, not encryption. Select the text encoding deliberately when converting non-ASCII characters so that decoding can reconstruct the intended bytes. Check whether your input is plain text or already encoded data before choosing the operation. A valid Base64 string does not prove that the decoded content is trustworthy.
Base64 text: formula and assumptions
Convert UTF-8 bytes to or from the RFC 4648 Base64 alphabet.
Text is processed locally. Encoding is not encryption; do not treat encoded data as secret.
Base64 with a selected text encoding: formula and assumptions
Text → selected codec bytes → standard padded Base64, or the reverse.
Uses a strict lossless text round trip. ASCII and Latin-1 retain their actual byte definitions. Arbitrary binary files use the separate file tool; encoding is not encryption.
Worked example
Using the Base64 text example:
- Operation
- Encode
- Text
- Hello, Finflo!
Convert UTF-8 bytes to or from the RFC 4648 Base64 alphabet.
Example result
Result: SGVsbG8sIEZpbmZsbyE=
- Base64 is an encoding, not encryption. Processing stays in this browser. Legacy text conversions require a lossless round trip; arbitrary binary data belongs in the file tool.
- ASCII and ISO-8859-1 use their strict byte meanings. GBK includes GB2312-compatible characters; ISO-8859-8-I shares the Hebrew byte map with logical text ordering.
These are illustrative inputs. Change the values to explore a different scenario.
Formula references
References explain the underlying methods; they do not imply endorsement or individual professional review of Finflo.
Common questions
Does Base64 protect confidential text?
No. Base64 is a reversible encoding, not encryption. Anyone with the encoded value can decode it.
Can I encode or decode binary files?
Yes. Use the separate local-file panel for binary files up to 10 MiB, or decode a Base64 text file back to bytes. The text modes instead interpret bytes with UTF-8 or another selected supported encoding. Files are processed in this browser; decoding does not establish that a file is safe to open.
Prepared by Finflo. See our methodology and editorial policy.