Quick start
- Choose Encode for readable component text or Decode for text that already contains percent codes.
- Paste the exact component value. For example, use price=10&tax=2 when you want that whole value protected inside a query parameter.
- Turn on plus-spaces only for form-style query values where spaces should become + instead of %20.
Best uses
Start here if one of these sounds like your job. The examples below show which inputs matter most.
- Encode a query value that contains &, =, spaces, or punctuation.
- Decode percent-encoded text back into readable text.
- Handle plus signs as spaces for form-style values.
- Check developer examples locally in the browser.
What this tool helps with
The URL Encode / Decode tool is made for URL components, especially query values, path pieces, and small snippets that need to travel safely inside a URL. It turns reserved characters into percent-encoded text and decodes them back.
Match each input label on the tool to the mode, the exact text to encode or decode, and whether spaces should use %20 or plus signs.
The logic in plain language
In plain language: The tool uses percent-encoding for URL components. Unsafe or reserved characters are converted to UTF-8 bytes, then each byte is written as a percent sign followed by two hexadecimal digits. Spaces can stay as %20 or become + when form-style plus-spaces mode is selected. The examples on the page are there so you can compare your inputs with a filled-out example before copying the answer.
The tool treats the input as a URL component. In encode mode, reserved or unsafe characters are converted to UTF-8 bytes and written as % plus two hexadecimal digits. In decode mode, valid percent triplets are changed back into readable text. Plus-space mode uses + for spaces when you are working with form-style query values.
How to read the answer
Read the output as the value you would paste into a query parameter, path piece, form body, or test request. Compare the input length and output length when the result looks surprising; extra spaces, copied punctuation, or an already-encoded percent sign can change the answer.
- For price=10&tax=2, encode mode returns price%3D10%26tax%3D2 so the equals sign and ampersand stay part of the value instead of acting like URL separators.
- For price%3D10%26tax%3D2, decode mode returns price=10&tax=2 so you can read the original value again.
- For hello tools, normal URL-component encoding returns hello%20tools; plus-space mode can return hello+tools when the receiving system expects form-style spaces.
Common mistakes to avoid
The common mistakes are encoding an entire URL when only one value should be encoded, decoding the same value over and over, using plus mode where + should stay a literal plus sign, or pasting private tokens into a convenience tool.
- Do not encode a full URL the same way as one query value. Encoding ://, ?, &, and = can stop the URL from working.
- Do not decode the same value repeatedly unless you know it was double-encoded. For example, %2520 may become %20 after one decode, then a space after a second decode.
- Do not paste real signed links, access tokens, passwords, session URLs, or private query strings unless you fully understand the risk. URL encoding is formatting, not secrecy.
Quick example
Say you need to place price=10&tax=2 inside one query value. If you leave it alone, the ampersand can be read as a separator between two parameters. Encode mode returns price%3D10%26tax%3D2, which keeps the equals sign and ampersand inside the value you are sending.
Whole URL versus one component
A complete URL such as https://example.com/?q=test already uses ://, ?, =, and & as structure. A component value such as price=10&tax=2 is different because those same characters are data. Encode the part you are inserting, not the whole address, unless your app specifically asks for an encoded full URL.
When a tool, API, or form mentions URLSearchParams, query string values, or application/x-www-form-urlencoded data, plus-space handling may matter. If it simply asks for a URI component, %20 is usually the clearer space marker.
Research and references
These references help check the tool logic, format choices, platform limits, or safety notes.
Worked examples for URL Encode / Decode
price%3D10%26tax%3D2
price=10&tax=2
hello%20tools or hello+tools in plus mode
FAQ in plain language
When should I use the URL Encode / Decode?
Use it when your task matches one of these common needs: Encode a query value that contains &, =, spaces, or punctuation. Decode percent-encoded text back into readable text. It works best when you already know the text, code, URL, mode, format, or technical setting the page asks for.
What is the URL Encode / Decode doing with my inputs?
In plain language: The tool uses percent-encoding for URL components. Unsafe or reserved characters are converted to UTF-8 bytes, then each byte is written as a percent sign followed by two hexadecimal digits. Spaces can stay as %20 or become + when form-style plus-spaces mode is selected. The examples on the page are there so you can compare your inputs with a filled-out example before copying the answer.
What do the main URL Encode / Decode inputs mean?
Mode: Choose Encode when you have readable text and want percent-encoded output. Choose Decode when you already have percent-encoded text. Input text: Paste the exact value you want to convert. Ampersands, equals signs, spaces, slashes, and punctuation can change how a URL is read. Plus-spaces: Turn this on for form-style query values where spaces are represented as + instead of %20. Component value: A query value like price=10&tax=2 should be encoded differently from a complete URL such as https://example.com/?q=test.
How should I read the URL Encode / Decode answer?
Read the output next to your original input. If the tool changes format, units, encoding, spacing, or capitalization, compare a small sample before copying the whole result into another app.
What should I double-check before trusting the answer?
Encode complete URLs and individual URL components differently. This tool is best for component values such as query parameters, path pieces, and small text snippets, not for blindly encoding an entire URL, secret token, or already-encoded string. Also check the selected mode, input format, encoding, and whether the text includes private keys, passwords, or sensitive data.
Should I encode a whole URL or just one part?
Usually encode only the part you are inserting, such as a query value or path segment. Encoding a whole URL can turn ://, ?, &, and = into text, which may stop the URL from working.
Why do spaces sometimes become %20 and sometimes +?
%20 is normal percent-encoding for a space. A plus sign is common in form-style query strings. Use plus-spaces only when the target system expects form-style values.
Related tools
- UTM Builder Build campaign URLs with source, medium, campaign, content, and term parameters.
- Subnet Calculator Calculate IPv4 CIDR network, broadcast, mask, wildcard, and usable host range.
- Hex Calculator Add, subtract, multiply, divide, and convert hexadecimal numbers.
Keep exploring
If this guide is close but not exact, these links keep you near the same kind of problem.
- Developer Tools Browse the full category for related tools that help with the same job.
- All free tools Search the complete Access Free Tools library by task, category, or tool name.
- All tool and utility guides Find more plain-language examples, logic notes, mistakes, and result explanations.
- Free tool resources Start here when you are not sure which tool page fits.
Privacy and copying results
Recent answers stay visible only while you work in the current browser tab. They are not sent to a server.
Use Copy answer when you want to save the inputs and result in notes, homework, a message, or a project list. Check the units, labels, and limits before copying.