What does a URL Decoder do?

It converts percent-encoded text back into readable characters.

%20 is the percent-encoded form of a space character.

What is the difference between %20 and +?

%20 is standard percent encoding for a space. + is often used for spaces in form-encoded query strings.

Should I use encodeURI or encodeURIComponent?

Use encodeURIComponent for query parameter values. Use encodeURI when preserving a full URL structure.

Why is my URL double-encoded?

Double encoding happens when already encoded text is encoded again, such as %20 becoming %2520.

Does URL encoding make a link safe?

No. URL encoding only changes text representation. It does not verify whether a link is safe or trustworthy.

Can I decode malformed URLs?

The tool handles malformed percent encoding gracefully and shows a helpful warning.

Is my input uploaded to a server?

This browser-based BlinkCalc tool is designed to convert input locally and should not store user input.

When should I encode a redirect URL?

Encode redirect URLs when placing them inside another URL’s query parameter to avoid breaking the outer URL.

URL Encoder / Decoder - Encode and Decode URLs Online

URL conversion tool

Encode or decode URL text

Choose a mode, paste text or a URL, review the converted output, then copy the result.

Text or URL to encode

Example: https://example.com/search?q=hello world&category=tools

Encoded output is ready to copy. URI component encoding is best for query parameter values.

URL-encoded output

Output is displayed safely as text and is not opened or fetched.

https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dhello%20world%26category%3Dtools

Conversion status

Encoded

Use URI component encoding for query parameter values.

Status

Encoded

Encoded output is ready to copy. URI component encoding is best for query parameter values.

Mode

Encode

Current conversion direction.

Input length

55

Characters in the input.

Output length

73

Characters in the output.

Characters converted

67

Approximate changed characters.

Spaces handling

%20

Current space conversion behaviour.

Copy output

Copy the encoded or decoded result for APIs, query strings, redirects, webhooks, or documentation.

Swap output into input

Move the current output back into the input box and switch modes.

Copy input

Copy the original input before conversion for comparison or debugging.

Privacy note

Conversion is designed to happen locally in your browser without external APIs.

Accuracy note

Full URLs and URL components should be encoded differently depending on where they are used.

Debugging note

Useful for APIs, query strings, redirect URLs, callback URLs, and webhook payloads.

Encoding options

Choose the right conversion behaviour for full URLs, URL components, and form-style query strings.

Encode mode

encodeURIComponent is best for query parameter values.

Space handling

+ is common in form-encoded query strings.

Decode + as spacesAuto-convert

Practical guidance

Use encodeURIComponent for query values such as redirect URLs. Use encodeURI when you want to preserve separators like ://, /, ?, and & in a full URL.

Practical URL encoding examples

Click an example to load it into the tool.

URL encoding quick reference

Space

%20

Ampersand

%26

Equals

%3D

Question mark

%3F

Slash

%2F

Colon

%3A

Hash

%23

Plus

%2B

Percent

%25

encodeURI

Preserves full URL structure.

encodeURIComponent

Best for query parameter values.

Developer guide

Understand URL encoding and decoding

URL encoding converts unsafe or reserved characters into percent-encoded sequences so text can safely appear inside URLs.

What is URL encoding?

URL encoding converts reserved or unsafe characters into percent-encoded sequences such as %20 for spaces, %26 for ampersands, and %3D for equals signs.

When should developers use URL encoding?

Use it for query parameters, API requests, redirect URLs, webhook URLs, search URLs, form submissions, callback URLs, and links with special characters.

URL encoding vs URL decoding

Encoding converts readable text into URL-safe text. Decoding converts percent-encoded text back into readable text and should handle malformed input safely.

encodeURI vs encodeURIComponent

encodeURI preserves full URL structure. encodeURIComponent encodes reserved characters for URL components and is usually best for parameter values.

Privacy and security

BlinkCalc is designed to convert locally in the browser. URL encoding does not verify whether a link is safe, malicious, or trustworthy.

Common URL encoding mistakes

Encoding an entire URL when only a query value should be encoded.

Double-encoding values such as %20 into %2520.

Forgetting to encode redirect URLs inside parameters.

Confusing + with %20.

Not encoding & inside query values.

Decoding malformed percent sequences.

Assuming URL encoding makes unsafe links safe.

How to use this URL Encoder / Decoder

1Choose Encode or Decode.
2Paste text, a URL, or a query string into the input box.
3Choose full-string or URI-component handling if needed.
4Review the converted output.
5Copy the result or swap it back into the input.

Why developers use a URL Encoder / Decoder

Prepare query parameters safely.

Debug API requests.

Decode webhook and redirect URLs.

Inspect encoded tracking links.

Avoid malformed URLs.

Encode callback URLs.

Compare readable and encoded values.

Reduce manual escaping mistakes.

URL Encoder / Decoder FAQs

It converts reserved or unsafe characters into percent-encoded sequences that can safely appear in URLs.

Related tools

More tools to try

URL Cleaner

HTML Encoder / Decoder

Base64 Encoder and Decoder

JWT Decoder

URL Encoder / Decoder