Developer tool
Encode or decode a URL
URL-encode or decode a component or a full URL with percent encoding in your browser. Unicode and emoji are supported.
Use component mode for query values. Full URL mode keeps : / ? & = # while encoding the rest. Nothing is uploaded.
- Runs locally
- No uploads
- Instant
- Free
Component uses encodeURIComponent. Full URL uses encodeURI so scheme, :, /, ?, &, =, and # stay readable.
How it works
- 01 Paste your data
- 02 Run the action
- 03 Copy the result
Why NEXNARA
-
Private
Your data stays in your browser.
-
Instant
Results appear immediately.
-
No uploads
Nothing is sent to a NEXNARA server.
-
Works anywhere
No installation required.
Learn more
What is URL encoding?
URL encoding (percent encoding) replaces reserved or non-ASCII characters with % sequences such as %20 for a space. Browsers and APIs use it in query strings and path segments.
How to use it
Choose Component for a query value or path segment. Choose Full URL when you already have a complete link and only need spaces and non-ASCII encoded. Decode undoes percent encoding. Swap exchanges the two boxes.
Component vs full URL
Component mode uses encodeURIComponent, which encodes nearly every reserved character. Full URL mode uses encodeURI so : / ? & = # stay in place. Putting a whole URL through component mode would turn it into one opaque value.
Common uses
Encode search terms, Unicode paths, or query parameters before putting them in a link. Decode a copied URL to read the original text. This is not Base64 encoding.
Privacy
Your text stays in the browser. It is not uploaded to NEXNARA and is not saved in cookies, local storage, or a database.
FAQ
What is percent encoding?
Percent encoding represents characters as % followed by two hex digits. A space becomes %20. Non-ASCII text becomes UTF-8 percent sequences.
When should I encode a full URL?
Use Full URL when you already have a complete URL and only need spaces or Unicode encoded. Use Component for a single value that will sit inside a URL.
What is the difference between encodeURI and encodeURIComponent?
encodeURIComponent encodes reserved characters such as &, =, ?, /, and #. encodeURI leaves those structure characters in place so a full URL stays a URL.
What if the encoding is invalid?
Broken sequences such as a lone %, %2, or %GG are reported as Invalid percent encoding. The page does not crash.
Does URL encoding support Unicode and emoji?
Yes. Text is percent-encoded as UTF-8, so Korean, Japanese, Arabic, and emoji round-trip in component mode.
Is my URL uploaded?
No. Encoding and decoding run in this browser only. There is no server upload and no external API.
Is URL encoding the same as Base64?
No. Percent encoding makes text safe in a URL. Base64 encodes arbitrary bytes as ASCII. Use the Base64 tool for data URLs and files.