Enter text or a URL above to get started
Try an example, or enter your own text above.
How to use the URL Encoder/Decoder
- Type or paste the text, query string, or encoded URL you want to convert.
- Tap Encode to percent-encode text for use in a URL, or Decode to convert it back to readable text.
- The converted output appears instantly below.
- Use the Copy or Share buttons to save or send your result.
Tip: Encode individual query parameter values, not the whole URL — encoding a full URL (including the http:// and slashes) will also encode characters that need to stay literal, breaking the URL.
Common mistakes to avoid
- Encoding an entire URL instead of just the parameter value that needs it, which breaks the http://, slashes, and domain.
- Double-encoding a string that's already encoded, turning % into %25 and corrupting the data.
- Forgetting that spaces become %20 (or + in query strings), not a literal space character.
How the URL Encoder/Decoder Works
Percent-encoding for safe URLs
URLs can only safely contain a limited set of characters. Percent-encoding (also called URL encoding) replaces any other character with a % followed by its two-digit hexadecimal code, so a space becomes %20 and an ampersand becomes %26. This tool uses the browser's built-in encodeURIComponent() and decodeURIComponent() functions, which correctly handle full Unicode text as well as reserved URL characters.
When to use this tool
Use it when building query strings with special characters, sharing a link that contains spaces or symbols, decoding a parameter value from a URL you received, or debugging why a link isn't working as expected.
✓ Pros
- Works instantly, right in your browser
- Uses the same encoding rules as real browsers and servers (RFC 3986)
- No sign-up, no ads blocking the result
✕ Limitations
- It encodes individual values, not whole URLs — encoding a full URL will also escape characters like : and / that need to stay literal.
- It doesn't validate that the resulting URL is well-formed or reachable.
- Very long inputs may take a brief moment to process since everything runs in your browser.
Common URL-Encoded Characters
What the percent codes mean
A handful of characters account for almost every URL-encoding question. Here are the ones you'll run into most often.
Frequently seen encodings
- Space →
%20(or+inside a query string specifically). - & (ampersand) →
%26, since & normally separates query parameters. - = (equals) →
%3D, since = normally separates a key from its value. - # (hash) →
%23, since # marks the start of a page fragment.
Encoding a Full URL vs. a Parameter Value
It's important to encode only the part of a URL that needs it. If you encode an entire URL like https://example.com/search?q=hello world, the slashes and colon get escaped too, breaking the link. Instead, encode just the value — "hello world" becomes "hello%20world" — and build the full URL around it: https://example.com/search?q=hello%20world. This tool is designed for that per-value use case, matching how encodeURIComponent() works in real code.
Quick Reference: Common Encodings
Exactly how a few common characters and phrases are percent-encoded:
| Plain text | Percent-encoded | Note |
|---|---|---|
hello world | hello%20world | space → %20 |
a&b=c | a%26b%3Dc | & and = are reserved |
100% off | 100%25%20off | % itself becomes %25 |
café | caf%C3%A9 | non-ASCII letters are UTF-8 encoded |
This follows RFC 3986 percent-encoding, the same standard used by browsers and web servers.
Features
Percent-encoding (RFC 3986)
Instant encode/decode
No data stored
Mobile friendly
How TickmarkTools compares
An honest, feature-by-feature look at browser-based developer tools.
| Feature | TickmarkTools | Typical free sites | Premium suites |
|---|---|---|---|
| Price | Free | Free / freemium | Free tier + paid plans |
| Sign-up required | No | Often yes | Yes |
| Data leaves your device | Never | Usually | Usually |
| Watermark on export | None | Sometimes | On free tier |
| Mobile friendly | ✓ | Varies | ✓ |
| Works without account | ✓ | Varies | ✗ |
These are general, illustrative observations about common patterns across free online calculator tools as a category — not verified or benchmarked data about any specific named competitor or product. Individual sites vary and may differ from what's shown here.
Why you can trust this tool
No data stored
Your input is never saved or logged.
Secure processing
All processing happens client-side in your browser.
Fast processing
Results render in milliseconds, no waiting.
Mobile friendly
Use this tool from any device.
No sign-up
No account, no email, no watermark.
Works offline*
Once loaded, this tool needs no internet connection.
Accuracy & limitations
This tool encodes and decodes accurately, but it's worth knowing the boundaries:
- Per-value, not per-URL. It's meant to encode individual values (like a query parameter), not an entire URL — encoding a full URL will break its structure.
- No URL validation. It doesn't check whether the resulting URL is well-formed, reachable, or points anywhere real.
- Strict decoding. Decoding will fail on malformed percent sequences, such as a stray % not followed by two valid hex digits.
URL Encoder/Decoder FAQ
Yes, the URL Encoder/Decoder is completely free with no sign-up required.
It replaces characters that aren't safe in a URL (like spaces and symbols) with a % followed by their hexadecimal code, so the URL stays valid.
No, only encode the specific value that needs it, such as a query parameter — encoding the whole URL breaks the slashes and colon that structure it.
Both are valid in different contexts. %20 is standard percent-encoding; + is a legacy convention specific to query strings and form submissions.
The string likely contains a malformed percent sequence, such as a % that isn't followed by two valid hexadecimal digits.
No. All calculations run entirely in your browser, and nothing you enter is ever sent to a server or stored.
💡 Quick Help
Tap a common question below for an instant, pre-written answer. This is a deterministic help widget, not a live AI assistant.
Can't find the tool you need?
Tell us what to build next — we ship new tools regularly.
Comments are stored locally in this browser only — they are not public and are not visible to other visitors.