About this tool
A URL is composed of a scheme, host, optional port, path, query, and fragment. Manual concatenation easily introduces mistakes with slashes, question marks, equals signs, and percent encoding, especially when a value contains spaces, non-ASCII text, `&`, or another URL.
The URL builder edits these parts separately and assembles a structurally valid address. It is useful for API requests, campaign links, and callback URLs, and helps distinguish query parameters from a page fragment while avoiding missing or double encoding.
How to use it
Enter the base address
Provide the scheme and host, then add a port and path when needed.
Add query parameters
Enter each key and value separately so delimiters and required URL encoding are handled consistently.
Verify and copy
Check the final path, parameters, and fragment, then make one real request in the destination environment.
Input and output example
Note that spaces and non-Latin characters in values are percent-encoded, while the & and = delimiters stay literal.
q = jane doe
page = 2
tags = a
tags = b?q=jane%20doe&page=2&tags=a&tags=bSupported range and limits
- Two directions
- Break down an existing URL's query string, or build a new one parameter by parameter
- Automatic encoding
- Spaces, non-Latin characters, & and = in values are percent-encoded
- Repeated parameters
- The same key can appear several times (tag=a&tag=b) and all occurrences are listed in order
- Empty values
- Distinguishes "present but empty" (key=) from "not present at all"
- Fragments
- Anything after # is not part of the query string and is never sent to the server
- Privacy note
- URLs end up in logs, Referer headers and browser history; keep sensitive values out of query parameters
When you would use it
Constructing an API request
Combine pagination, filtering, and sorting options without manually juggling multiple `&` characters.
Generating a tracked link
Add campaign attribution while retaining existing query values and a page anchor.
Taking apart a callback URL that fails
When a third-party callback or redirect errors, break it down parameter by parameter to check the encoding and whether anything required is missing.
What to know before you start
- Encode parameter names and values individually. Encoding the complete URL produces a value rather than a directly navigable address.
- The fragment after `#` is normally handled by the client and is not sent in the HTTP request.
- Do not place passwords, tokens, or sensitive personal data in a query string because it can appear in history and server logs.
Related concepts
- query string
- The key-value section after `?`, with multiple parameters commonly separated by `&`.
- percent-encoding
- A percent sign plus hexadecimal bytes used to represent reserved characters and non-ASCII text safely in a URL.