URL Encoder / Decoder
Make search text and parameters safe inside links — or decode ugly %20 soup. Not a URL shortener.
Not a shortener — makes spaces and symbols safe inside links
One value — for search text or a single parameter you will put inside a URL (e.g. hello world → hello%20world).
—
Build a query string
Type keys and values — we encode them so & and spaces stay safe
How to use this tool
- Choose Encode (make text URL-safe) or Decode (make %xx readable).
- Encode a search term or parameter with One value, or a full https://… address with Whole link.
- Optional: build key/value pairs at the bottom into a safe query string.
- Copy the result into your app, docs, or API call.
What this is (and is not)
This is not a shortener and not a “disguise my link” service. It percent-encodes characters so a space or & does not break a query string. Example: hello world becomes hello%20world, which you put after ?q=. Decode does the reverse when you need to read a messy link.
FAQ
Is my URL uploaded?
No. Encoding and decoding run entirely in your browser. DevDock never sends your URLs or query strings to a server.
Is this a URL shortener?
No. A shortener creates a new short link (often hosted by someone else). This tool only percent-encodes characters — spaces become %20, & becomes %26 — so text is safe inside a URL. The destination does not change.
One value vs Whole link — which should I use?
One value is for a single piece of text you will put inside a URL (a search term or parameter). Whole link is when you already have a full https://… address and only need spaces or special characters fixed without breaking the link structure.
When do I use Space → %20 vs Space → +?
%20 is the usual choice for URLs. + is an older form-style way to mean a space in some query strings. Prefer %20 unless you need to match form-style output.
What does Keep decoding do?
Some strings are encoded twice (%2520 instead of %20). This option decodes again until the text stops changing, which unwraps nested encoding.
Is this the same as HTML encode?
No. URL encoding is for links and queries (%20). HTML encoding is for markup (&). Use each for its own job.
Escaping HTML markup instead? Try the HTML Encoder / Decoder. Building campaign URLs? Use the UTM Link Builder. Need Base64 transport encoding? Open Base64 Encode / Decode.