Free URL Encoder and Decoder Online – Encode URI Component & Query String Parser | TrenTyx

trentyx@local:~/text-encoding/url-encoder $ run url-encoder_

Encode & decode URLs or URI components with live syntax highlighting and automatic query string breakdown. 100% browser-based, no data sent to server.

input.txt
Double-Encoding Warning: Input contains %25. This text may already be URL-encoded. Encoding it again will produce %2525.
output.encoded

Type or paste text on the left to see live output here.

query-params.parsed
Base URL
# Parameter Key Decoded Value Raw Encoded Value

What is URL Encoding (Percent-Encoding)?

URL encoding converts characters into a format that can be safely transmitted over the Internet within URLs. Unsafe ASCII characters (such as spaces, quotes, or ampersands) and non-ASCII Unicode characters are replaced with a % followed by two hexadecimal digits representing their UTF-8 byte value. Using encodeURIComponent is recommended for query string parameters, while encodeURI preserves full URL structures. This tool performs live conversion 100% locally in your browser.

Common Use Cases

  • Building query strings — safely encode user input (spaces, special characters) before appending it to a URL parameter.
  • Debugging broken links — decode a percent-encoded URL to see its original, human-readable form.
  • Parsing query parameters — break down a complex URL into its individual key-value parameters automatically.
  • Fixing double-encoding bugs — detect when a URL has been encoded twice by mistake, causing malformed characters.

Frequently Asked Questions

What's the difference between encodeURI and encodeURIComponent?

encodeURI preserves characters that are structurally part of a URL, like /, :, and ?, making it suitable for encoding a full URL. encodeURIComponent encodes those characters too, making it the correct choice for individual query string values.

What does "double-encoding" mean and why is it a problem?

Double-encoding happens when an already-encoded URL gets encoded again, turning %20 into %2520. This tool warns you when it detects this pattern so you can fix it before it breaks a link.

Why do spaces sometimes appear as "+" instead of "%20"?

The + convention comes from the older application/x-www-form-urlencoded format used in HTML form submissions, while %20 is the standard percent-encoding for a space used elsewhere in URLs.

Is my URL data sent anywhere when I use this tool?

No, all encoding, decoding, and parsing happens locally in your browser — nothing is transmitted to a server.

Related Tools