URL Encoder / Decoder

Last updated:

Percent-encode or decode URLs and query string values instantly. Switch between full URL mode, which preserves structure, and component mode, which safely escapes reserved characters in a single parameter.

Runs in your browser. Nothing is uploaded.

Refer a Client, Earn a Reward

Introduce a client who needs a website or help getting found. We handle the proposal, delivery and support directly with your client. One-off projects pay 10%, with a $100 minimum. Monthly retainers pay 10% each month for the first six months.

Refer a client

See 36 client websites

How the URL Encoder Works

The tool uses the browser's native percent-encoding functions for accurate, standards-compliant results.

  1. Choose a mode, Encode to make a string URL-safe, or Decode to read it back.
  2. Pick a scope, full URL keeps : / ? & = working, component mode escapes them.
  3. Convert instantly, results update as you type, with UTF-8 handling for any language.
  4. Copy or chain, copy the output or feed it back to reverse the operation.

Why URL Encoding Matters

Correct encoding keeps links, tracking, and integrations working reliably.

  • Working links, spaces and symbols in URLs break navigation unless they are encoded.
  • Accurate analytics, properly encoded UTM and query parameters keep campaign data clean in GA4.
  • Accurate URL construction, encode a redirect target as a parameter value so reserved characters do not break the surrounding URL. Separately validate allowed destinations; encoding does not prevent an open redirect.
  • Reliable APIs, encode values before placing them in query strings so reserved characters do not corrupt requests.

Messy, broken, or double-encoded URLs can quietly leak ranking signals. Our SEO services include a full technical URL and crawl audit.

Common Percent-Encodings

CharacterEncodedCharacterEncoded
space%20&%26
?%3F=%3D
/%2F#%23
+%2B@%40

URL Percent-Encoding Reference

Reserved characters carry structural meaning in a URL and must be percent-encoded when used as data. Unreserved characters (letters, digits, and - _ . ~) never need encoding. The table below lists the most common reserved characters and their encoded values.

Character Encoded Notes
space%20Always safe; in form data it may appear as + instead.
!%21Sub-delimiter; encode inside a value.
#%23Reserved; starts the fragment, so encode in data.
$%24Sub-delimiter; encode inside a value.
&%26Reserved; separates query parameters.
'%27Sub-delimiter; encode inside a value.
(%28Sub-delimiter; encode inside a value.
)%29Sub-delimiter; encode inside a value.
+%2BEncode to preserve a literal plus, since it can mean a space.
/%2FReserved; separates path segments.
:%3AReserved; separates scheme and port.
;%3BSub-delimiter; encode inside a value.
=%3DReserved; assigns a query parameter value.
?%3FReserved; starts the query string.
@%40Reserved; separates userinfo from host.

Next steps

URL Encoder / Decoder related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Base64 Encoder / Decoder

HTML Entity Encoder / Decoder

UTM Builder

Technical SEO Audit: What to Check and How to Fix It

On-Page SEO Checklist for 2026

How to Check and Test Your Robots.txt File: The Complete Guide

URL Encoder / Decoder: FAQ

What is the difference between Full URL and Component mode?
Full URL uses the browser's encodeURI and decodeURI functions, which preserve URL structure such as slashes and separators. Component mode uses encodeURIComponent and decodeURIComponent, which escape text intended for a single query value, path segment, or parameter.
Which mode should I use for a query parameter value?
Use Component mode for the value itself, then place that encoded value into the URL. Encoding an entire URL as a component will also escape its structural characters, which is usually not what a browser address needs.
Why does decoding sometimes return an error?
A percent sign must be followed by a valid two-digit hexadecimal byte sequence, and encoded bytes must form valid text. Incomplete or malformed sequences cause the browser decoder to reject the input instead of guessing.
Why did percent signs become %25 after encoding?
The encoder does not detect whether text was encoded previously. Encoding an already encoded percent sequence escapes the percent sign again, so decode once or start from the original unencoded value to avoid double encoding.
How are spaces and Unicode characters handled?
The native browser URL functions encode Unicode as UTF-8 percent sequences. Spaces become %20 here; this tool does not convert them to the plus-sign convention sometimes used by HTML form query strings.
What does Swap do in the URL encoder?
Swap moves the current output into the input and switches between Encode and Decode. It is handy for reversing a result, but it replaces the previous input field value.
Does decoding a full URL reveal every encoded reserved character?
Not always. Full URL decoding keeps escapes that would become reserved URL syntax in place, while Component mode decodes those characters. Choose the mode based on whether you are handling a whole URI or one contained value.
Is the URL or text sent anywhere?
No. Encoding, decoding, swapping, and copying use native functions in your browser, and the entered value is not submitted by this tool.