Work with URL components and duplicate query parameters

How to use the workspace

1. Choose parse, build, encode or decode.
2. For build, enter an absolute base URL and add name/value pairs in their intended order. Decide whether to replace the existing query.
3. For encoded text, choose URI-component or form rules. Review the resulting text and parsed fields.

A concrete starting point

https://example.com/search?tag=network&tag=security
Two tag parameters remain two ordered pairs.
Form spaces: +    URI-component spaces: %20

The example is displayed as text in the tool and is never automatically opened.

Read the result carefully

Duplicate query parameter names can be meaningful. The table preserves those pairs rather than collapsing them into one object property. A URL parser also distinguishes path, query, fragment, hostname and credentials.

Common mistakes to avoid

• A plus sign has form-encoding semantics; it is not universally a space.
• A fragment is not the same thing as a query parameter.
• URLs may contain tokens or credentials. This local tool does not fetch them, but copying or downloading can expose them elsewhere.

Limits & privacy

Absolute URLs up to 16,384 characters and up to 1,000 ordered parameters. General encode/decode text is bounded to 1 MiB. No navigation or remote requests.