My Tool Studio
Developer

URL Encoder / Decoder

A customer pastes a search link into a bug report and half the query string is missing. The culprit is usually an unescaped ampersand or space, and this page sorts it out in both directions. Run url decode to turn %20 and %26 back into characters you can actually read, or url encode a raw value so it survives inside a query parameter. The tool covers url encode and decode with two buttons and nothing else to configure, and because it works locally in your browser, the links you inspect, including ones stuffed with tracking parameters, stay private.

Always freeNo sign upRuns in your browser

How to use

01

Paste the URL or value

Put the raw text or the escaped link into the Input pane. The Try sample button loads a URL with a space and an ampersand so you can watch both change.

02

Choose a direction

Click Encode for a percent-escaped string ready for a query parameter, or Decode to expand the escape sequences. Malformed sequences trigger an error message instead of a wrong answer.

03

Copy and use it

Grab the output with the Copy button and drop it into your address bar, your code, or the bug ticket you're writing up.

Why URL Encoder / Decoder

Common questions

Which characters break a query string?
The usual suspects are &, =, ?, #, +, and spaces, because each has a job in URL syntax. If a user types soap & glory into a search field and you pass it along raw, the server reads glory as a new parameter. Encoding first keeps the value in one piece, which is why url encode online is such a common last step before testing an API call.
Is this the same as encodeURIComponent?
Yes, the Encode button calls exactly that function, so the output matches what url encode javascript searches are after. Decode uses decodeURIComponent. If your code and this page ever disagree, something else in your pipeline is double-escaping the value.
Can I turn a tracking link back into readable text?
That's one of the best uses for url decode online. Marketing and analytics URLs bury the destination under layers of escaped parameters, and decoding works like a link to text converter: paste the monster link, click Decode, and read what it actually says.
Should I encode the whole URL or just one value?
Just the value. Encoding a complete URL escapes the :// and every / in the path, which breaks it. Paste only the piece that goes between = and &, encode it, then place the result into the URL you're building.
Why am I seeing a Malformed URL encoding error?
Decode hit a percent sign that isn't followed by two hex digits, often a literal % in the text or a truncated copy-paste. Fix or remove the stray %, or grab the full link again, and the decode will go through.
Is a url formatter different from decoding?
People searching for a url formatter usually want a long link made legible, and decoding does exactly that by expanding the escapes. This page doesn't restructure or validate the address beyond that, so the output is the same URL, just readable.
Does double encoding cause the %2520 bug?
Yes. Encode a space once and you get %20; encode that result again and the % itself becomes %25, producing %2520. Because this is a single url encode decode page working as one encode decode online utility, you can decode twice in a row to unwind it, then encode exactly once.

More Developer tools

View all