URL Encode / Decode
Percent-encode and decode text for URLs — plus a parser that breaks any URL into its parts.
URL encoding (percent-encoding) replaces characters that are unsafe in URLs with %XX escapes. You need it whenever a query-string value contains spaces, &, =, #, or non-ASCII text — search terms, redirect URLs, callback parameters, API filters. Choose between encodeURIComponent for individual values and encodeURI for complete URLs, and the output updates live as you type.
There is also a URL parser: paste any full URL and see its host, path, hash, and every query parameter decoded into a readable table — much faster than squinting at a 400-character tracking link. Everything runs locally in your browser, so URLs containing session tokens or API keys are never sent anywhere.
How to URL-encode or decode text
- 1
Pick Encode or Decode and choose Component (for values) or Full URL mode.
- 2
Paste your text — the result appears instantly.
- 3
Copy the output, or paste a whole URL into the parser to inspect its query parameters.
Why use Nofolo’s url encode / decode?
Two encoding modes
encodeURIComponent escapes everything for query values; encodeURI preserves :, /, ?, and & for whole URLs.
Live both ways
Encode or decode instantly as you type — no convert button.
URL parser
Break a full URL into protocol, host, path, hash, and decoded query parameters.
Unicode correct
Non-ASCII characters become UTF-8 percent sequences (é → %C3%A9) and decode back losslessly.
Readable errors
Malformed percent sequences are reported clearly instead of failing silently.
Private
Nothing you paste is transmitted — safe for URLs carrying tokens or IDs.
Frequently asked questions
What is the difference between encodeURI and encodeURIComponent?
encodeURIComponent escapes every reserved character, including /, ?, =, and &, so use it for individual query-string values. encodeURI leaves URL structure characters intact, so use it to clean up a complete URL without breaking it.
Why are spaces sometimes + and sometimes %20?
%20 is the percent-encoding of a space. The + convention comes from the older form-urlencoded format used in query strings. This tool encodes spaces as %20; when decoding, %20 always means space, while + only means space in form-encoded data.
How are characters like é or ₦ encoded?
They are first converted to UTF-8 bytes, and each byte becomes a %XX escape — é becomes %C3%A9. Decoding reverses this automatically.
Why does decoding fail with a malformed URI error?
The input contains a % that is not followed by two hex digits (for example a lone % or %ZZ). Fix or re-encode stray percent signs and try again — the error note points this out when it happens.
Are the URLs I paste logged anywhere?
No. Encoding, decoding, and parsing all happen in your browser using native JavaScript functions. URLs with session tokens or API keys never leave your device.
Related tools
Base64 Encode / Decode
Encode text or files to Base64 — and decode back — UTF-8 safe, with a URL-safe option.
Slug Generator
Turn titles into clean, SEO-friendly URL slugs — accents and stop words handled.
JSON Formatter
Format, validate, and minify JSON with instant error pinpointing.
UUID Generator
Generate cryptographically random UUID v4s — one or a thousand — with code-ready formatting.