Codificar text for safe use inside a URL query string
Turn arbitrary texto (con spaces, ampersands, Unicode, equals signs) en un valor ese puede ser placed directly después ?key= en un URL sin 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 Codificador de URL →
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
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 Analizador de URL →
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.
Preguntas frecuentes
- 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.