URL encode and decode
Encode text so it is safe inside a link or query string, or turn a percent-encoded URL back into readable text. Paste a full link to see its host, path and every query parameter decoded.
Runs in your browser. Links you paste, including any tokens in them, never leave your device and are not stored by EpiFive.
How to use it
- Type or paste your text, a query value or a full URL.
- Choose Query value or path part to encode a single value, or Whole URL to tidy up a complete address.
- Tick Spaces as + for HTML form data.
- Tap Encode or Decode, then copy the result. Use as input lets you run it again, for example to decode a link that was encoded twice.
Examples
price & taxencodes toprice%20%26%20tax.₹encodes to%E2%82%B9, its three UTF-8 bytes.%2520is a space encoded twice: decode it twice to get back to a space.
Related tools
- Base64 encode and decode: Encode or decode Base64 text (UTF-8 safe) and convert files to and from Base64.
- HTML entity encoder and decoder: Escape & < > " for HTML, or decode named and numeric entities such as é and ₹ back to text.
- Slug generator: Turn titles into clean, SEO-friendly URL slugs: lowercase, hyphens, no accents, optional length limit and bulk mode.
- JWT decoder: Decode a JSON Web Token’s header and payload and read its expiry times. Decode only, no verification.
- JSON formatter: Format, validate and minify JSON, with the line and column of any error.
Questions people ask
What is URL encoding?
URL encoding, also called percent-encoding, writes characters that are not allowed or have a special meaning in a web address as a % followed by two hex digits. A space becomes %20, & becomes %26 and é becomes %C3%A9 (its two UTF-8 bytes). This lets any text travel safely inside a link.
Should I encode a query value or the whole URL?
Encode each value on its own with “Query value or path part” (like JavaScript’s encodeURIComponent). It also encodes / ? & = and #, so a value such as “a&b” cannot break the URL. “Whole URL” (like encodeURI) leaves those characters alone and only fixes spaces and non-ASCII text in a complete address.
Is a space %20 or +?
Both appear. In paths and most APIs a space is %20. HTML forms submitted as application/x-www-form-urlencoded use + for spaces in the query string. Tick “Spaces as +” when you build or read form data; leave it off otherwise, because a literal + in a path stays a +.
Why do I get a “malformed” error when decoding?
A % must always be followed by two hex digits. Text like “50% off” is not valid encoded text; the % should have been written as %25. You can also see this error when escapes describe bytes that are not valid UTF-8, for example a URL cut off in the middle of a character.
Is URL encoding a way to hide data?
No. Anyone can decode it, and URLs end up in browser history, server logs and analytics. Never put passwords or API keys in a URL. If you are decoding a link that contains a token, this page does it on your device without sending it anywhere.