WebNift
Back to URL Decoder
Official Guide

URL Decoder Guide

Learn how to safely decode percent-encoded URLs, understand the difference between decodeURI and decodeURIComponent, and handle complex edge cases.

7 min read

WebNift Editorial Team

WebNift Editorial Team

Practical guides and resources for using WebNift's free online tools.

URL Decoder Guide

URL decoding (also known as percent-decoding) is the process of translating percent-encoded character sequences back into their original, readable text format.

WebNift’s URL Decoder is a free, local, client-side developer utility that instantly decodes URLs while strictly adhering to native JavaScript decoding standards.

What Is URL Decoding?

When data is sent over the internet within a URL, it must only contain safe ASCII characters. Any unsafe characters (such as spaces, emojis, or international text) are translated into a sequence of percent signs followed by hexadecimal digits (e.g., 

%20
for a space).

URL decoding reverses this process. It takes a percent-encoded string and translates it back into human-readable text.

How URL Encoding Works

URL encoding uses a percent sign (

%
) followed by a two-digit hexadecimal representation of a character's byte value.

For example, the ASCII value for a space is 

32
, which is 
20
in hexadecimal. Therefore, a space becomes 
%20
. Modern percent-encoding uses UTF-8, allowing multi-byte characters like emojis to be represented as longer percent sequences (e.g., 
%F0%9F%91%8B
).

How to Use the URL Decoder

Using the WebNift URL Decoder is straightforward:

  1. Paste your text: Enter the encoded URL or text into the input field.
  2. Select your mode: Choose whether you are decoding a URL component or a full URI.
  3. Run the tool: Click "Run Tool" to decode the text.
  4. Review: The decoded output will appear in the results panel.
  5. Copy: Use the Copy button to quickly save the result to your clipboard.

Because the tool operates entirely locally in your browser, your data is never sent to a server.

URL Component vs Full URI Decoding

The URL Decoder offers two distinct modes that map directly to native JavaScript functionality:

Decode URI Component

This mode uses 

decodeURIComponent()
. It decodes everything, including characters that have special structural meaning in a URL like 
?
, 
=
, 
&
, 
/
, and 
#
. This mode is ideal when you are decoding the value of a single query parameter.

Decode Full URI

This mode uses 

decodeURI()
. It is designed to decode a complete URL without destroying its structure. It will leave reserved structural characters encoded (so a 
%3F
remains 
%3F
, preserving the intended structure), while safely decoding spaces and text.

Understanding Percent-Encoding

Percent-encoding is the universal standard for uniform resource identifiers (URIs). It ensures that URLs can be safely transmitted across different network protocols without syntax errors or misinterpretation. The decoder expects standard, valid hexadecimal sequences.

%20
vs 
+

A very common source of confusion is the difference between 

%20
and 
+
.

The WebNift URL Decoder follows strict, native URI decoding behaviour:

  • %20
    becomes a literal space (
    ).
  • +
    remains a literal plus sign (
    +
    ).

While a plus sign (

+
) is sometimes interpreted as a space, this is only true within the context of 
application/x-www-form-urlencoded
query strings (like an HTML form submission). In standard URI decoding, a plus sign is simply a plus sign. Our tool does not automatically convert plus signs to spaces, ensuring your data is not inadvertently mutated.

Decoding 
%2B
and Other Encoded Characters

Because a literal plus sign is a reserved character in some contexts, it is often encoded as 

%2B
. When passed through the URL Decoder, 
%2B
safely decodes back into a literal 
+
.

Other common characters include:

  • %3A
    decodes to 
    :
  • %2F
    decodes to 
    /
  • %3F
    decodes to 
    ?
  • %3D
    decodes to 
    =

(Note: In Full URI mode, these specific characters will remain encoded to protect the URL's structure).

Unicode and International Characters

The URL Decoder natively supports UTF-8, making it fully compatible with international characters.

Percent-encoded sequences can represent complex, multi-byte characters. For example:

  • Caf%C3%A9
    seamlessly decodes to 
    Café
    .
  • %D9%85%D8%B1%D8%AD%D8%A8%D8%A7
    decodes to the Arabic 
    مرحبا
    .
  • %E4%BD%A0%E5%A5%BD
    decodes to the Chinese 
    你好
    .
  • %F0%9F%91%8B
    decodes to the waving hand emoji 
    👋
    .

What Is Double Encoding?

Sometimes, a URL is accidentally encoded more than once. When this happens, the percent signs themselves become encoded as 

%25
.

For example, a space (

%20
) encoded a second time becomes 
%2520
.

The WebNift URL Decoder performs a strict single-pass decode. Decoding 

%2520
will result in 
%20
. This is an intentional safety feature to prevent the tool from recursively destroying intentionally encoded data. If you have double-encoded text, simply run the decoded output through the tool a second time.

Why Some Encoded URLs Fail to Decode

If the URL Decoder throws an error, your input likely contains malformed percent sequences or invalid UTF-8 data.

For example, the string 

hello%
contains a percent sign that is not followed by valid hexadecimal digits. Native JavaScript decoding will throw a 
URIError
when it encounters malformed input. The tool surfaces this error explicitly rather than attempting to silently repair or guess your data, ensuring you are aware of the invalid input.

URL Decoding Examples

Here are some common scenarios and their expected outputs in Component mode:

  • Spaces: 
    hello%20world
    → 
    hello world
  • Encoded Plus: 
    price%2Btax
    → 
    price+tax
  • Literal Plus: 
    hello+world
    → 
    hello+world
  • Percent Sign: 
    100%25
    → 
    100%
  • Double Encoded: 
    hello%2520world
    → 
    hello%20world

Common URL Decoding Mistakes

  • Assuming 
    +
    means space:     In standard URI encoding, a plus sign is literal. Do not expect standard URI decoders to convert it to a space.
  • Decoding full URLs as components: Using Component mode on a full URL will decode the 
    ?
    and 
    &
    characters, breaking the URL structure. Always use Full URI mode for complete web addresses.
  • Ignoring errors: If the tool throws an error, the encoded string is broken. Do not assume the tool failed; inspect your input for incomplete 
    %
    sequences.

URL Decoder FAQ

What is URL decoding? URL decoding (percent-decoding) translates percent-encoded character sequences back into their original text form.

What does 

%20
mean in a URL? 
%20
is the standard percent-encoded representation of a space character.

Does 

+
mean a space in a URL? In standard URI encoding, a plus sign (
+
) is interpreted literally. It is only treated as a space in the context of 
application/x-www-form-urlencoded
form data.

What does 

%2B
decode to? The sequence 
%2B
decodes to a literal plus sign (
+
).

What is the difference between decodeURI() and decodeURIComponent()? 

decodeURI()
is for full URLs and leaves reserved characters (like 
?
, 
&
, and 
=
) encoded. 
decodeURIComponent()
decodes everything, making it suitable for specific query parameter values.

Can the URL Decoder handle Unicode characters? Yes. It accurately decodes valid UTF-8 percent sequences, supporting emojis, CJK characters, Arabic, and other international text.

Why won't my encoded URL decode? If decoding fails with an error, the input likely contains malformed percent sequences or invalid UTF-8 (for example, a lone 

%
sign without trailing hex codes).

Does this tool decode a value more than once? No. The tool performs a single decoding pass to ensure safety. If your input was double-encoded (e.g., 

%2520
), the result will be the single-encoded version (
%20
).

Is URL decoding the same as Base64 decoding? No. URL decoding reverses percent-encoding used for web addresses. Base64 is an entirely different binary-to-text encoding scheme.