Query string builder
Spaces, symbols and Arabic letters are encoded for you so the link does not break when shared or sent to an API.
Loading the tool…
Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.
How to use it
- Enter parameters (name=value per line), encoding and base url (optional).
- The result appears straight away and updates as you edit.
- Copy the result, or copy a link that keeps the same values to share it.
How it is calculated
Each name and value is UTF-8 percent-encoded. RFC 3986 mode writes a space as %20; form mode (application/x-www-form-urlencoded) writes it as +. Pairs are joined with &.
Example
Inputs: Encoding = RFC 3986 (space as %20), Base URL (optional) = https://example.com/search. Result: Query string: q=%D8%AD%D8%A7%D8%B3%D8%A8%D8%A9%20%D8%B6%D8%B1%D9%8A%D8%A8%D8%A9&page=2&sort=price%20asc; Parameters: 3.
q=حاسبة ضريبة page=2 sort=price asc
q=%D8%AD%D8%A7%D8%B3%D8%A8%D8%A9%20%D8%B6%D8%B1%D9%8A%D8%A8%D8%A9&page=2&sort=price%20asc
Limits and caveats
- Each line splits at the first = only, so values may contain = safely.
- Leading and trailing spaces around names and values are removed.
Questions about this tool
When should I use + versus %20?
Use %20 for links and APIs in general, and + when mimicking an HTML form sent with GET. Servers usually accept both in the query.
Can the same name repeat?
Yes. Put each value on its own line with the same name, like tag=a then tag=b.
Why do Arabic letters turn into %D8 codes?
URLs carry text as UTF-8 then percent-encoding; browsers show it as Arabic again in the address bar.