When do I need URL encoding?

Any time a URL contains reserved characters (space, #, ?, &, /, :, +, =) that aren't being used in their special role. Form submissions, query strings, and API paths are the common cases — a user input with a space becomes %20 when sent as a query parameter.

What's the difference between encoding a query string and a path component?

Path components shouldn't encode the forward slash; query string components must encode &, =, +, and space as %2B or +. JavaScript's encodeURIComponent is the stricter version and usually what you want for query params.

Can I safely paste an API token or secret here?

Yes — the encoder runs entirely in your browser. Nothing is sent to a server, so you can encode bearer tokens, database connection strings, or webhook URLs without exposing them.

Developer Utilities · Free tool

URL Encoder & Decoder

Encode URLs for safe links and query strings, or decode them back to readable text. This free, no-download tool handles all percent-encoding tasks in your browser.

Updated June 2026

Input

Output

Found this useful?Email Buy Me a Coffee

What it does

A free URL encoder and decoder. Handles query strings, special characters, and Unicode safely. Everything happens in your browser.

URL encoding is required whenever you put special characters in a URL — query parameters, redirect paths, API endpoints. Errors here cause cryptic bugs; this tool saves the debugging time.

Embed this tool on your siteShow snippet

Paste this snippet into any page. Loads on-demand (lazy), no tracking scripts, and sized to most dashboards. Replace the height to fit your layout.

<iframe src="https://freetoolarena.com/embed/url-encoder-decoder" width="100%" height="720" frameborder="0" loading="lazy" title="URL Encoder & Decoder" style="border:1px solid #e2e8f0;border-radius:12px;max-width:720px;"></iframe>

Embed docs →

How to use it

Paste a URL or text in the input.
Click Encode to escape special characters.
Click Decode to un-escape percent-encoded text.
Copy the result with one click.

Frequently asked questions

When do I need URL encoding?: Any time a URL contains reserved characters (space, #, ?, &, /, :, +, =) that aren't being used in their special role. Form submissions, query strings, and API paths are the common cases — a user input with a space becomes %20 when sent as a query parameter.
What's the difference between encoding a query string and a path component?: Path components shouldn't encode the forward slash; query string components must encode &, =, +, and space as %2B or +. JavaScript's encodeURIComponent is the stricter version and usually what you want for query params.
Can I safely paste an API token or secret here?: Yes — the encoder runs entirely in your browser. Nothing is sent to a server, so you can encode bearer tokens, database connection strings, or webhook URLs without exposing them.

Learn more

Explore more developer utilities tools

100% in-browserNo downloadsNo sign-upMalware-freeHow we keep this safe →