URL & Link Tools
100% Client-Side 100% private in-browser decoding. Zero tracking or server logs.

URL Decoder (Percent-Decoding)

Decode percent-encoded URLs, hex sequences, and plus signs into readable text

RFC 3986 URL Percent-Encoding & Decoding Studio

100% Client-side. Safe encoding of reserved delimiters, UTF-8 unicode octets, and query parameters.

Client-Side RAMRFC 3986 / WHATWG

Fine-tune decoding passes and space transformations

Presets:
119 encoded characters
91 characters Valid UTF-8 Stream
Engine execution completed in 1 pass.
Encoding: UTF-8Spec: RFC 3986

About URL Decoder (Percent-Decoding)

Fast, private in-browser RFC 3986 URL decoder. Converts percent-encoded escape sequences (%20, %2F, %3F, %26, %3D) and plus-encoded spaces (+) back into readable plain text and UTF-8 characters. Includes deep recursive multi-pass unrolling for double-encoded URLs.

Key Capabilities & Features

  • Recursive multi-pass decoding to resolve double or triple percent-encoded links
  • Form-urlencoded plus sign (+) to space conversion switch
  • Resilient UTF-8 error recovery for malformed byte streams
  • Batch decoding with character counter

How to Use URL Decoder (Percent-Decoding)

1

Paste Encoded String

Enter percent-encoded URL or query text.

2

Enable Recursive Mode (Optional)

Turn on multi-pass decoding if links contain nested %25 sequences.

3

Copy Decoded Text

Grab the clean readable text with one click.

Privacy & In-Browser Execution Guarantee

100% private in-browser decoding. Zero tracking or server logs.

Frequently Asked Questions

What is a double-encoded URL?

A double-encoded URL occurs when an already percent-encoded string is encoded a second time, turning %20 into %2520 (since % is encoded as %25). Recursive decoding resolves these back to original spaces.

Why are spaces sometimes decoded from plus signs (+)?

Under the application/x-www-form-urlencoded specification historically used in HTML forms, spaces are represented as plus signs rather than %20.