⚡Free Tools

URL Encoder & Decoder with Query-String Editor

Percent-encode or decode text and URLs the right way — component, full URL, HTML form or strict RFC 3986 — then edit query parameters in a table and copy a clean, correctly encoded link.

Input
Output

URL parts and query-string editor

What URL encoding (percent-encoding) does

A URL may only contain a limited set of characters. Letters, digits and - . _ ~ are always safe. Characters such as ? & = # / have a special meaning: they separate the path, the query and the fragment. Everything else — spaces, Hindi, the rupee sign, emoji, quotes — must be written as bytes in the form %XX, where XX is the hexadecimal value of each byte. That is percent-encoding, defined in RFC 3986. A space becomes %20, & becomes %26 and ₹ becomes %E2%82%B9, because it takes three bytes in UTF-8.

Decoding reverses the process. This page does both instantly in your browser. Your URLs never leave your device. That matters because URLs often carry session tokens, e-mail addresses, password-reset codes and API keys.

Component vs full URL: the mistake that breaks links

Most broken links come from choosing the wrong kind of encoding. This tool offers five modes and says what each is for:

ModeLeaves unencodedUse it for
Component (encodeURIComponent)A–Z a–z 0–9 - _ . ! ~ * ' ( )One query value or one path segment, for example a search term or a redirect URL inside ?next=
Full URL (encodeURI)The above plus ; , / ? : @ & = + $ #A whole URL that already has its structure but contains spaces or non-English characters
HTML formA–Z a–z 0–9 * - . _; space becomes +POST bodies and query strings built like a browser form (application/x-www-form-urlencoded)
RFC 3986 strictOnly A–Z a–z 0–9 - . _ ~OAuth 1.0 signatures, AWS SigV4 canonical requests, anything that compares encoded strings byte for byte
PathStrict, but keeps /File paths such as /files/my report (final).pdf

Rule of thumb: if you are putting a value into a URL, use Component. If you have a complete URL that just needs its spaces and Unicode fixed, use Full URL. Using Full URL on a value is the classic bug. A value like a&b=c passes through unchanged and silently creates an extra parameter.

How to use the decoder

  1. Choose Decode and paste the encoded text or URL. The result updates as you type.
  2. Decode + as space is on by default, because form-encoded query strings use + for spaces. Turn it off when a literal plus sign matters, for example in a Base64 value or a phone number such as +91 inside a path.
  3. If the output still contains %XX sequences, the text was encoded twice. That happens when a URL is passed through two systems, such as a tracking link inside an e-mail. Press Decode fully to peel all layers off at once; the status line tells you how many layers there were.
  4. Malformed input does not crash the tool. A stray % or a byte that is not valid UTF-8 is kept as it is, and the status line shows exactly which sequence is wrong and at which character position. In comparison, the browser's own decodeURIComponent throws “URI malformed” and gives you nothing.

The query-string editor

Paste any full URL and the lower panel splits it into protocol, host, port, path and fragment, and lists every query parameter in a table with the decoded key and value. You can then:

Why this tool instead of the usual encoder sites

Common examples

TextComponentForm
hello worldhello%20worldhello+world
a&b=ca%26b%3Dca%26b%3Dc
₹500%E2%82%B9500%E2%82%B9500
नमस्ते%E0%A4%A8%E0%A4%AE%E0%A4%B8%E0%A5%8D%E0%A4%A4%E0%A5%87same
it's (ok)!it's%20(ok)!it%27s+%28ok%29%21

Everyday links that need correct encoding

Paste any of these into the decoder to check what the receiving app will actually see, and use the table to fix a single value safely.

Tips for developers

Sources and standards

Frequently asked questions

What is the difference between encodeURI and encodeURIComponent?

encodeURI keeps the characters that give a URL its structure (: / ? # & = and others), so it is for complete URLs. encodeURIComponent encodes those too, so it is for a single value placed inside a URL. Using encodeURI on a value is a common bug.

Should a space be %20 or +?

Both are correct in different places. In paths and in RFC 3986 encoding a space is %20. In HTML form data (application/x-www-form-urlencoded), which most query strings follow, a space is +. When decoding, this tool treats + as a space by default; you can switch that off.

Why does my URL still contain %25 after decoding?

%25 is an encoded percent sign, which means the text was encoded twice. Press “Decode fully” to remove all layers at once.

How do I encode Hindi or the rupee symbol in a URL?

Use Component mode. Each character is converted to its UTF-8 bytes and every byte is written as %XX, so ₹ becomes %E2%82%B9 and न becomes %E0%A4%A8.

Can I edit query parameters without hand-encoding?

Yes. Paste a full URL and edit keys and values as plain text in the table. The URL is rebuilt with the correct encoding, and you can remove tracking parameters in one click.

Is my URL sent to a server?

No. Encoding, decoding and parsing all happen in your browser, and the page works offline after it loads.

Why does decodeURIComponent say “URI malformed”?

The input has a % not followed by two hex digits, or bytes that are not valid UTF-8. This tool decodes the valid parts, keeps the bad sequence as it is and shows its position.

Keyboard shortcuts

Ctrl + EnterConvert now
Ctrl + Shift + SSwap input and output