URL Encode/Decode
Encode or decode URLs and query strings instantly. Handle special characters safely in URLs.
Next step
URLs and query strings break easily when they contain spaces, emoji, or reserved characters like &, =, ?, and #. Encoding the right part of the string keeps links safe when you pass them between forms, APIs, redirects, and tracking tools.
Related Articles
JSON API Debugging Checklist: Fast Root Cause IsolationUse this API debugging checklist to quickly isolate malformed JSON, encoding issues, and schema mismatches before they hit production.What is Base64 Encoding? A Practical GuideUnderstand Base64 encoding: what it is, why it's used, and how to encode/decode values for APIs, emails, and data URIs.
Help and details
How to use
- Paste a URL, query value, or plain text into the input field.
- Choose encode or decode mode.
- Turn on query - string mode if you want spaces to become + signs during encoding.
- Copy the converted result.
Privacy and processing
All processing happens in your browser. Your data is never sent to our servers.
Frequently Asked Questions
What is URL encoding?
URL encoding, also called percent - encoding, converts special characters into a safe format for URLs and query strings.
When should I use URL encoding?
Use it when passing text through query parameters, redirects, forms, or API requests that expect URL - safe values.
Is my data sent to your servers?
No. Encoding and decoding happen locally in your browser.
Does this handle international characters?
Yes. UTF - 8 characters such as Korean, Japanese, emoji, and other non - ASCII text are supported.
Should I encode an entire URL?
Usually no. In most cases you only encode parameter values, not the whole URL structure.
What is the difference between URL encoding and Base64?
URL encoding makes text safe for URLs. Base64 is a different encoding scheme for representing binary or text data.
Does this work offline?
Yes. Once the page has loaded, the conversion happens in the browser without sending data anywhere.
Why would I use query - string mode?
Some systems expect spaces to be represented as + instead of %20 when working with form - style query values.