URL Encode & Decode Online
Encode a URL or query string for safe links, or decode %20 / %40 text instantly. Parse query params and rebuild the URL. 100% in your browser, no signup.
Query-string parser
Paste a full URL to inspect protocol, host, path, and decoded query pairs. Edit pairs and rebuild the URL. Encode/decode above is for percent-encoding text; this panel is for structure.
Encode and decode vs full URL parse
Percent-encoding (encode/decode) turns unsafe characters into %XX sequences so values survive inside query strings, redirects, and API calls. Use it when you have a raw string like a search term or email and need a URL-safe form, or when you receive %20-style text and want the readable original. It does not explain the structure of a link.
The query-string parser takes a complete URL and shows protocol, host, path, and each decoded key/value pair in a table you can edit. Rebuild when you need a corrected link without hand-editing encoded ampersands. For binary or data-URI work, use Base64. To checksum a payload or file after transfer, use the Hash Generator.
How this compares to typing encodeURIComponent in DevTools
Browser consoles can encode one string at a time, but they do not show a decoded query table or let you rebuild a long tracking URL after editing UTM parameters. This page combines encode, decode, and full URL parse in one place, with copy buttons for each step. Nothing is sent to Instant Tools servers. For API payloads that need JSON validation before you embed them in a query string, use the JSON Formatter first, then encode the result here.
Common Use Cases
Query Parameters
name=John Doe&city=New Yorkname=John%20Doe&city=New%20YorkSpecial Characters
hello@world.com?ref=top#sectionhello%40world.com%3Fref%3Dtop%23sectionAbout URL Encoding
- • URL Encoding: Also known as percent-encoding, converts special characters to a format that can be transmitted over the Internet
- • Why encode? URLs can only contain ASCII characters. Special characters need to be encoded
- • Common encodings: Space → %20, @ → %40, # → %23, ? → %3F, & → %26
- • Use cases: Query parameters, API requests, form data, email addresses in URLs
- • Reserved characters: Characters like :, /, ?, #, [, ], @, !, $, &, ', (, ), *, +, ,, ;, = have special meaning in URLs
How to Use
- 1Choose between 'Encode' or 'Decode' mode using the toggle button
- 2Paste or type your URL or text in the input field
- 3Click 'Process' to encode or decode the text
- 4Review the output in the result area below
- 5Click 'Copy' to copy the result to your clipboard
- 6Use 'Swap' to reverse the operation quickly
URL Encoding Examples
Simple URL with Spaces
hello world → hello%20worldSpaces are encoded as %20
Email in URL
user@example.com → user%40example.comThe @ symbol is encoded as %40
Query Parameters
search?q=cats & dogs → search?q=cats%20%26%20dogsSpaces and & symbols must be encoded in query strings
URL Encoding Tips
- •Always encode URL parameters before sending API requests
- •Use decoding to make URLs readable and understand query parameters
- •Double-encoding can cause issues - avoid encoding already encoded URLs
- •Some characters like '/', ':', '?' have special meanings in URLs
- •Form data in POST requests should be URL-encoded
- •Email addresses in mailto: links should be encoded
- •Test your encoded URLs to ensure they work correctly
Related Tools
Base64 Encoder/Decoder
Encode and decode Base64 strings and files
Hash Generator
Generate MD5, SHA-1, SHA-256 hashes
UUID Generator
Generate unique identifiers
JSON Formatter
Format and validate JSON data
Text Diff
Compare two texts and see differences
Prompt Diff
Compare system prompts and agent rules side-by-side
Frequently Asked Questions
What is URL encoding (percent encoding)?
URL encoding converts unsafe characters in URLs to %XX hex codes so links transmit correctly. Spaces become %20, @ becomes %40, and non-ASCII characters get UTF-8 percent sequences. This free tool encodes and decodes instantly in your browser.
When should I encode a URL or query string?
Encode whenever you pass user input in query parameters (?q=...), form GET requests, redirect URLs, or API calls with special characters. Always encode values (not the whole URL structure) before appending to query strings.
What's the difference between URL encoding and Base64?
URL encoding makes text safe inside URLs and query strings. Base64 encodes binary data as ASCII text for attachments or data URIs. Use this tool for percent-encoding; use our Base64 tool for file or blob encoding.
Can I decode a double-encoded URL?
Yes. Run decode once per encoding layer. If a parameter was encoded twice, decode twice. Watch for %2520 (double-encoded space) in broken links.
How do I decode %20 or other percent codes in a URL?
Switch to Decode mode, paste the encoded string (for example hello%20world or a full query value), and click Decode. Each %XX sequence becomes the original character. Run decode again if the link was encoded twice.
Should I encode the whole URL or only the query value?
Encode only the value part of each query parameter, not the scheme, host, slashes, or ? and & separators. Use the query-string parser below when you need to inspect or rebuild a full link with many parameters.
Is my data private?
Yes. Encoding and decoding run 100% client-side. Nothing is sent to a server.
What does the query-string parser do?
Paste a full URL to see protocol, host, path, and a table of decoded query key/value pairs. Edit the pairs and rebuild the URL. That is separate from encode/decode, which percent-encodes text for safe use inside URLs.