Reduce encoding mistakes
Encode spaces, Korean text, and special characters according to URL rules instead of concatenating strings manually.
🔒 Browser-side processing
Build encoded query strings and shareable URLs from key-value pairs.
Guide
Encode key-value pairs safely for search URLs, share links, and API test query strings.
Encode spaces, Korean text, and special characters according to URL rules instead of concatenating strings manually.
Build filters, page numbers, sorting values, and other parameters in one place to reproduce API or screen states.
Check required parameters and empty values before copying the final URL.
Workflow
Examples
Input
base https://api.example.com/search
q developer tools
page 2
Output
https://api.example.com/search?q=developer%20tools&page=2
Input
redirect https://example.com/back?id=1&t=2
Output
redirect=https%3A%2F%2Fexample.com%2Fback%3Fid%3D1%26t%3D2
The & and = inside the value must be encoded or the parameter list breaks apart.
Troubleshooting
Both usually decode to a space in a query string, but in a path a + is a literal plus. Servers differ, so %20 is the safer choice.
tags=a&tags=b, tags[]=a&tags[]=b, and tags=a,b are all in use. Which one works depends on the server framework — check the API docs first.
Review
Servers can interpret repeated keys differently. Match array parameter rules with the API documentation.
URLs can appear in browser history, logs, and previews. Avoid putting tokens or personal data in query strings.
Related