URL Encode / Decode

Percent-encode or decode URL components or full URIs.

Help Us Improve
4.9 (0)

How to use URL Encode / Decode

Three quick steps — no sign-up needed

  1. Step 1

    Choose Encode or Decode

    Select the direction of conversion.

  2. Step 2

    Pick Component or Full URI scope

    Component encodes a single part; Full URI applies broader encoding rules carefully.

  3. Step 3

    Paste input and convert

    Enter the string and copy the encoded or decoded result.

About URL Encode / Decode

URL Encode / Decode applies percent-encoding so reserved characters travel safely in URLs, or reverses that encoding. Developers searching "URL encode online", "percent encoding", or "decode URI component" need correct handling of spaces, unicode, and query values.

Choose Encode or Decode, then Component or Full URI scope. Component mode is appropriate for a query value or path segment; encoding an entire URL blindly can break scheme separators if misused.

Spaces may become %20 or + depending on context (application/x-www-form-urlencoded). Match the standard your server expects.

An encoding helper - not a URL shortener or crawler.

Benefits of URL Encode / Decode

Encode and decode Both directions supported.
Component vs full URI Safer control over what gets escaped.
Query-safe strings Handle spaces and symbols correctly.
API debugging Fix broken request URLs quickly.

Frequently asked questions

When should I use component encoding?

When encoding a single path segment or query parameter value.

Why is + used for spaces?

Form encoding often uses +; %20 is also common in URLs - know your stack.

Can I encode a full URL?

Use Full URI mode carefully so scheme and host remain valid.

Does this protect against XSS?

No - URL encoding is not HTML escaping.

Is Unicode supported?

Percent-encoding can represent UTF-8 bytes of non-ASCII characters.