Plain text, the simplest data format. No formatting, no metadata, just characters. Universal compatibility across every device and program ever made.
How to open
Every text editor on every platform. Browser previews.
free · in-browser · no upload
Drop your Text file. We'll convert it to Base64 right here in your browser, your file never leaves your device.
Select your file here to get started
or drop your file here.
Accepts .txt
How it works
Click the dropzone above or drag a Text from your desktop. Files of any size, there's no upload, so there's no upload limit.
The conversion runs entirely in this tab using JavaScript and WebAssembly. Your file never touches our servers, we don't have any.
Get your Base64 the moment the conversion finishes. Convert another, or close the tab.
Your file is never uploaded. The entire conversion runs in your browser using WebAssembly. We can't see what you convert because we have no server to see it.
Server converters cap free users at 1-2 GB and gate larger files behind a paid plan. Since nothing uploads, our limit is whatever your browser can handle.
No account required. No watermark on the output. No queue. Drop a file, get a converted file.
Why convert Text → Base64
Base64 is the standard for embedding binary data in text-only channels: email attachments (MIME), data: URIs in CSS, JWT payloads, JSON fields that need to carry images, every API that has a 'base64-encoded payload' parameter. Devs hit this 5x a day debugging.
You're inlining a small SVG icon into your CSS as a data: URI. You wrap the SVG markup, paste it here, and get back the base64 string for `data:image/svg+xml;base64,...`. No round-trip to a server-based tool that might log your data.
My base64 has line breaks every 76 characters — is that a problem?
MIME standard wraps base64 at 76 columns. Most modern parsers tolerate this. If your consumer is strict, the converter strips whitespace on decode automatically; you can also pre-strip with `tr -d '\n' < file.b64`.
Decoded text shows '?' or garbled characters.
Base64 encoded the bytes as-is — the encoding (UTF-8 vs Latin-1 vs UTF-16) of the original text matters. Our encoder uses UTF-8 throughout. If your source was Latin-1, multi-byte characters may decode incorrectly. Re-encode the source as UTF-8 first.
Formats involved
Plain text, the simplest data format. No formatting, no metadata, just characters. Universal compatibility across every device and program ever made.
How to open
Every text editor on every platform. Browser previews.
Base64 encodes any byte sequence as ASCII text using 64 printable characters (A-Z, a-z, 0-9, +, /, with = padding). Output is ~33% larger than input but survives every text channel that strips or mangles binary: email attachments (MIME), JSON fields, URLs (URL-safe variant), data: URIs, JWT payloads. The format dates to RFC 989 (1987) and was standardized in RFC 4648.
How to open
Any text editor displays base64. To decode back to bytes: `base64 -d` on Mac/Linux, `certutil -decode` on Windows, or paste into any base64 web decoder. Used heavily in dev tools, API debugging, and security workflows.
FAQ
Yes. No signup, no watermark, no daily file count limit. Every conversion runs in your browser, your file never touches our servers because there are no servers.
Nowhere. The conversion runs entirely in your browser using JavaScript and WebAssembly. Your file is never uploaded to our servers. We don't have any servers handling files, there's nothing for us to log, store, or accidentally leak.
Whatever your browser can hold in memory. Practically, this means a few hundred MB on most computers, significantly larger than the 1-2 GB caps that server-upload converters charge for. Very large files (multi-GB) may require closing other browser tabs first.
Universal text interchange. Embedding binary data in text-only channels (email, JSON, URLs). The most common reason to convert is compatibility, Base64 works in places where Text doesn't, or vice versa.
Every text editor on every platform. Browser previews.
Once the page is loaded, the conversion itself runs entirely offline. The first time you use a tool, your browser downloads the conversion library (a one-time cache). If you reload while offline, the page won't load, but you can install the site as a Progressive Web App for full offline use.
Single file at a time for now. Batch conversion is on the roadmap, for now, drop one file, download the result, then convert the next.