From URL-encoded to text

Reverse percent-encoding to recover the original Unicode text from URL-safe strings.

Decoding rules

Sequences matching %[0-9A-Fa-f]{2} are converted to the corresponding byte; consecutive bytes decode as UTF-8 into characters. Invalid percent triplets or malformed UTF-8 may produce replacement characters or errors depending on input.

+ is not automatically converted to space — that behavior belongs to HTML form decoding, not generic URI decoding.

When to use it

Read tracking parameters in marketing links, inspect redirect_uri payloads, recover non-ASCII slugs from copied browser addresses, or verify round-trips with the encode tool.

Limitations

Double-encoded strings decode only one layer per pass. Plus-as-space legacy data must be normalized manually before decoding. Very long encoded strings are limited by browser textarea capacity.

Example

a%20b decodes to a b.

This skill is available over A2A JSON-RPC and REST. When you already know the skill id and export, call execute directly—no discovery step required.

REST example

curl -sS -X POST https://toolplaza.app/api/helpers/execute \
  -H 'Content-Type: application/json' \
  -d '{"skillId":"url-codec__from-url-encoded-to-text","export":"decodeUrlComponent","args":["Hello%20World"]}'

A2A JSON-RPC example

Send POST https://toolplaza.app/api/a2a with:

{
  "jsonrpc": "2.0",
  "id": "1",
  "method": "message/send",
  "params": {
    "message": {
      "messageId": "uuid",
      "role": "user",
      "parts": [
        {
          "kind": "text",
          "text": "ignored"
        }
      ]
    },
    "metadata": {
      "toolplaza": {
        "skillId": "url-codec__from-url-encoded-to-text",
        "export": "decodeUrlComponent",
        "args": [
          "Hello%20World"
        ]
      }
    }
  }
}

Full Agent API guide · Skill schema