Encode spaces in plain text
Input
hello world
Output
hello%20world
Useful when spaces must be safe inside a URL or parameter value.
Developer Tools
Review practical URL Encoder examples so you can understand expected input, output, and common patterns faster.
Use this free URL Encoder to convert unsafe characters into percent-encoded text for URLs, query parameters, redirects, and request values. It is useful when preparing links, encoding spaces and symbols, building tracking URLs, debugging API calls, and making sure special characters are transmitted safely inside web addresses. Paste text or a full URL to encode it instantly in the browser.
Example pages are especially useful for developer tools because they show what good input looks like, what kind of output to expect, and how the tool behaves in common scenarios.
Input
hello world
Output
hello%20world
Useful when spaces must be safe inside a URL or parameter value.
Input
name=John & role=admin
Output
name%3DJohn%20%26%20role%3Dadmin
Helpful when building parameter values that contain equals signs, ampersands, or spaces.
Input
https://example.com?a=1&b=2
Output
https%3A%2F%2Fexample.com%3Fa%3D1%26b%3D2
Useful when a URL itself needs to be passed as a parameter value.
Input
https://example.com/login?next=/dashboard
Output
https%3A%2F%2Fexample.com%2Flogin%3Fnext%3D%2Fdashboard
Useful for redirect flows where one URL must be safely embedded inside another.
Input
email=user@example.com?x=1&y=2
Output
email%3Duser%40example.com%3Fx%3D1%26y%3D2
Helpful for debugging how reserved characters are encoded before sending them.
Input
Hello world
Output
%D0%9F%D1%80%D0%B8%D0%B2%D0%B5%D1%82%20%D0%BC%D0%B8%D1%80
Useful when non-English text must be included in a link or parameter safely.
Input
{"name":"John","role":"admin"} Output
%7B%22name%22%3A%22John%22%2C%22role%22%3A%22admin%22%7D
Useful when sending structured text through a query parameter.
Input
line one line two
Output
line%20one%0Aline%20two
Helpful for checking how multiline text is represented after URL encoding.
Fix: Decide whether you need to encode the whole string or just one parameter value before copying the result.
Fix: Use Base64 tools only when the target system specifically expects Base64, not percent-encoded text.
Fix: Decode the value first or confirm whether it has already been encoded before running the tool again.
Fix: Reserved characters may be encoded depending on the context and how the value will be used.
Fix: Trim the input first if exact encoded output matters.
After reviewing these examples, run the live tool with your own input. If your task involves a follow-up step, the related page can help you move to the next tool in the workflow.
Open the main URL Encoder page and test your own real input.