Convert text to Base64 or back. Supports Unicode via UTF-8.
Base64 shows up in data URLs, JWT parts, API credentials, email MIME and embedding binary in text. A local encoder avoids pasting secrets into random websites.
DevsDrill encodes and decodes in the browser with Unicode via UTF-8, which matters for accents and non-Latin text. Invalid Base64 input should fail clearly rather than silently corrupting output. Use Swap when you want to round-trip quickly. Remember that Base64 is encoding, not encryption — anyone can decode it.
Common tasks include turning a UTF-8 string into a header value, inspecting a data URL payload, or recovering text from a Base64 blob found in logs. Keep an eye on URL-safe alphabets versus standard Base64 when integrating with JWTs or certain APIs.
Unicode via UTF-8 matters for accents and non-Latin text. Invalid input should fail clearly. Watch for URL-safe alphabets versus standard Base64 when integrating with JWTs or certain APIs. Local conversion avoids pasting API keys into random websites.
Encode or decode when you hit data URLs, JWT segments, Basic auth material, MIME bodies or binary-in-JSON payloads — and you want the conversion to stay on your machine.
Yes. Text is encoded as UTF-8 before Base64.
No. Encoding and decoding are local.
The tool focuses on standard Base64 text workflows with UTF-8. JWT-style Base64URL differences may need manual alphabet tweaks.
This UI is text-oriented. For large binaries use local CLI tools; paste small text payloads here.
Standard Base64 often includes padding. If an API rejects your string, check alphabet and padding rules in its docs.
You can decode segments manually, but the dedicated JWT decoder is clearer for header/payload inspection.
Paste text or Base64 into the input. Choose Encode to produce Base64 from UTF-8 text, or Decode to recover text. Copy output places the result on the clipboard when the browser allows it. Swap exchanges input and output for quick iteration.
Encoding and decoding run locally. Secrets you paste are not uploaded to DevsDrill servers. Still treat Base64 output as sensitive if the source was sensitive — encoding does not hide data.