Encode non-ASCII JSON text for a test payload or decode a Base64 string without losing Korean or emoji characters.
Never paste production passwords, live JWT access tokens or private customer records.
No uploads, cookies, tracking or third-party scripts. Your input stays in browser memory.
Ready. Enter a test value.
Classic btoa/atob can corrupt or reject Unicode strings because Base64 operates on bytes, not text characters. This tool explicitly uses UTF-8 for input and output, rejects malformed padding and explains binary data that isn't valid UTF-8.
Choose Encode or Decode, paste disposable text, then click Run. The result can be copied into your test request. Base64 is an encoding, not encryption or confidentiality protection.
Text mode only. This UI does not decode arbitrary binary files, PEM certificates or data URLs. It never submits input or output to any API, but you should still avoid placing confidential secrets in shareable URLs.
Yes. The encoder converts Unicode text to UTF-8 bytes before Base64. The decoder requires valid UTF-8 output.
No. It only changes representation. Anyone can decode it; use proper encryption and credential handling.
Not in this text-only tool. Binary files may not be UTF-8 and are intentionally rejected.