Text Encoding Converter
Type or paste text, pick an encoding and get the encoded form instantly — or flip on decode mode and turn Base64, percent-escapes, HTML entities or JSON escapes back into plain text. Both directions update as you write, and everything happens in your browser — nothing is uploaded.
What each encoding does
Base64 turns any bytes into a safe block of A–Z, a–z, 0–9, + and / characters — the standard way to embed binary data (images, attachments, API tokens) inside text formats. URL encoding (percent-encoding) escapes characters that have special meaning in web addresses, like spaces and &, so queries travel intact. HTML entities escape markup characters (&, <, >, quotes) so text displays literally inside a page instead of being parsed as tags. JSON escaping wraps text in quotes and escapes the characters JSON forbids in raw form, which is what you need when embedding a string in JSON code.
Unicode handled the right way
Many encoders choke on accents, non-Latin scripts and emoji because they convert characters straight to Base64 one by one. This tool is correct: text is first converted to its UTF-8 bytes and encoded from those, so Olá, mundo! 🚀 round-trips perfectly. In decode mode the bytes are converted back to UTF-8, and an input that is not valid Base64 (bad characters, wrong padding) shows a clear warning instead of producing mojibake.
Najczęściej zadawane pytania
How do I decode Base64 back to text?
Check the decode mode box, keep Base64 as the encoding, and paste the Base64 string in the text field — the decoded text appears in the result field as you paste. Leave decode mode off to encode in the normal direction.
Why do emoji and accents come out broken in other Base64 tools?
Naive encoders feed UTF-16 characters straight into Base64, which mangles anything outside ASCII. Here text is encoded through its UTF-8 bytes, so accents, non-Latin scripts and emoji encode and decode correctly.
Is my text sent to a server?
No. Encoding and decoding run entirely in your browser — there are no server calls, no logging, and your text never leaves your device. That makes it safe for tokens and other sensitive strings.
What is the difference between URL encoding and HTML entities?
Both escape special characters, but for different contexts: URL encoding (e.g. %20 for a space) makes text safe inside web addresses and query strings, while HTML entities (e.g. < for <) make text safe inside HTML markup. Use each one where its format applies.
Konwertery
- Unit Converter — Length, mass, temperature & more
- Roman Numeral Converter — Numbers ↔ Roman numerals
- Number Base Converter — Binary, octal, decimal, hex & any base
- Unix Timestamp Converter — Unix time ↔ date & time
- What Is My IP — Your IP, location & ISP on a map