URL Encode / Decode
Percent-encode text for safe use in URLs, or decode an encoded URL back to plain text.
URLs can only safely contain certain characters, so spaces, ampersands and accents have to be percent-encoded (a space becomes %20). URL Encode / Decode converts text into that safe form and decodes encoded URLs back to readable text.
How to use url encode / decode
- 1. Paste text or an encoded URL.
- 2. Choose encode or decode.
- 3. Copy the result.
When to use URL Encode / Decode
Build a safe query string
Encode a value so it can be dropped into a URL parameter without breaking it.
Read an encoded link
Decode a messy %-encoded URL back into plain, readable text.
Debug web requests
Check how parameters are encoded when troubleshooting an API or link.
Encode a value, not the whole URL
Encoding escapes every character except letters, digits and - _ . ! ~ * ' ( ). That includes : / ? & and =, so encoding a full address turns "https://" into "https%3A%2F%2F" and the link stops working. Encode only the value you're putting into a parameter, then add it after the =. Spaces become %20 and non-English letters are written as their UTF-8 bytes: ș becomes %C8%99.
The plus sign
Web forms often write spaces as + in query strings (q=hello+world). Decoding here follows the URL standard and only turns %20 into a space, so a + stays a +. If the text came from a form, replace + with spaces first using Find and Replace. A stray % that isn't followed by two hex digits can't be decoded and is reported as invalid.
Frequently asked questions
Why does a space become %20?
Spaces aren't allowed in URLs, so they're percent-encoded. Many characters get the same treatment to keep the URL valid.
What's the difference from Base64?
URL encoding only escapes unsafe characters for URLs; Base64 re-encodes everything into an A–Z/0–9 alphabet for text-safe transport.
Is my input private?
Yes — it's processed in your browser.