Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenType or paste text and copy its Base64 form, with accented letters and emoji encoded correctly.
Any UTF-8 text works, including emoji and non-Latin scripts.
The Base64 output refreshes on every keystroke, no Run button needed.
The status line compares input characters with Base64 characters.
Grab the single-line result or save it as encoded.txt.
A webhook provider wants a JSON field holding a Base64-encoded note, and the note includes a customer's name with an umlaut. A quick btoa() in the console throws on that character. Base64 Encoder converts the text to UTF-8 first, so the encoded value decodes back to exactly what you typed.
Output updates on every keystroke, and the status line shows how many characters went in and how many Base64 characters came out, which makes the roughly one-third size increase easy to see. Text becomes UTF-8 bytes before encoding, so 'Hello, 世界! 🌍' round-trips cleanly. The result uses the standard alphabet with + and / and = padding, ready for JSON fields, Basic auth test strings or small data URLs. Sample, Copy, Download and Clear buttons handle the usual chores.
A common mistake is dropping standard Base64 into a URL or a token, where + and / cause trouble. Run the output through the URL-safe Base64 converter instead of swapping characters by hand. To encode an image or PDF rather than text, encode a file to Base64 reads the bytes directly. The post on formatting, minifying and Base64-encoding JSON privately walks through a typical API payload from start to finish.
Encoding uses the browser's own btoa function after the UTF-8 conversion, entirely inside the open page. What you type is not posted to a server.
Related: Base64 Decoder
Keyboard shortcut
Wrap short UTF-8 or token strings for Base64-typed API fields.
Encode small snippets when a data: URL is the pragmatic option.
Skip opening a shell for a one-off encode during debugging.
Answers for this tool. For site-wide help, open the FAQ hub.
The browser's btoa only accepts characters in the Latin-1 range, so an emoji or a Chinese character throws an error. This encoder converts the text to UTF-8 bytes first and then encodes those bytes, which is also what most server-side libraries do.
No. It is an encoding, not encryption. Anyone can decode it in a second, so never treat a Base64 value as a secret or as a way to obscure passwords and keys.
No, it is one unbroken line. If a format such as PEM or MIME expects lines of 64 or 76 characters, wrap the result with the Base64 Splitter.