URL Encoder & Decoder

Tool guide

What is URL Encoder & Decoder?

URL Encoder and Decoder separates component mode from full-URL mode. Component mode encodes separators such as slashes, question marks, and equals signs; full mode preserves URL structure while handling spaces and non-ASCII text. Malformed percent escapes and invalid UTF-8 are rejected explicitly. Common workflows include the following. Encode a query value or individual path segment. Inspect percent-encoded text found in logs. Preserve a full URL structure while encoding Chinese text or spaces. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.

When to use it

Encode a query value or individual path segment.
Inspect percent-encoded text found in logs.
Preserve a full URL structure while encoding Chinese text or spaces.

How to use it

Choose URL component or full URL mode.
Enter text to encode or percent-encoded text to decode.
Convert and copy the result.
Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.

Runnable examples

The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.

Example 1

https://jsonlane.com/en/tools/json/formatter/?source=featured tools&mode=strict#example

Example 2

filter=status:complete&keyword=JSON tools/bilingual&return=/en/category/json/

Input rules

Use component mode for query values and path segments.
Full mode does not verify whether a host or protocol is reachable.
Decoded input must contain valid percent escapes and UTF-8 bytes.
Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
Full URL mode preserves reserved separators and does not validate that the result is an absolute URL.

Output rules

Component mode encodes URI separator characters.
Full mode preserves /, ?, &, =, and other structural characters.
A plus sign remains a plus sign because form-encoding rules are not applied.
Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
+ remains + when decoding.

Limitations and cautions

Full URL mode preserves reserved separators and does not validate that the result is an absolute URL.
+ remains + when decoding.
Malformed percent sequences and invalid UTF-8 are rejected.

How your data is handled

Encoding and decoding use local URI and UTF-8 browser functions and never visit the supplied URL.

FAQ

Which mode should I use?

Use component mode for a query value, path segment, or key. Use full URL mode when separators must remain structural.

Does + decode to a space?

No. This tool follows URI percent-encoding; form-urlencoded plus-to-space behavior is not applied.

What happens to invalid UTF-8 escapes?

Malformed percent sequences or invalid UTF-8 are rejected with an error.

When should I use component or full-URL mode?

Use component mode for a query value or path segment; use full-URL mode when separators such as /, ?, and & must remain structural.

Why is a plus sign not decoded as a space?

That conversion belongs to form encoding. This page follows URI percent-encoding rules and does not make the implicit substitution.

Does the tool visit the URL I enter?

No. It transforms characters and percent sequences locally without making a network request or checking whether the address exists.