URL Parameter Editor
Parse every part of a URL and edit query params in a table — change values, delete or add params and rebuild the link live, with auto-encoding.
>_ USAGE GUIDE
Paste a complete URL and it breaks into protocol, domain, path, and every query parameter, presented as an editable table. Change values, delete rows, add parameters — and the full link reassembles in real time. Far faster than hunting for & and = in the address bar, and non-ASCII values are percent-encoded automatically on rebuild.
- Paste the URL: every component is extracted and listed as a table row
- Edit the parameters: modify values, remove tracking params, or add new ones directly in the table
- Copy the rebuilt link: encoding is applied automatically, ready to use
Typical scenarios: batch-tuning parameter values during integration (page numbers, tokens, environments), analyzing the tracking parameters on a competitor's landing page, and cleaning useless parameters out of shared links. Marketing teams use the same table view to audit UTM tagging before a campaign launch — a mislabeled source or medium is invisible in the live URL but obvious in the table. Parsing and rebuilding run locally, so links containing tokens never leave your device.
>_ FAQ
Q1 · What are the parts of a URL called?
Standard structure: protocol://domain:port/path?query#fragment. The query string is the set of key=value pairs after ?, joined by &. This tool splits each piece out and lists every parameter on its own row, so one glance tells you what a link carries and where it points.
Q2 · Will edited parameters with Chinese text come out garbled?
No. Values are percent-encoded per the standard on rebuild (%E4%BD%A0... form), producing a working link. The reverse also holds: encoded parameters pasted in are decoded for display, so the table always shows the human-readable version while the rebuilt URL keeps the wire-safe form.
Q3 · What is a punycode domain (starting with xn--)?
Internationalized domains — ones containing non-ASCII characters — must be represented in pure ASCII inside DNS, and that representation is punycode, like xn--fiq228c.com. This tool recognizes it and shows the original internationalized form; parsing and rebuilding are transparent. Decoding any xn-- link before judging it is also a basic anti-phishing habit.
Q4 · Why did the page behave differently after I deleted a parameter?
Parameters are inputs the page runs on: removing token causes unauthorized errors, removing id loses the resource, and removing utm_* only affects analytics. Safe-to-clean parameters are trackers — utm_, spm, from and friends; functional parameters such as id, token, and code should be confirmed before deletion.
Q5 · Can I use this to build signed API links?
Editing and rebuilding ordinary parameters is exactly its job — but never hand-edit signature parameters like sign or signature. Signatures are computed over the parameter set with a key and a specific ordering rule, so touching any field breaks server-side verification. For signed requests, use the system's signing SDK; this tool suits signature-free parameter work.