URL-Tools
URL encode / decode
Try it
Percent-encode or decode query strings and path components safely in the browser.
Loading…
How to use this tool, examples, and related tips.
Paste your string into the input field.
Click Encode to percent-encode special characters, or Decode to convert percent-encoded sequences back to their original characters.
Copy the output for use in URLs, query strings, or API requests.
URL encoding — formally called percent-encoding — replaces characters that are not permitted in URLs with a % followed by their two-digit hexadecimal ASCII code. For example, a space becomes %20, & becomes %26, and = becomes %3D. This is necessary because URLs have a defined syntax where certain characters carry structural meaning (separating query parameters, for instance) and others are simply not valid. URL decoding reverses the process, converting percent-encoded sequences back to their original characters for readability or processing.
Constructing query strings — Encode parameter values that contain special characters before appending them to a URL.
Debugging malformed URLs — Decode a percent-encoded URL to read it clearly and identify where encoding has gone wrong.
Working with OAuth and API authentication — Many OAuth flows require precisely encoded redirect URIs and scope strings.
Handling user input in URLs — Encode user-supplied strings before embedding them in URLs to prevent injection or broken links.
Answers about this tool and how your data is handled.
encodeURI encodes a full URL and leaves structural characters like /, ?, and & intact. encodeURIComponent encodes a single component (e.g., a query parameter value) and percent-encodes those structural characters too. This tool encodes a string as a component — equivalent to encodeURIComponent.
Encode individual components — query parameter keys and values, path segments, fragment identifiers — not the full URL. Encoding the entire URL will break its structure by encoding the ://, /, and ? characters.
No. Encoding and decoding run entirely in your browser. Nothing is uploaded.
Unreserved characters — letters (A–Z, a–z), digits (0–9), and -, _, ., ~ — are never percent-encoded, per RFC 3986.
No. They target different characters and use different syntax. URL encoding uses %XX sequences; HTML encoding uses entity references like &. Use the right tool for the context.
Zuerst dieselbe Kategorie, dann andere Utilities.
URL-Tools
Percent-encode or decode query strings and path components safely in the browser.