What does percent-encoding look like and how is it decoded?

Percent-encoding replaces special characters with a percent sign followed by two hex digits representing the character's UTF-8 byte value. For example, a space becomes %20, and an ampersand becomes %26. Decoding reverses this substitution.

How do I see all query parameters from a URL at once?

Use the Query String to Object tool. Paste the full URL or just the query string portion, and it produces a JSON object where each key is a parameter name and each value is the decoded parameter value.

What if a query parameter value itself contains encoded characters?

The decoder handles multiple levels of encoding. If a value was double-encoded (encoded twice), you may need to run it through the decoder twice to fully restore the original string.

Decode URL Parameters Online

Percent-encoded URLs are intentionally designed to be machine-readable rather than human-readable. A URL like https://example.com/search?q=hello%20world&filter=date%3A2024 is technically correct but awkward to read and analyze. When debugging redirects, inspecting tracking links, or reverse-engineering third-party integrations, you need to decode all those %XX sequences back to readable characters, split the query string into named parameters, and understand what each value means. devtoolkit.sh's URL Decode tool reverses percent-encoding instantly. The Query String to Object converter parses the entire query string into a JSON object where each parameter name maps to its decoded value, making it easy to see all parameters at once. The URL Parser breaks a full URL into its components — scheme, host, path, query, and fragment — so you can inspect each part separately. Together, these tools handle everything from simple query strings to complex OAuth callback URLs with nested encoded values.

%URL DecodeHOT

Decode percent-encoded URL strings back to readable text.

?{}Query String to Object

Parse a URL query string into a JSON object.

/URL Parser

Break down a URL into its individual components using the browser URL API.

FAQ

What does percent-encoding look like and how is it decoded?: Percent-encoding replaces special characters with a percent sign followed by two hex digits representing the character's UTF-8 byte value. For example, a space becomes %20, and an ampersand becomes %26. Decoding reverses this substitution.
How do I see all query parameters from a URL at once?: Use the Query String to Object tool. Paste the full URL or just the query string portion, and it produces a JSON object where each key is a parameter name and each value is the decoded parameter value.
What if a query parameter value itself contains encoded characters?: The decoder handles multiple levels of encoding. If a value was double-encoded (encoded twice), you may need to run it through the decoder twice to fully restore the original string.