URL Encode/Decode

Need to encode text for use in a URL or decode percent-encoded text back into a readable format? This tool makes it easy to convert between plain text and URL-encoded text, with results updating instantly as you type. Special characters, spaces, and symbols are converted into the appropriate percent-encoded representation, making it useful for working with URL parameters, query strings, web development, and API requests.

Simply enter your text to encode it or paste an encoded string to decode it. Everything is processed directly in your browser, with nothing sent to a server, keeping your input private and under your control.

URL Encode/Decode

Encodes every reserved character — use this for a single value going into a query string or path segment, such as &, ? or spaces.

Plain text

Encoded

Encoding and decoding happen in your browser. Nothing is uploaded.

How to use it

The URL encoder/decoder converts between plain text and percent-encoded URL text in both directions.

Pick a modeUse Component for a single value, or Full URL to keep the structure of a whole address intact.
Type in either boxType plain text on the left to encode it, or paste encoded text on the right to decode it.
Read the result liveThe other box updates automatically as you type.
Copy the resultUse the Copy button beside the encoded box.

Good to know

Nothing is uploaded

Encoding and decoding happen entirely in your browser.

Component vs Full URL

Component mode (encodeURIComponent) escapes everything including &, = and /. Full URL mode (encodeURI) leaves those untouched so a whole address still works.

Unicode-safe

Non-English characters and emoji are percent-encoded correctly using their UTF-8 bytes.

Frequently asked questions

What's the difference between Component and Full URL mode?

Component mode encodes a single piece of data that will be placed inside a URL, such as a query parameter value, so it escapes characters like &, = and / that would otherwise break the URL's structure. Full URL mode encodes an entire address, so it leaves those structural characters alone and only escapes things like spaces.

Why did decoding fail?

The encoded text contains a % that isn't followed by two valid hexadecimal digits, so it isn't a valid percent-encoded sequence.

What do %20 and + both mean?

Both represent a space. %20 is the standard percent-encoding used in URL paths, while + is an older convention specific to query strings and form submissions. This tool uses %20, which is always safe.

Is my text uploaded anywhere?

No. Both encoding and decoding happen locally in your browser.