Nothing leaves.
Every conversion happens inside your browser tab. Tokens, keys and private payloads are never uploaded, logged or stored.
base64s.com — Paste to begin
Paste text or Base64. The page decides whether to encode or decode, and the result appears at once.
Every conversion happens inside your browser tab. Tokens, keys and private payloads are never uploaded, logged or stored.
No file-size ceilings and no queues. Large inputs convert at the speed of your own device.
Standard and URL-safe alphabets, padding on or off, full UTF-8, and decoding that recognises both variants.
Small icons embedded straight into HTML and CSS.
data:image/png;base64,iVBORw0KGgo…Files and signatures carried through text-only payloads.
"file": "JVBERi0xLjQK…"Every MIME attachment travels as Base64.
Content-Transfer-Encoding: base64JWTs use Base64URL to survive URLs and headers.
eyJhbGciOiJIUzI1NiJ9.…Which is why Base64 text is always about a third longer than the data it carries.
= so the length divides by four.btoa(str)atob(b64)Buffer.from(s).toString("base64")Buffer.from(b64, "base64")base64.b64encode(b)base64.b64decode(s)echo -n "hi" | base64echo "aGk=" | base64 -dbase64.StdEncoding.EncodeToString(b)base64.StdEncoding.DecodeString(s)No. It is an encoding, fully reversible by anyone. For secrecy, use encryption such as AES.
Base64URL swaps +/ for -_ and usually drops padding, making it safe in URLs, filenames and JWTs.
Padding, which rounds the length up to a multiple of four. Most decoders accept text without it.
Every three bytes become four characters, so encoded text runs about 33% longer than the original.
Usually stray whitespace, a mixed-up alphabet, or binary data such as an image being read as text.
Never. base64s is built to run entirely in your browser, with no server-side processing at all.
The converter at the top of this page is the whole tool. What you paste stays on your machine.
Back to the top