Tool workspace
URL Encoder / Decoder
Input
Encode or decode text, URL components, and form values with this free online URL Encoder / Decoder. You can also parse query parameters, edit parameter values, and build an updated URL. Convert text as you type or manually, then copy or download the result.
Input
Output
Loading tool
Developer Tools
URL Encoder / Decoder
Encode or decode text, URL components, and form values with this free online URL Encoder / Decoder. You can also parse query parameters, edit parameter values, and build an updated URL. Convert text as you type or manually, then copy or download the result.
Quick guide
How to use
Enter your text or URL: Type or paste the value into the input field, or upload a supported text file.
Choose the operation: Select encode or decode.
Select the encoding type: Choose URL component, full URL, or form value, depending on your data.
Convert: Enable automatic conversion as you type or select the Convert button.
Review the output: Check the converted text and the input and output character counts.
Copy or download: Copy the result or download it as a file.
If the input contains an invalid percent-encoded sequence, the decoder displays an error rather than silently treating the data as valid.
Details
About this tool
Encode or decode text, URL components, and form values with this free online URL Encoder / Decoder. You can also parse query parameters, edit parameter values, and build an updated URL. Convert text as you type or manually, then copy or download the result.
What Is URL Encoding?
URL encoding, also called percent encoding, represents certain characters using a percent sign (%) followed by two hexadecimal digits.
URLs can contain characters that have special meanings or are not safe to use directly in every part of a URL. Spaces, ampersands, and non-ASCII characters are common examples.
For example:
A space can become %20.
An ampersand (&) can become %26 when it is part of a value.
A character outside the basic ASCII character set is represented using its UTF-8 bytes, each percent-encoded as needed.
Encoding helps data travel correctly in URLs, query strings, and web requests. It is especially important when a value contains characters that could otherwise be interpreted as URL syntax.
URL Component, Full URL, and Form Encoding
The correct encoding method depends on what you are encoding.
URL component encoding
Use component encoding for an individual value or part of a URL, such as a search term, username, or query parameter value. It encodes reserved characters that could otherwise change the structure of the URL.
Example:
Original: hello world
Encoded: hello%20world
Full URL encoding
Full URL encoding is intended for a complete URL. It preserves URL structure characters such as :, /, ?, and &, while encoding characters that need escaping.
For example, a URL such as https://example.com/search?q=hello world can be encoded without treating its structural separators as ordinary text.
Do not use component encoding on an entire URL if you need to preserve its structure. Component encoding would also encode separators such as / and ?.
Form-style encoding
HTML form submissions commonly use the application/x-www-form-urlencoded format. In this format, spaces are represented by + rather than %20.
Example:
Original: hello world
Form-encoded: hello+world
A literal plus sign is encoded as %2B, so it is not confused with a space.
Parse and Edit URL Query Parameters
A query string is the part of a URL that follows the question mark (?). It contains parameters, usually written as key-value pairs separated by ampersands (&).
For example:
https://example.com/search?q=coffee&category=books
This URL contains two parameters:
You can use the query parameter tools to:
Parse parameters from a URL.
View parameter names and values.
Add a new parameter.
Remove an existing parameter.
Build an updated URL with your changes.
A parameter can appear more than once. For example:
https://example.com/search?tag=design&tag=development
This URL contains two tag values. Repeated parameters can be meaningful, so they should not automatically be treated as duplicates or discarded.
Common Uses of URL Encoding
URL encoding is used in many parts of web development and everyday browsing:
Query strings: Safely include search terms, filters, and other values in a URL.
Web forms: Encode submitted form values, including spaces and special characters.
APIs: Send data in URL paths and query parameters.
Links: Create links that contain special characters or non-English text.
Debugging: Inspect encoded values and understand how a URL's parameters are structured.
URL Encoding Examples
The examples show how the same text can be represented differently depending on the encoding context.
Is URL Encoding the Same as Encryption?
No. URL encoding is not encryption and does not protect private information. It changes how text is represented so that it can be used safely in a URL or form submission.
Encoded text can be decoded by anyone. Do not use URL encoding to hide passwords, API keys, or other sensitive information.
Practical inputs
Examples JSON
URL Encoding Examples
The examples show how the same text can be represented differently depending on the encoding context.
Help
Frequently asked questions
What is percent encoding?
Percent encoding represents certain characters using % followed by two hexadecimal digits. It allows characters to be represented in a URL-compatible form.
What is the difference between %20 and +?
Both can represent a space in certain contexts. %20 is the percent-encoded representation of a space. In form-style encoding, a space is represented by +. A plus sign in a value is encoded as %2B.
When should I use URL component encoding?
Use it when encoding an individual value, such as a search term or query parameter value. It encodes characters that could otherwise be interpreted as part of the URL structure.
Should I encode an entire URL as a component?
Usually not. Component encoding also encodes structural characters such as /, ?, and &. Use full URL encoding when you need to preserve the structure of a complete URL.
Can I decode a URL that contains non-English characters?
Yes. Percent-encoded non-ASCII text is commonly represented using UTF-8 bytes. The decoder can turn valid encoded sequences back into readable text.
Can I edit query parameters with this tool?
Yes. You can parse query parameters from a URL, add or remove parameters, and build an updated URL.
Does the tool support repeated query parameters?
Yes. A URL can contain the same parameter name more than once, such as tag=design&tag=development. Repeated values should be preserved when they are meaningful.
Is URL encoding secure?
No. URL encoding is a text representation method, not a security or encryption method. Anyone can decode an encoded value.