Micro Tool Yard logo
Tools
Result
Ad Slot

How it works

  1. Choose Encode or Decode

    Encode plain text/URLs into percent-encoded form, or decode percent-encoded text back.

  2. Pick Component or Full URL

    Component mode escapes every reserved character; Full URL mode preserves URL structure like :// and ?.

  3. Copy the result

    The output updates as you type and copies to your clipboard in one click.

URL Encode / Decode converts text to and from percent-encoding — the %XX escape sequences that let arbitrary characters (spaces, ampersands, non-ASCII text) travel safely inside a URL, which otherwise only reserves a specific set of characters for its own structure.

Component mode escapes everything that isn't valid inside a single URL segment or query-string value, which is the right choice whenever you're encoding one piece of data (like a search term) that will be inserted into a URL you're building. Full URL mode assumes the input is already a complete, structured URL and only escapes characters (like spaces) that aren't valid anywhere in a URL, leaving the delimiters that define its structure — ://, ?, &, =, # — untouched.

Mixing the two up is a common source of broken links: encoding a whole URL with Component mode escapes its own :// and ? into unusable garbage, while encoding a single value with Full URL mode fails to escape an & or = inside it, letting that value accidentally inject extra query parameters.


FAQ

What's the difference between Component and Full URL mode?
Component mode (encodeURIComponent) escapes every character that isn't safe inside a single query-string value, including &, =, ?, and /. Full URL mode (encodeURI) assumes the input is already a complete URL and leaves structural characters like ://, ?, &, =, and # untouched, only escaping things like spaces.
When should I use Component mode?
Use Component mode when encoding a single value that will be placed inside a URL — like a search query or a redirect target — since it safely escapes characters (such as & or =) that would otherwise be misread as part of the URL's own structure.
Why does decoding sometimes show an error?
Percent-encoding represents each byte as %XX. If the input has a stray % not followed by two valid hex digits, or represents an incomplete multi-byte UTF-8 sequence, decoding fails — that usually means the text wasn't actually percent-encoded, or was truncated.
Is my data sent anywhere?
No. All encoding and decoding happens locally in your browser using native JavaScript URI primitives.