What's the difference between Component and Full URI encoding?

Component encoding (encodeURIComponent) escapes every reserved character and is meant for individual values like a query parameter. Full URI encoding (encodeURI) preserves URL-structural characters like :, /, ? and & since they're already valid in a complete URL.

Why does my URL look broken after encoding?

If you encode a full URL using Component mode, characters like : and / get escaped too, which breaks the URL structure — switch to Full URI mode for complete URLs.

URL Encoder / Decoder

Percent-encode or decode URLs and query string components.

INPUT

OUTPUT

Processed 100% in your browser — nothing you enter here is ever uploaded.

Common use cases

Building a query string with special characters

Turn a search phrase with spaces or symbols into a safe value you can append to a URL's query string.

Decoding a redirect URL from server logs

Server logs often show percent-encoded redirect targets — decode one to read the actual destination URL.

Sharing a link with non-English characters

Encode a URL containing accented letters or non-Latin scripts so it pastes correctly into any app or document.

How to use the URL Encode/Decode

Choose Encode or Decode, then pick "Component" for a single query value or "Full URI" for an entire URL.

Type or paste your text — the result updates live as you type.

"Component" encoding escapes every reserved character (use this for query string values like search terms).

"Full URI" encoding leaves characters like : / ? & untouched since they're structurally part of a URL.