URL Params Editor
URL Params Editor — runs in your browser. Inputs are not stored.
Edit URL query parameters
How to use
- Paste the full address in the URL field. Example: https://example.com/path?a=1&b=2
- Press Parse to split query keys into rows. Invalid addresses are handled with a fallback.
- Edit keys and values, or press Add row to add a parameter. The same key can appear on several rows.
- Press Build URL to create the result URL and Copy it. Encoding follows browser rules.
- To assemble UTM only, use the UTM builder; to inspect host and path only, use the URL parser with this tool.
Key concepts
URL parameter editing is for fixing campaign queries, API endpoints, and search filters in a table. Parsing and serializing use URLSearchParams, so spaces and Hangul are encoded automatically when you build. Hash (#) handling follows the URL constructor. It is a parameter editor that lets you change keys and values of campaign UTM, search queries, and API callback URLs in a table and produce a newly encoded address. It rebuilds an encoded URL after you edit the query string row by row. It does not send a real HTTP request.
It only concatenates strings and does not request a server. There is no dedicated UTM field set; any key is allowed. After parsing, edit the rows and press Build URL to refresh the result field. Spaces and Hangul are encoded on serialize. After parsing, change values and press Build URL so the result field updates. The same key can sit on several rows.
Example
Parsing https://example.com/search?q=한글&page=1 creates q and page rows. Change page to 2, add a row for sort=new, then press Build URL to fill the result with the encoded new address. Copy it into the browser address bar. Parsing https://shop.example/item?id=10&ref=ad, changing ref to mail, and adding sort=price yields three query pairs. Changing only utm_source and adding a row for utm_campaign lets you assemble a campaign URL.
Related: UTM builder · URL parser
Frequently asked questions
Are URL hash (#) fragments kept?
Behavior follows the URL constructor, and invalid URLs use a fallback. Hash fragments follow the URL constructor implementation.
What happens if the same query key appears more than once?
Multiple rows are kept as they are. Two rows with the same key remain duplicate query parameters and are serialized as-is.
Do I have to encode the query myself?
Encoding is automatic when you build. You usually do not need to type percent-encoding by hand. Hangul values are encoded when building.
Is the edited URL requested from a server?
No. Only a string is created. The built address is not actually requested and is not sent to a server.
Can I enter only UTM parameters?
You can enter them as ordinary keys. There is also a UTM builder tool. For UTM only, the UTM builder can be simpler. The UTM-specific UI is in the UTM builder.
Can I press Build URL without parsing first?
If the rows are empty, you get an address with no query. Parsing first is safer. Skipping parse can leave the rows empty and drop the existing query.
Last reviewed: 2026-09-04