Skip to content

URL Encoder / Decoder

Percent-encode text for one part of a URL, or a whole URL while keeping its structure — and decode them back. Handles Hindi, emoji and repeated query parameters, and flags malformed escapes instead of guessing.

FreeRuns in your browserNo sign-up
Action
What to convert

Component mode encodes every reserved character (/ ? & = # + and more), so the text is safe as ONE part of a URL — such as a query value or a path segment. Spaces, tabs and line breaks are kept exactly. URL encoding is not encryption — anyone can decode it, so it doesn’t protect passwords or secrets.

0 characters · 0 bytes (UTF-8)

Up to 5 MB. Ctrl + Enter (⌘ + Enter) to encode.

Empty

Your text is processed in your browser and is not sent to our servers.

How to use URL Encoder / Decoder

  1. 1

    Choose what to convert

    Pick Encode or Decode, then “URL component” for a single value (like a search term) or “Full URL” for a complete link.

  2. 2

    Paste your text or URL

    Enter up to 5 MB. Full URLs need a scheme such as https://. “Load example” fills in a sample.

  3. 3

    Convert and copy

    Select Encode or Decode, check the notes and URL parts, then copy the output or use it as the input to convert it back.

Frequently asked questions

What is URL encoding?

URL encoding (percent-encoding) replaces characters that aren’t allowed in URLs with % and their UTF-8 bytes in hexadecimal — a space becomes %20 and “न” becomes %E0%A4%A8.

Should I encode a URL component or the full URL?

Encode a component when you’re building a URL from pieces — for example a search term for ?q=. Component encoding also encodes / ? & = # and +, so the value can’t break the URL. Use full URL mode to clean up a complete link: it keeps the structure and encodes only what isn’t allowed in each part.

Why isn’t “+” decoded as a space?

In URL encoding “+” is a plus sign; only HTML form data uses “+” for spaces. Turn on “Decode + as a space” when decoding form data or query strings that came from a form.

Why are some characters still encoded after decoding a full URL?

Decoding %2F in a path, or %26 and %3D in a query value, would turn data into new path segments or parameters and change what the URL means. Those escapes, %25 and invisible characters stay encoded so the decoded URL still points to the same place.

Is URL encoding a way to hide or secure data?

No. URL encoding isn’t encryption — anyone can decode it. Don’t put passwords or secrets in URLs.

Is my data sent anywhere?

No. Encoding and decoding happen in your browser, so your text and URLs stay on your device.