online URL encode decode
URL Encode/Decode
Quick start: URL Encode/Decode in 3 steps
- Paste the string to encode or decode
- Run encode/decode and inspect the output
- Copy into a browser, curl, or config to verify
URL Encode/Decode: curated examples
- •Example: encode `hello 世界` for a `?q=` parameter.
- •Example: decode double-encoded `%2520` from logs when redirects break.
About URL Encode/Decode
Encode URL text as percent escapes or turn escaped content back into readable text. The page handles full links and individual parameters, and flags invalid escape sequences.
It is especially useful for query values: spaces, &, #, and non-ASCII characters cannot simply be concatenated into them.
How URL Encode/Decode works
Browser-console encodeURIComponent, scripts, and CLI tools are appropriate when encoding belongs in a repeatable flow. For inspecting one link or testing one parameter, comparing both forms on a page is clearer.
Do not blindly encode an entire URL as a parameter value. Usually the protocol, path, and separators stay intact; encode each parameter key and value instead, or https:// becomes data too.
Why use URL Encode/Decode on WoDeTool
WoDeTool keeps URL Encode/Decode, related utilities, clipboard detection, and pipelines together, so you can work through JSON, JWT, and Diff in one workspace.
Use Smart Clipboard on the home page to auto-detect pasted JSON, Base64, or JWT and jump to URL Encode/Decode. Save a tool pipeline to chain URL Encode/Decode with related utilities. Read our guides for real-world workflows.
Common use cases
- •Build a search parameter: Encode C# 入门 & 进阶 for a ?q= value so # and & do not change URL semantics.
- •Check a callback URL: Decode redirect_uri=https%3A%2F%2Fexample.com%2Fdone in an OAuth callback to verify its destination.
- •Reproduce a logged request: Turn /search?q=%E5%8C%97%E4%BA%AC back into the actual query, 北京.
Related tutorials
Frequently asked questions
- Is URL Encode/Decode free to use?
- Yes. URL Encode/Decode on WoDeTool is completely free with no sign-up required. Open the page and start using it immediately.
- When must I URL-encode?
- Encode query/path values that contain spaces, non-ASCII, or reserved characters like `&`, `=`, `#` — otherwise servers may truncate or misparse.
- encodeURI vs encodeURIComponent?
- This page encodes text like encodeURIComponent (component style). If you only need a query value encoded, paste that value — not the full URL.
Tell us what tool you want and we'll prioritize it
Feedback →