URL Encoder / Decoder
Cmd/Ctrl+Enter saves this input to history.
Advertisement
Percent-encode text for safe use in a URL, or decode it back. This is a thin wrapper around the browser's own encodeURIComponent/decodeURIComponent — the same encoding your browser and HTTP libraries already rely on, so output matches what you'd get in application code.
Frequently asked questions
- Is this the same as Base64 encoding?
- No, different purpose entirely. Percent-encoding (what this tool does) escapes characters that aren't safe in a URL — spaces, &, ?, non-ASCII text — using %XX hex sequences. Base64 encodes arbitrary binary data as ASCII text and isn't URL-safe by default (it can contain + and /).
- Why does decoding fail with an error?
- The input has a malformed percent-encoded sequence — a % not followed by exactly two valid hex digits. That usually means the text was already decoded once (a literal % in the content) or was corrupted in transit.
- Should I encode a full URL or just part of it?
- Just the part that needs it — usually a single query parameter value. Encoding an entire URL, including https:// and the domain, breaks it: the : and / that make it a valid URL get escaped along with everything else.
- Is my data uploaded anywhere?
- No. Encoding and decoding happen locally in your browser tab — nothing is sent to a server.
Read the full guide for this tool →
Related tools & guides
Part of Encoding & Decoding Tools
Tools
Guides
- Base64 Encoding Explained (and Where It Silently Breaks)
- Converting Between camelCase, snake_case, and kebab-case: Where Word-Splitting Goes Wrong
- HEX, RGB, and HSL: Converting Between Color Formats
- MD5 vs SHA-256: Which Hash Should You Actually Use
- encodeURIComponent vs encodeURI: Which Characters Get Percent-Encoded
- URL Parsing and Query String Encoding — What the Browser's URL API Does for You
- Base64 vs Base64URL
- URL Slugs: Diacritics, Unicode, and What Gets Stripped
- UUID v4 vs v7
Advertisement