URL Decode / Query Parser

Decode URL-encoded text, inspect full URLs, and expand query parameters into a readable table.

Encoded URL Input

Treat + as space Parse query parameters

Decoded Output

#	Parameter	Value
No query parameters parsed yet.

0 characters 0 lines

URL Decode / Query Parser

URL Decode converts percent-encoded sequences back into readable text and can break a query string into individual parameter names and values.

Everything runs locally in your browser, which is useful when inspecting callback URLs, analytics links, signed URLs, or API request parameters.

How to use

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

What is this tool?

URL decoding reverses percent encoding by converting sequences such as %20 and %E2%9C%93 into their original characters.

The query parser splits the part after ? into key-value pairs and preserves repeated parameters as separate rows.

Input notes

Malformed percent escapes will be reported instead of silently changing the input. For full URLs, structural separators are preserved while encoded characters are decoded.

Example

A callback URL can be decoded and parsed:

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.