Reading percent - encoded values from logs
Debug logs often show parameters like `%EA%...`. Decoding reveals the real keyword or parameter so you can reproduce the request accurately.
URL Encode/Decode
Encode or decode URLs and query strings instantly. Handle special characters safely in URLs.
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.
How to use
Paste a full URL or a parameter value, then encode or decode to confirm what is actually being sent.
- 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.
Why this tool is useful
URLs and query strings must safely represent characters that are not allowed in plain form, such as spaces, non - ASCII letters, and reserved symbols. When you inspect logs or debugging screens, you may see percent - encoded values that are hard to read. When you build links, leaving characters unencoded can lead to broken requests or unexpected parsing.
Encoding and decoding helps you move between “human - readable” values and “URL - safe” values with fewer errors.
What this tool helps with
You can validate link parameters and reproduce issues more reliably by working with the exact encoded value. This is useful for redirects, UTM parameters, and search queries.
It also reduces the risk of double - encoding or partial encoding, which often causes bugs where parameters look correct but decode incorrectly on the server side.
Examples
Building redirect or tracking URLs safely
When a parameter itself contains a URL or special characters, encoding is required. Encoding the inner value helps prevent truncation and parsing errors in different environments.
Recommended for
Recommended if you: - debug query strings and redirects - handle non - ASCII characters or reserved symbols in URLs - build tracking links and need stable parameters - investigate “works in one place, breaks in another” link issues
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.
Related Tools
Decode JWT header and payload instantly. No verification, no server upload. Works in your browser.
Convert JSON to YAML or YAML to JSON instantly. Runs in your browser with no upload.
Generate random UUIDs (v4) and GUIDs instantly. Create unique identifiers for databases, APIs, and applications.