URL Encoder / Decoder
Encode text for safe use in URLs or decode percent-encoded strings back to readable text. Supports component and full-URL encoding.
How to use URL Encoder / Decoder.
- 1
Paste your text or URL into the input area
- 2
Click 'Encode Component' for query-string values, or 'Encode URL' to encode a full URL while keeping :// and ? intact
- 3
Click 'Decode' to convert a percent-encoded string back to readable text
- 4
Click 'Copy' to copy the result to your clipboard
Why use this tool.
Build safe query strings with special characters, spaces, and non-Latin text
Debug percent-encoded URLs from logs, analytics, and redirect chains
Two encoding modes: component encoding for parameter values, full-URL encoding that preserves structure
100% client-side — URLs with tokens or session IDs never leave your browser
No signup or installation required
About URL Encoder / Decoder.
True Tool Deck's URL Encoder / Decoder is a free online tool for percent-encoding text so it's safe to use in URLs, and for decoding encoded URLs back into readable form. Developers and marketers hit this constantly: building query strings with special characters, debugging UTM-tagged links, reading percent-encoded values out of server logs, or fixing double-encoded URLs from redirect chains. The tool offers both component encoding (encodeURIComponent) for parameter values and full-URL encoding (encodeURI) that preserves URL structure, with correct UTF-8 handling for international characters. Like every True Tool Deck utility, it runs 100% client-side — URLs containing session tokens or private parameters never leave your device.
Frequently asked questions.
What is URL encoding?
URL encoding (percent-encoding) replaces characters that aren't allowed in URLs with a % followed by their byte value in hexadecimal — a space becomes %20, an ampersand becomes %26. It ensures special characters in parameters don't break the URL's structure.
What's the difference between 'Encode Component' and 'Encode URL'?
'Encode Component' (encodeURIComponent) encodes every special character including /, ?, and & — use it for individual query-string values. 'Encode URL' (encodeURI) preserves characters that are part of URL structure like ://, ?, and & — use it to safely encode a complete URL.
Why do spaces sometimes appear as + instead of %20?
In query strings, the older application/x-www-form-urlencoded format represents spaces as +. Modern percent-encoding uses %20. Both are decoded as a space by servers; this tool produces the standard %20 form.
Does this handle non-English characters?
Yes. Characters like é, ü, 中, or emoji are encoded as their UTF-8 byte sequences (é becomes %C3%A9), which is the standard all modern browsers and servers expect.
Is my URL sent to a server?
No. All encoding and decoding runs in your browser with JavaScript. URLs containing tokens, session IDs, or private parameters are never transmitted anywhere.