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.

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.

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.

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.

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.

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.

%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.

Double-encoding changes percent signs too. For example, %20 can become %2520. Decode once and inspect the result before encoding again.

Common causes include a broken percent triplet, copied whitespace, text that was not URL-encoded, or a plus sign that should stay as + instead of becoming a space.

Do not paste real secrets, access tokens, signed URLs, private query strings, or session links into any tool unless you fully understand the risk. Encoding does not make them safe.

No. URL encoding protects characters so they can travel inside URLs. Base64 changes bytes into printable text for a different set of use cases.

No. The tool runs in your browser tab. Your recent answers stay only on the page while you use it, and they are not sent to a server.