URL Encode / Decode
Encode or decode URL strings instantly by pasting text into the input field.
This tool supports percent-encoding commonly used in URLs, making it easy to convert special characters into a safe format
or restore encoded strings back to readable text.
It is useful for building query parameters, checking API request URLs, and debugging encoded values found in logs or configuration files.
With a single click, you can switch between encoding and decoding
and view the result immediately.
All processing is performed locally in your browser.
No input text or results are sent to any server, ensuring fast performance and privacy-safe usage.
URL parts
This does not look like a URL.
Query parameters (editable)
GuideHow to use & features
- Enter text at the top and click Encode or Decode to transform it.
- Review how spaces and special characters change, then copy the output for reuse.
- Long query strings are supported; very large inputs may take a moment to process.
- All conversions run locally with no network requests.
SamplesSample input & output
URL-encode a query
https://example.com/search?q=open api&lang=en
https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dopen%20api%26lang%3Den
FAQFAQ
How does it encode?
With JavaScript's `encodeURIComponent`, as UTF-8 percent-encoding (like `%E3%81%82`). Non-ASCII text and emoji are converted per UTF-8 byte.Which characters are left unchanged?
Letters, digits and `-` `_` `.` `!` `~` `*` `'` `(` `)`. Other symbols, including `/`, `?`, `&`, `=`, `:`, `+` and spaces, are encoded.Is a space `%20` or `+`?
`%20`. It does not become `+` as in the form submission format (`application/x-www-form-urlencoded`). On decode, `+` stays as it is rather than turning into a space.Can I enter a whole URL?
Not recommended. The `:` and `/` in `https://`, plus `?`, `&` and `=`, are all encoded and the URL stops working. Encode only the value part of a query parameter.When does decoding fail?
A truncated percent sequence such as `%E3%81`, or a `%` not followed by hexadecimal digits, gives a "Decode failed" error.Does it support Shift_JIS or EUC-JP?
No. Only UTF-8. A Shift_JIS value such as `%82%A0` from an older site is not decoded correctly.
Use casesCommon use cases
Encoding a query parameter value
Make a search term or message containing non-ASCII text, spaces, `&` or `=` safe to pass as a URL parameter.Passing a redirect URL as a parameter value
Encode the value when you pass another URL in `redirect_uri=`, `next=` and similar.Making `%E3%81...` in logs readable
Turn long percent-encoded strings from access logs or the address bar back into the original text.Checking before passing to curl or an API client
Confirm that values for `-d` or a query are correctly encoded before sending.
NotesNotes & limitations
Do not use it on a whole URL
`:`, `/`, `?`, `&` and `=` are encoded too, breaking the URL structure. Use it only on parameter values.`+` and `%20` are different things
This tool encodes a space as `%20` and does not turn `+` back into a space on decode. For form-style data (where `+` means a space), change `+` to `%20` before decoding.Do not encode twice
Encoding an already encoded string turns `%` into `%25`, giving values such as `%2520`.Non-UTF-8 character encodings are not supported
Values encoded in Shift_JIS or EUC-JP cannot be decoded correctly.
AboutAbout this tool
URL Encoder and Decoder
URLs often need special characters, spaces, non-English text, and symbols to be percent-encoded. This URL encoder and decoder helps you convert readable text into URL-safe strings and decode encoded values such as %20, %2F, or UTF-8 sequences.
Common use cases
- Debug query strings: Decode parameters from tracking links, API requests, or redirects.
- Prepare safe URLs: Encode search terms, callback URLs, filenames, and form values.
- Inspect copied links: Understand what a long encoded URL actually contains.
Encoding note
Different contexts encode spaces and reserved characters differently. A value that is safe in a query parameter may not be safe in a path segment, so check the exact place where the value will be used.
Articles for this tool
How to URL Encode and Decode Strings for APIs and Query Parameters
Learn what percent encoding means, when to encode URLs, and how to inspect encoded query strings safely during API and tracking-link debugging.
How to Convert URL Parameters to JSON for UTM and API Debugging
Turn long query strings into readable JSON so you can review UTM tags, API filters, duplicated keys, and encoded values more easily—with concrete examples.
URL Mechanics and Parameter Analysis: From Encoding to JSON Conversion
Explore the structure of URLs, the necessity of Percent-Encoding, and efficient ways to handle complex query parameters in web development.
curl Options List: -X, -H, -d and Windows curl.exe
curl options by purpose: -X, -H, -d, -F, -o, -L, -k, -w, timeouts and retries. How -d differs from --data-raw, the @ file prefix, and curl.exe quoting.
Encoding vs Hashing vs Encryption: The Difference and When to Use Each
Base64 encoding, SHA-256 hashing and encryption are constantly confused but serve different purposes. A comparison table, examples, and when to use each.
