URL Decode / Query Parser

Decode URL-encoded text and expand query parameters into a readable table.

Encoded URL Input
Decoded Output
# Parameter Value
No query parameters parsed yet.
0 characters 0 lines

What does URL Decode / Query Parser do?

URL Decode reverses percent-encoded text and parses query-string parameters into readable key/value pairs.

  • Primary use: URL Decode reverses percent-encoded text and parses query-string parameters into readable key/value pairs.
  • Key technical fact: Query strings commonly use & between parameters and = between a parameter name and value.
  • Practical check: Validate the result before using it in authentication, signing, checksum, or transport code.
Topic Direct answer Source
Direct answer URL Decode reverses percent-encoded text and parses query-string parameters into readable key/value pairs. WHATWG URL Standard
Key fact Query strings commonly use & between parameters and = between a parameter name and value. WHATWG URL Standard
Processing model Runs locally in the browser; no production Node server receives the input. Browser JavaScript

Decode URLs and inspect query parameters

This URL decoder reverses percent-encoding and can split query strings into parameter names and values. Use it to inspect callback URLs, tracking links, signed URLs, OAuth redirects, analytics parameters, or API requests copied from logs.

Query strings commonly use & between parameters and = between a name and value. Form-style queries often use + for spaces, so the plus-as-space option helps decode values the way many web frameworks receive them.

How to use

  1. Paste a full URL, encoded path, or raw query string.
  2. Keep Treat + as space enabled for form-style query strings.
  3. Keep Parse query parameters enabled to extract key-value pairs.
  4. Click Decode URL, then review the decoded text and parameter table.

What is URL decoding?

URL decoding converts percent-encoded sequences such as %20, %2F, and UTF-8 byte sequences back into readable characters. It makes encoded paths and query values easier to audit.

A query parser reads the part after ? and separates parameters into rows. Repeated names, empty values, encoded nested URLs, and malformed escapes are common edge cases worth checking before reusing a decoded link.

Input notes

Malformed percent escapes should be treated as input errors, not silently trusted. Decoding can reveal hidden redirects, scripts, tokens, or personally identifiable values, so review the result before sharing it.

Example

A callback URL can be decoded and expanded into readable parameters:

Input
https://example.com/search?q=hello+world&redirect=https%3A%2F%2Fcoding.tools%2F

Decoded
https://example.com/search?q=hello world&redirect=https://coding.tools/

Parameters
q = hello world
redirect = https://coding.tools/

MCP integration

MCP (Model Context Protocol) lets AI agents and apps discover and run Coding.Tools utilities for repeatable conversions, formatting, hashing, and generation workflows.

MCP tool name: url-decode

MCP endpoint: https://coding.tools/mcp

Call tools/list first. Each tool entry includes inputSchema, outputSchema, and examples so an AI agent or client can build valid arguments without guessing.

For tools/call, read result.content[0].text for the display value and result.structuredContent for machine parsing. Tool-level failures return isError: true; protocol failures return a JSON-RPC error.

Example tools/call request:

curl -s https://coding.tools/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"url-decode","arguments":{"input":"https://example.com/search?q=hello+world&redirect=https%3A%2F%2Fcoding.tools%2F","options":{"parseQuery":true}}}}'

Most text and data tools accept an input string plus optional options. Browser-only image tools are listed for discovery and return a web UI link when they need browser image APIs.