Yoryantra
Home/Tools
← Back to Tools

Percent Encoding Analyzer

Analyze percent-encoded URL text. Inspect %XX escapes, decode UTF-8 bytes, find malformed percent encoding, compare raw and decoded values, and debug URLs directly in your browser.

Paste a URL, query string, redirect target, API parameter, or any text containing percent escapes like %20, %2F, or %E2%82%B9.

Options

This analyzer explains percent escapes instead of only decoding them, which helps when debugging broken redirects, query strings, and copied URLs.

Output

Percent encoding analysis output will appear here.
Percent encoding analysis happens directly in your browser. Your URL or text is not uploaded to a server.

Inspecting Percent-Encoding in URLs and Query Strings

Percent encoding is used in URLs to represent characters that cannot safely appear as plain text. A space may become %20, a slash may become %2F, and UTF-8 characters can appear as multiple percent escapes.

This Percent Encoding Analyzer goes beyond a normal URL decoder. It shows each percent escape, checks whether it is valid, highlights reserved characters, detects malformed sequences, and compares the raw value with the decoded output.

Using the Percent Encoding Analyzer

  1. Paste a full URL, query string, redirect URL, or encoded text.
  2. Choose safe, component-style, or URI-style decoding.
  3. Turn plus-to-space handling on for form-style query values if needed.
  4. Review valid and invalid percent escapes in the table.
  5. Copy the decoded output, report, JSON, or escape table.

Common Percent Encoding Analyzer Use Cases

  • Debugging broken URLs with malformed percent escapes.
  • Checking encoded redirect parameters inside query strings.
  • Understanding why %2F, %3A, or %26 changes URL behavior.
  • Inspecting UTF-8 characters encoded as multiple %XX bytes.
  • Comparing plus signs and spaces in form/query decoding.
  • Reviewing copied URLs from browsers, logs, APIs, and analytics tools.

Example Percent Escapes

%20  -> space
%2F  -> /
%3A  -> :
%C3%A9 -> é

Plus Signs Are Not Always Spaces

In application/x-www-form-urlencoded query values, a plus sign is often treated as a space. In a normal URL path, however, plus is just a plus character. This is why the tool lets you choose whether plus signs should be decoded as spaces.

When debugging API requests or redirect URLs, this difference can matter. A value copied from a form body may need different decoding than a raw URL path.

Frequently Asked Questions

What is percent encoding?

Percent encoding represents characters in URLs using a percent sign followed by two hexadecimal digits, such as %20 for a space.

What is a malformed percent escape?

It is a percent sign that is not followed by two valid hexadecimal digits, such as %G1 or a trailing % at the end of a string.

Is %2F the same as a slash?

It decodes to a slash, but whether it behaves like a path slash depends on where and when decoding happens.

Should plus signs become spaces?

Only in some form/query decoding contexts. A plus sign in a URL path is normally a literal plus sign.

Is anything uploaded when I analyze a URL?

No. Analysis happens directly in your browser.