Does this encode a whole URL or just a value?
It's built for encoding a single value, like a query parameter — encoding a whole URL will escape its slashes and question mark too.
Developer Tools
Percent-Encode a URL Component
Percent-encode text or a URL component for safe use in a query string, right in your browser.
Why this escapes more than you might expect
This tool uses JavaScript's encodeURIComponent, which escapes a broader set of characters than you might expect — including /, ?, &, and = — because it's designed for encoding a single value that will be placed inside a URL, like a query parameter, not for encoding an entire URL that already contains those structural characters.
That distinction matters: if you encode a complete URL (like https://example.com/page?id=1) with this tool, the slashes and the question mark get escaped too, which usually isn't what you want. Encode just the value part — the bit that goes after `?key=` — not the whole address.
Workflow at a glance
Use this quick flow to understand where the tool fits in your work and what to review before relying on the output.
Review checklist
Before
Confirm you're encoding a single value for a query parameter, not trying to encode a whole URL.
After
Decode the result with URL Decoder to confirm it matches your original text exactly.
When to encode a value before using it
Use it when you need to safely include a piece of text — a search term, a name, a value with special characters — as part of a URL's query string, without those characters breaking the URL's structure.
Who needs URL encoding
Developers building query strings
Safely encode a value before appending it to a URL as a query parameter.
Anyone constructing a share link
Encode a title or message that will be passed as a URL parameter.
Support engineers
Encode a value to reproduce or test a URL from a bug report.
Students learning about URL encoding
See exactly which characters get escaped and why.
What this encoder does
Uses encodeURIComponent
Escapes a wide set of special characters, appropriate for encoding a single query value.
Instant encoding
Output updates as you type.
Escapes /, ?, &, and =
These structural URL characters are encoded too, since this targets component values, not full URLs.
Runs entirely client-side
Nothing you type is sent to a server.
Encoding a value step by step
- 1Type or paste the value you want to encode.
- 2Read the percent-encoded result as it updates automatically.
- 3Copy the encoded value.
- 4Append it to your URL's query string, not the whole address.
Where URL encoding gets used
Safely encoding a value before appending it to a URL as a query parameter.
Encoding a title or message that will be passed as a URL parameter in a share link.
Encoding a value to reproduce or test a URL from a bug report.
Seeing exactly which characters get escaped and why.
Where your text goes
Encoding happens directly in your browser using encodeURIComponent — nothing you type is sent to a server.
Encoding the right part of a URL
- Encode just the value going into a query parameter, not the entire URL including its slashes and question mark.
- Test with a value containing spaces, ampersands, or slashes to see exactly how those get escaped.
- Use URL Decoder afterward to confirm the encoded value decodes back to your original text.
- Check whether your specific use case needs encodeURI instead, which escapes fewer characters and is meant for whole URLs.
URL encoding mistakes to avoid
Encoding an entire URL instead of just a value
This escapes slashes and question marks too, which breaks a full URL's structure — encode only the component value.
Assuming this matches encodeURI
encodeURIComponent (used here) escapes more characters than encodeURI, which is meant for whole URLs.
Forgetting to decode on the receiving end
The value needs to be decoded again wherever it's read, or it will appear as the encoded string.
Double-encoding an already-encoded value
Encoding a value twice produces %25 sequences instead of the original characters when decoded once.
Encoding a value versus a whole URL
URL Encoder is built for encoding individual query values safely, not entire URLs. Keep that distinction in mind, and pair it with URL Decoder to confirm a full round-trip works as expected.
Need hands-on help?
Get help with documents, SEO, content, or website fixes
Use this tool for quick work. If you need a real file prepared, a page reviewed, or a website issue fixed, send the URL and describe the problem.
FAQ
URL Encoder FAQ
Answers for using URL Encoder on I Love Tool XYZ.
Which characters get escaped?
A broad set including /, ?, &, and =, since encodeURIComponent targets component values, not full URLs.
Is this the same as encodeURI?
No, encodeURIComponent (used here) escapes more characters than encodeURI.
Is my text sent to a server?
No. Encoding happens entirely in your browser.