TASK

Encode text for safe use inside a URL query string

Turn arbitrary text (with spaces, ampersands, Unicode, equals signs) into a value that can be placed directly after ?key= in a URL without breaking parsing.

1

When you paste raw text into a query string, characters like spaces, &, =, and non-ASCII letters break URL parsing. Percent-encoding converts each unsafe byte to %XX so the value survives transport intact.
2

URL Encoder →
Paste the raw text (e.g. 'hello world & co=2'). The tool outputs the percent-encoded form ready to drop after ?q=.
3

url-encode → hex-encode
View recipe Open in Toolchain

Use the chain when the value is itself JSON or Base64 — it encodes the payload and then percent-encodes the result in one pass.
4

URL Parser →
Sanity check: paste the full URL ?q=<encoded> and confirm the parser reads the parameter back as your original text.
5

If you only need to encode a fragment (not a full component), prefer encodeURIComponent semantics — the tool already handles reserved characters correctly for query values.

Frequently asked questions

Why does a space become %20 and not +?: %20 is the percent-encoded form of a space byte. The + form is specific to application/x-www-form-urlencoded body encoding; for query strings in URLs, %20 is universally safe.
Should I encode the whole URL or just the value?: Only the value. Encoding the entire URL would percent-encode the ?, =, and & that structure the URL, breaking it. Encode each parameter value individually.

Workflows that solve this

Convert Base32 to Hex

Decode Base32 and re-encode as hex for debugging.

Convert Base64 to Hex

Decode a Base64 string into raw bytes and re-encode it as hexadecimal for inspection or interop.

Convert Binary to Hex

Decode a binary (base-2) string into its byte value and re-encode as hexadecimal.

ChaCha20 Encrypt then Hex

ChaCha20 encrypt then hex-encode the ciphertext.

Encode a JSON payload for URL transport

Prepare a JSON document for a URL parameter: pretty-print, Base64-encode, then percent-encode — the exact inverse of the nested-parameter decode chain.

Hex encode then decode round-trip

Encode text to hexadecimal and decode it back to verify the round-trip preserves the original data.

Hex-encode text and analyze

Convert text to its hexadecimal representation then compute character statistics on the hex output.

Convert Multibase to Hex

Decode multibase and re-encode as plain hex.

Convert Octal to Hex

Decode octal and re-encode as hex for compact representation.

Punycode Decode and URL Parse

Decode Punycode domain then parse the full URL.

Reverse text and show hex encoding

Reverse a string then inspect its hexadecimal representation — useful for debugging byte-order issues and encoding puzzles.

SHA-512 Hash then Hex Encode

Compute SHA-512 hash then encode as hex for readability.

Kebab Case and URL Encode

Convert to kebab-case then URL-encode for safe URL slugs.

Decode URL and show hex bytes

Percent-decode a URL-encoded string then view its hexadecimal byte representation for low-level analysis.

URL Decode and Parse

URL-decode then parse the URL into components.

URL Encode then Base64 Double Encode

URL-encode then Base64-encode for double encoding in API payloads.

Encode a text payload for URL transport

Percent-encode text then show its hex representation for safe URL parameter transport.

XXencode then Hex

XXencode text then hex-encode the result.

Learn more

Want to understand why?

How to Build Query Strings

A beginner-level guide covering query-string, url, building. Includes step-by-step instructions, common errors, troubleshooting tips, and security considerations for query-string.

How to Encode URLs in Go

A beginner-level guide covering url, encoding, go. Includes step-by-step instructions, common errors, troubleshooting tips, and security considerations for url.

Form encoding (application/x-www-form-urlencoded) is how HTML forms encode key-value pairs on submission, encoding spaces as + instead of %20.

Percent-Encoding

Percent-encoding is the mechanism that converts unsafe characters in URLs into %HH form, defined by RFC 3986.

Related tools

Percent-encode text for safe use in URLs. Free, private, and 100% client-side.

Parse a URL into its components: protocol, host, path, query, hash, port, username, and password. Free, private, and 100% client-side.

Decode percent-encoded URL text back to readable characters. Free, private, and 100% client-side.