Free URL Encoder & Decoder
Runs locallyUpdated October 25, 2026
Encode or decode URL components and query parameters using standard RFC 3986 UTF-8 percent-encoding locally in your browser.
Output
How to use URL Encoder / Decoder
Paste raw text, a query parameter value, or a percent-encoded string into the input box.
Select Encode to convert reserved characters into %XX sequences, or Decode to restore readable text.
Copy the transformed output for use in query strings, redirect rules, or API requests.
Encode and decode URLs with RFC 3986 percent-encoding
URLs can only transmit a restricted set of US-ASCII characters safely across browsers, email clients, and HTTP servers. When a query parameter contains spaces, ampersands (&), question marks (?), or non-English UTF-8 characters, unencoded characters break the URL structure. Use this free URL encoder / decoder to convert strings to and from percent-encoded format instantly in your browser.
Common reserved characters & percent-encoded equivalents
| Character | Purpose in Raw URL | Percent-Encoded Value | Why Encoding Is Needed Inside Parameters |
|---|---|---|---|
(Space) | Invalid in raw URLs | %20 (or + in forms) | Prevents chat apps and email clients from breaking the link at the space |
& (Ampersand) | Separates query parameters | %26 | Prevents an ampersand inside a value from starting a new fake parameter |
= (Equals) | Separates key from value | %3D | Keeps key=value parsers from splitting the parameter value |
? (Question mark) | Starts the query string | %3F | Needed when passing a nested callback or redirect URL inside a parameter |
# (Hash / Fragment) | Starts client-side anchor | %23 | Prevents the browser from truncating everything after # before sending to the server |
/ (Forward slash) | Separates URL path segments | %2F | Encodes slashes when passing a full URL or path inside a single parameter |
Before and after: encoding a nested redirect parameter
If you pass a destination URL containing its own query string inside a ?redirect= parameter without encoding, the & breaks the outer URL:
- Unencoded (Broken):
https://example.com/login?redirect=https://example.com/search?q=seo&page=2 - Component-Encoded (Safe):
https://example.com/login?redirect=https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dseo%26page%3D2
Related URL & campaign utilities
Build clean analytics tracking links with the UTM campaign URL builder, inspect query parameters key-by-key in the URL parser, or generate clean hyphenated permalinks with the text to slug converter.
URL Encoder / Decoder FAQs
?, &, =, #, /), and non-ASCII UTF-8 bytes with a % symbol followed by two hexadecimal digits (for example, a space becomes %20 and & becomes %26).Related Link & URL Tools
More link & url tools and nearby utilities.
UTM Campaign URL Builder
Free UTM builder for Google Analytics 4 (GA4): append standardized utm_source, utm_medium, utm_campaign, utm_term, and utm_content parameters to any URL.
Open tool →Anchor Text Extractor
Extract all <a href> link destinations and visible anchor text from pasted HTML to audit internal linking and anchor diversity.
Open tool →HTML & Broken Link Checker
Find empty hrefs, hash placeholders (#), and javascript: links in pasted HTML, or test up to 15 live URLs for HTTP 200, 301, and 404 status codes.
Open tool →Htaccess Redirect Generator
Generate Apache .htaccess 301 permanent and 302 temporary redirect rules for URL changes, HTTPS enforcement, and domain migrations.
Open tool →
Guides for URL Encoder / Decoder
Step-by-step articles that use this tool.