Base64 Encoder & Decoder

No. Base64 is encoding, not encryption — it is fully reversible and provides no security. Never use it to protect secrets.

No. Toolvore reads, encodes, decodes and previews the bytes inside your browser. No file or pasted value is sent to a server. Files are capped at 20 MiB because the original bytes and the larger encoded string must coexist in tab memory.

Yes. Choose File and Decode, paste the raw payload or a full data URI, set a filename and decode it. The page recognises common signatures including PNG, JPEG, GIF, WebP, PDF and ZIP, shows the first 64 bytes for inspection and downloads the exact decoded bytes. A recognised extension is suggested, but it does not prove that the rest of a damaged file is valid.

A valid Base64 value can represent any bytes, not necessarily UTF-8. Text mode deliberately rejects an invalid UTF-8 sequence instead of replacing bytes with � and pretending the decode succeeded. Switch to File mode to inspect and download the binary unchanged.

Choose Base64URL before decoding a single URL-safe segment. It uses minus and underscore instead of plus and slash and commonly omits equals-sign padding; the decoder restores that padding. A JWT contains three dot-separated segments, so decode the header and payload separately, not the full token. The third segment is a binary signature, and the dedicated JWT decoder is better when you want the token split automatically.

They are padding. Base64 writes four characters for each group of three source bytes, so the last group sometimes needs one or two equals signs to reach four characters. They carry no data. Toolvore can emit padded or unpadded raw output and restores omitted padding while decoding, but it still rejects padding in the middle, more than two equals signs, and impossible payload lengths.

Three bytes become four characters, so the payload grows by about one third before a data-URI prefix or line wrapping is counted. Base64 is a transport encoding, not compression. A linked image can also be cached separately, while an inlined data URI travels with every copy of its document, so large assets are usually better left as files.

They represent the same bytes. Base64URL replaces Standard Base64's plus with minus and slash with underscore, and it often drops trailing padding, which avoids characters with special meaning in URLs and filenames. Do not confuse Base64URL with percent-encoding: percent-encoding escapes selected URL characters, while Base64URL rewrites every source byte into a separate alphabet.

No. A prefix can claim that arbitrary bytes are image/png or text/plain. Toolvore reports that declaration but separately checks common file signatures, previews only recognised raster images, never renders SVG or HTML, and serves the download as application/octet-stream. Signature checks identify a likely format; they are not malware scanning or full file validation.

Yes. Paste the complete data:...;base64,... value in either decode mode. Parameters such as charset are allowed, whitespace in the payload is ignored and the media type is reported. A data URI without the ;base64 marker is percent-encoded data rather than Base64 and is rejected instead of being mis-decoded.