URL encode/decode
Percent-encode or decode a URL/string.
URL encode/decode percent-encodes text so it's safe to use inside a URL (like a query parameter value), or decodes a percent-encoded string back to its original form, updating automatically as you type.
How to use
- Choose Encode or Decode.
- Paste your input — the result updates automatically.
Common use scenarios
- Encoding a value containing spaces or special characters before putting it in a URL query string.
- Decoding a URL-encoded parameter to see its actual, readable content.
- Preparing a search term or user input for safe inclusion in a link.
- Debugging a URL that contains unexpected percent-encoded characters.
✓Content & verification reviewed: 2026-08-25
How we verify URL encode/decode
How to confirm the encoded or decoded result is exactly right.
This encodes individual values, not a full URL
This tool percent-encodes a single value (like one query parameter's worth of text) — it's not meant to encode an entire URL including the protocol, domain, and path separators, which would incorrectly encode characters like "://" and "/" that need to stay literal.
Round-trip check
Encode some text with special characters or spaces, then paste the result into Decode mode — you should get back exactly your original text, confirming the encoding is reversible and correct.
Spaces become %20 or +, depending on context
Standard percent-encoding turns a space into "%20", while the older "application/x-www-form-urlencoded" convention (used in some form submissions) uses "+" instead — check which convention your target system expects if spaces aren't decoding as you expect.
Before you rely on the result
- You're encoding a single value (like a query parameter), not trying to encode an entire URL at once.
- You've confirmed a round-trip (encode then decode) returns your original text.
- If spaces matter, you know whether your target system expects "%20" or "+" encoding.
- You've checked the decoded output looks correct and readable before using it further.
Who this is for
- Developers encoding values before inserting them into URL query strings.
- Anyone decoding a URL-encoded parameter to see its actual content.
- People preparing search terms or user input for safe inclusion in a link.
- Anyone debugging a URL containing unexpected or garbled percent-encoded text.
Real-world examples
Encoding a search query for a URL
A developer needs to build a search URL containing a user's query text with spaces and special characters, and encodes just that value before inserting it into the query string.
Decoding a mysterious URL parameter
Someone sees a URL with a parameter full of % characters and decodes it to reveal the actual, readable text it represents.
Debugging a broken link
A developer investigates a link that isn't working as expected and decodes its parameters to check whether special characters were encoded correctly.
Limitations
- This encodes individual values (e.g. a query parameter), not a full multi-part URL.
Frequently asked questions
Can I encode a whole URL with this tool, including "https://"?
You can, but it's usually not what you want — that would encode the "://" and "/" separators too, breaking the URL structure. This tool is meant for encoding individual values like a single query parameter.
Why did a space turn into "%20" instead of "+"?
That's standard percent-encoding behavior. The "+" convention for spaces comes from an older, form-specific encoding standard — if your target system expects "+", you may need to substitute it manually.
Why did decoding fail on my input?
The input needs to be a validly percent-encoded string — a stray "%" not followed by two valid hex digits, or a string that was never actually encoded, will cause decoding to fail with an error rather than guessing at the intent.
Does this handle Unicode characters like emoji or CJK text?
Yes — non-ASCII characters are encoded as their UTF-8 byte sequence, each byte represented as a percent-encoded hex pair.
🔒 Runs in your browser — nothing is uploaded. Results are for reference only; see the disclaimer. Last updated: 2026-08-25
Subscribe for updates
New tools and tips, straight to your inbox. No spam, unsubscribe anytime.