Skip to content
Entrovix AI

URL Encoder

Percent-encodes text so it survives being put in a URL, with a choice between encoding a whole URL and encoding a single parameter value.

Runs in your browser — nothing is uploaded

Input
Output

Your result appears here. Everything runs in your browser.

Why use it

Built to be genuinely useful

Two modes, because they differ

Encoding a full URL must leave : / ? & alone; encoding a value must not. Using the wrong one is the usual cause of a link that breaks on the second parameter.

Handles every character, not just spaces

Non-ASCII text is encoded as UTF-8 bytes, which is what a modern server expects and what a naive replace-spaces-with-%20 gets wrong.

Nothing is uploaded

It runs in your browser. Tokens, keys and customer data routinely end up in these tools, and none of it should have to cross a network to be decoded.

Free, no sign-up

No account, no daily cap, and no feature held back behind a paywall.

How it works

Three steps

  1. 1

    Paste the text or URL.

  2. 2

    Choose whether you are encoding a whole URL or a single value.

  3. 3

    Copy the encoded result.

The two kinds of encoding, and why picking wrong breaks links

A URL has structure: the colon after the scheme, the slashes between path segments, the question mark before the query, the ampersands between parameters. Those characters are punctuation. Encoding them turns the punctuation into text and the URL stops being a URL.

Inside a parameter value, the same characters are data. A search term containing an ampersand must be encoded, or the server reads it as the start of another parameter and the value is silently truncated at that point. This is where most broken links come from: a value encoded with the whole-URL rules, so its ampersand survived and split the query.

The practical rule is to encode each value on its own, then assemble the URL from the encoded pieces. Encoding an already-assembled URL is a repair job, and it can only guess which characters were punctuation and which were data.

Double encoding, and how to recognise it

If you see %2520 in a URL, something has been encoded twice. The space became %20, then the % of %20 became %25, giving %2520. It is a common result of a value being encoded by application code and again by a framework that assumed it was raw.

The symptom on the receiving end is a value that arrives containing a literal %20 rather than a space. Decoding once gets you back to the correctly encoded form; decoding twice gets you the original. If you find yourself decoding twice routinely, the bug is upstream.

FAQ

Questions people ask

API access

Need URL Encoding in Your Application?

Integrate URL encoding directly into your application, backend or build pipeline through API access.

Tell us what you are building, how you plan to use it and the volume you expect. We will come back to you with availability, integration details and a quote for your usage.

Need a tool like this for your business?

We build internal tools, dashboards and automation that fit how your team works.

See Our Services