Encode the right part.
Convert a query value without leaving &, = or + as ambiguous separators. Choose an explicit encoding mode for your destination.
URL ENCODER, DECODER & QUERY STRING EDITOREvery character.
Every character.
In the right place.
Make encoded links readable, prepare a parameter value or edit a query one row at a time. Keep control of spaces, separators and repeated keys.
A CLEARER LOOK AT YOUR LINKS
Text ↔ URL encoding
Use component mode for one parameter value. URI syntax preserves separators; form mode treats + as a space when decoding. Conversion runs exactly once and does not trim text. Untouched imported files retain their line endings; browser editing or clipboard operations may normalize them.
Full URLs must start with http:// or https:// and contain no raw spaces. Query-only input may start with ?. Changing the source or space interpretation requires parsing again.
Input and converted output: up to 1 MiB each. UTF-8 text files only. No links are visited and no conversion history is saved.
Make the meaning visible.
Your converted text or rebuilt query appears here, with complete copy and download options.
COMPONENT / URI / FORM VALUE
YOUR RESULT
Encoding is not encryption. Query editing can change signed links, tracking and page behaviour. Check the result before sharing it.
EDIT THE DETAILS
One row. One parameter.
Rows are shown in their original order, including duplicates and empty separators. Leave “Include =” off for a bare flag. Fields use \n, \r, \t, \uXXXX and \\ escapes to preserve control characters and backslashes; ordinary text needs no quotes.
Tracking removal affects utm_* and the explicit click/campaign keys listed below. It is optional. Sorting keeps the relative order of rows with the same key. Rebuilt percent escapes may use a different spelling from the input.
Read a long link.
Decode once or inspect ordered query rows. See repeated keys, flags and empty values without automatically opening the link.
Make deliberate edits.
Add, reorder or remove parameters. Export a complete link or a JSON/CSV report and verify it before use.
Understand each character.
Which encoding mode should I choose?
For one URL component, such as a query value, use RFC 3986 component mode: only letters, digits, hyphen, period, underscore and tilde stay unescaped. URI syntax mode follows JavaScript encodeURI/decodeURI and preserves reserved separators such as /, ?, #, & and =. It is not a complete URL validator or hostname converter. Form value mode uses the application/x-www-form-urlencoded character set, with spaces as + and literal plus signs as %2B.
Why does a plus sign sometimes become a space?
A + is a space in form-style query encoding, but a literal plus in percent-only component decoding. Choose the intended interpretation before parsing. In the query editor, the space setting controls both how the source is read and how the output is built. Changing it requires parsing again.
Will the tool decode repeatedly or repair invalid text?
No. Each conversion decodes exactly once. For example, %252F becomes %2F in component mode, not a slash. Malformed percent escapes, invalid UTF-8 and unpaired Unicode surrogates are rejected clearly. The tool does not silently insert replacement characters or trim text. Encoded control characters are retained as data.
Are duplicate parameters and empty values kept?
Yes. The query editor preserves ordered duplicate keys, empty keys, empty separators and the difference between flag and flag=. It splits a row at the first = only. An empty query marker and the original full-URL prefix and fragment are retained. Query escapes are regenerated, so percent-escape case and space spelling may change.
How do I edit newlines, tabs or backslashes in a parameter?
Query fields show escaped text so single-line browser inputs cannot silently drop line endings. Use \n for newline, \r for carriage return, \t for tab, \uXXXX for a four-digit Unicode escape and \\ for a literal backslash. Ordinary text and quotation marks are entered normally. Invalid escapes produce an error. Exported URLs encode the resulting characters correctly.
Which tracking keys can be removed?
Only when you choose Remove tracking keys, the editor removes keys starting with utm_ and these exact keys, ignoring case: gclid, dclid, gbraid, wbraid, fbclid, msclkid, ttclid, twclid, mc_cid and mc_eid. Other parameters remain. This does not remove all possible tracking. Editing, sorting or removing parameters can break signed links or change page behaviour; verify the result at its intended destination.
What are the input limits and export options?
Input and converted output are each limited to 1 MiB of UTF-8 text. Encoding can increase the size and exceed the output limit. Batch mode supports up to 1000 lines. Untouched imported text keeps CRLF, LF and CR separators, including empty lines. Pasting or editing in a browser may normalize line endings; copy/paste can also vary by platform. Downloads preserve the converted UTF-8 text. The query editor supports 200 rows and 65536 UTF-16 code units per decoded key or value. Copy or download complete output; export ordered query rows as JSON or CSV. Formula-like CSV cells gain an apostrophe. Spreadsheet apps may still interpret numbers or dates; use JSON to retain exact text values.
Are links opened or sent to a server?
No. This tool processes your text locally and does not request, navigate to, check status codes for or validate ownership of entered URLs. No conversion history is saved to browser storage. Query Undo/Redo keeps up to 50 valid versions in memory, with a 4 MiB history budget; parsing a new source or clearing removes them. Normal site analytics and feedback services may still load. Encoding is not encryption, and decoded text is not proof that a link is trustworthy.