Encoding & decoding

Encode and decode Base64, URL encoding, hex, HTML entities, JSON strings, JWT and query strings — free, instant and 100% local.

• Text to Base64 — Safe in a Header or a Body Encode text as Base64, with an optional URL-safe variant. The text becomes UTF-8 bytes first, so accents and emoji arrive on the other side intact.
• Base64 to Text — Read What a Blob Says Decode Base64 back to text. Line breaks, missing padding and the URL-safe alphabet are all accepted, because that is how Base64 actually arrives.
• URL Encode — A Value That Survives the Trip Percent-encode text for a URL: space becomes %20 and every reserved character is escaped, so the value reaches the server as you wrote it.
• URL Decode — Read the Parameters of a Link Decode percent-encoded text back to readable form. The plus sign is kept as a plus, which is right for URLs and wrong for form data — told apart here.
• Text to Hex — See the Invisible Character Show text as its UTF-8 bytes in hexadecimal, space-separated. The byte count is usually the surprise, and the stray byte is usually the answer.
• Hex to Text — Paste a Dump However You Got It Decode hexadecimal bytes back to UTF-8 text. Spaces, commas, colons, 0x prefixes and capitals are all accepted, because dumps come in every shape.
• HTML Escape — Text That Renders as Text Escape text for HTML. The five structural characters become named entities and everything above ASCII a numeric reference that works on any page.
• HTML Entities to Text — Read a Scraped Snippet Decode HTML entities back to characters. Numeric references are all supported, and an unknown name stays visible so you can see what it was.
• Text to JSON String — Paste It Into a Payload Turn text into a JSON string literal, quotes included. Two invisible line terminators are escaped as well, so the value pastes into curl or a fixture.
• JSON String to Text — Read the Value Inside Decode a JSON string literal back to text. Surrounding quotes are optional, and a refusal names what is wrong and where, so you can fix it.
• JWT to JSON — Read the Claims Inside Decode a JWT header and payload, signature unchecked. You read exp, iss and the scopes, which is usually what tells you why a token was refused.
• Query String to JSON — Paste the Whole URL Turn a URL query string into JSON. Paste the whole address if you like: the parameters come out as an object you can read line by line.
• JSON to Query String — Ready for the URL Convert a flat JSON object into a URL query string. Percent-encoding is handled and arrays become repeated keys — paste it after the question mark.
• XML Escape — Text That Stays Inside the Tag Replace the five XML markup characters with their entities, so your text survives inside an element or an attribute and the document still parses.
• XML Unescape — Read an Escaped Snippet Decode the five XML entities and numeric character references back to text, in a single pass, so you read what the document actually carried.
• JavaScript Escape — Paste It Into a Literal Escape text for a JavaScript string literal: backslashes, all three quote styles and control characters, so the line compiles wherever you drop it.
• JavaScript Unescape — Read a Literal From a Bundle Decode a JavaScript string literal back to plain text: named escapes, \uXXXX, \u{...}, \xNN and surrogate pairs all come back as characters.
• Java Escape — Safe in an ASCII-Only Source Escape text for a Java string literal. Every non-ASCII character becomes \uXXXX, so the result survives an ASCII-only source or a .properties file.
• Java Unescape — Read a Literal From Source Decode a Java string literal back to text, including \uXXXX and surrogate pairs, so a line lifted out of a .java file becomes readable again.
• C# Escape — A Literal That Compiles as Is Escape text for a regular C# string literal, including the \a, \v and \0 sequences specific to .NET, so the line compiles where you paste it.
• C# Unescape — Read a Literal From Your Code Decode a C# string literal back to text: the named escapes C# adds over Java, plus \uXXXX, \u{...} and \xNN, all turned back into characters.
• CSV Escape — A Field That Keeps Its Column Quote a CSV field only when RFC 4180 requires it, doubling any inner quotes. Pick your delimiter, and the field lands in one cell, not three.
• CSV Unescape — Read the Cell as It Was Written Undo RFC 4180 field quoting: drop the enclosing quotes and turn each doubled quote back into one, so you see the value a spreadsheet stored.
• SQL Escape — A Literal for the Query You Type Double the single quotes and wrap the result: a complete ANSI SQL string literal, ready to paste into the query you are writing by hand in a client.
• SQL Unescape — Read the Value in a Query Undo ANSI SQL quoting: drop the enclosing single quotes if present and turn each doubled quote back into one, so you see the value as stored.