MySafeInfo. Data Pass

URL encode / decode

Encode a value, decode URL text, or inspect query parameters.

FreeNo pass requiredNo ads

Your text and files stay in your browser.

Drop a file here, or use Open file. Ctrl+Enter / Command+Enter runs the tool.

Ready for your input
Processed on your device

Paste text or try an example to begin.

No uploads. No ads. No Data Pass required. Buy me a coffee

Encode URL values and read query parameters

Prepare a value for a query string, decode percent-encoded text, or inspect the parameters in an existing URL. Separate modes make the distinction between a single value and complete URI text explicit. A value containing an ampersand needs that character encoded so it does not become a new parameter. A complete URI usually needs its structural separators preserved. The tool only transforms text; it never opens, requests, or follows the supplied address.

URL encoding examples

Encode a search value

Input

Hello & goodbye

Result

Hello%20%26%20goodbye

Choose A query value and Encode. The space and ampersand become percent escapes, so the entire result can be used as one parameter value rather than being split into multiple parameters.

Decode a form-style value

Input

coffee+%26+tea

Result

coffee & tea

Choose A query value, Decode, and Decode + as a space. The plus convention is used by form-style query strings; leave that setting off when a literal plus sign should remain a plus.

How to work with encoded URLs

  1. Paste text into Input, or open a UTF-8 file. Choose A query value when encoding one value that will be placed after an equals sign.
  2. Use Complete URI text to preserve structural separators. Reserved percent escapes stay escaped when decoding in this mode, preventing accidental changes to URL structure.
  3. Choose Inspect query parameters for a complete HTTP or HTTPS URL or a query string. Read the name and value columns; repeated parameter names remain separate rows.
  4. Copy or download the result. Query inspection produces CSV that can be sent directly to CSV to JSON or CSV to XML without uploading the original address.

URL encoding questions

Will the tool visit the address I paste?

No. URLs are treated as text and are never fetched. Query inspection reads the query portion locally. Tokens or other confidential parameter values are not written to navigation history, browser storage, or server requests by this tool.

Why are there value and URI modes?

They preserve different characters. Value encoding escapes separators such as ampersands, equals signs, and slashes. URI encoding leaves reserved separators intact. Use value mode for individual parameters; do not encode a whole URL as a value unless another application specifically expects that.

What happens to repeated query parameters?

Inspection keeps each occurrence in its original order, including empty values. A URL with two tag parameters produces two rows. The table previews the first 200 parameters; the CSV output and download include all parsed parameters within the size limits.

Can the tool repair invalid percent escapes?

It reports malformed escapes or invalid UTF-8 instead of guessing. Each percent sign in encoded input needs two hexadecimal digits. Encoding an already encoded value escapes its percent signs again, so avoid applying Encode repeatedly unless double encoding is intentional.

Encoding is not validation or encryption

Encoding does not make a URL trustworthy, encrypt a secret, or verify that a destination exists. Inspect query parameters supports HTTP and HTTPS addresses and raw query strings. Input is limited to 10 MiB with bounded output and processing time. When importing query CSV into a spreadsheet, import values as text so formula-like content remains literal.