URL Encoder/Decoder
Encode or decode URLs for safe transmission
Input
Paste your URL or text here
Adjust encoding and decoding behaviour to mirror production services, marketing tooling, or compliance pipelines.
Decode options
Input → Plain textUse for modern web payloads, emojis, and multi-language text.
Preserve newline-delimited payloads—ideal for batched tokens or log exports.
Live decode
Process text instantly using native browser APIs.
Output
Encoded or decoded result
Output will reflect whichever action you run next.
Decode files from URL-encoded format
Upload text files that contain percent-encoded content. We decode everything locally so you can review sensitive exports, webhook payloads, or CSV backups without leaving your browser.
Click or tap to select a file
We'll process the file instantly and prepare a decoded download for you.
Useful when each line contains a standalone query string or token.
Best practices
- Keep an original copy of the encoded file before transforming it.
- Verify the decoded file in a sandboxed environment before executing binaries.
- Match the character set to the system that produced the export to avoid garbled text.
- Need to re-encode? Use the download alongside the main tool to round-trip cleanly.
Decode tangled links in seconds
Our URL Encode & Decode tool translates unreadable query strings, campaign URLs, and signed tokens back into plain text—and performs the reverse when you are ready to ship. Built for developer toolkits and marketing teams alike, it keeps data consistent with how browsers implement RFC 3986.
Under the hood we rely on UTF-8, the standard encoding for web content. That means names like François, emojis, and multi-language messages return the exact byte pairs remote services expect, without extra configuration.
- Everything local
- All processing happens in your browser—paste sensitive URLs without risk.
- Character smart
- Highlights which symbols must be escaped and why certain bytes change length.
- Workflow ready
- Copy, share, or archive output directly from the panel alongside input snippets.
How percent-encoding actually works
Turning characters into web-safe bytes is a predictable two-step dance. Use this sequence to diagnose mismatched payloads or handshake errors when integrating with APIs:
- Convert each character to bytes using UTF-8 (or the declared character set). Multibyte glyphs—like ç—expand into several hex pairs.
- Translate every byte that is not an ASCII letter or digit into a percent triplet. For example, the UTF-8 bytes
C3andA7for ç become%C3and%A7in the final URL.
Browsers and HTTP clients render the decoded version to users but send the encoded bytes on the wire. Long sequences are normal—some Unicode characters can expand into nine printable characters once encoded.
Quick encoding example
See the before and after
Input: François & co.
UTF-8 bytes: 46 72 61 6E C3 A7 6F 69 73 20 26 20 63 6F 2E
Encoded: Fran%C3%A7ois%20%26%20co.
Decoding checklist
Keep results reliable
- Trim stray whitespace before decoding multi-line payloads.
- Identify the target character set via the
Content-Typeheader. - Re-encode after edits to avoid double-decoding edge cases.
- Log failures with the original encoded string for reproducible bug reports.
Character reference at a glance
Memorize these sets to know when encoding is mandatory and when you can keep characters in their original form. The guidance mirrors RFC 3986 and modern browser behavior.
Reserved characters
Escape for literal usage
! * ' ( ) ; : @ & = + $ , / ? # [ ]
These symbols control routing and parameter structure. Percent-encode them when the intent is to store them as data rather than separators.
Unreserved characters
Safe without encoding
A–Z a–z 0–9 - _ . ~
Keeping these characters literal improves readability and keeps URLs short. Encoding them is optional but rarely beneficial.
Common percent codes
Handy when debugging
- Space
- %20 or +
- New line
- %0A / %0D%0A
- Percent
- %25
- Curly brace
- %7B %7D
- Quote
- %22
- Hash
- %23
Use these mappings to explain why marketing attribution links or API signatures change length after encoding.
When you should encode (and when you can skip it)
Form submissions using application/x-www-form-urlencoded replace spaces with plus signs and normalize newlines. REST and GraphQL clients usually send plain UTF-8 but still require percent-encoding for reserved characters. When the payload travels through email, chat apps, or analytics platforms, encoding prevents accidental truncation.
Skip encoding only when every system in the chain explicitly supports raw UTF-8 and you control both ends. Otherwise, treat encoding as the default to maintain interoperability.
Real-world plays
- Marketing teams: protect UTM parameters inside QR codes and SMS links.
- Product analytics: escape JSON blobs stored in query parameters.
- Security engineers: verify signed URLs and SSO assertions before logging.
- Support desks: decode customer-provided URLs to reproduce bugs quickly.
Private by design, free forever
The encoder relies solely on client-side JavaScript. Nothing leaves your browser, so temporary tokens, signed requests, and staging credentials remain private. HTTPS encryption protects the page itself from tampering.
The tool is free to use—no sign-up, no download, no ads. Bookmark it, pin it inside your browser devtools, or share it with your team for a dependable encoding workflow.
Learn more about URL encoding
Dive deeper into standards, browser quirks, and integration guides with the resources below. They cover everything from form submissions to custom protocol handlers.
Frequently asked questions
Quick answers for product managers, engineers, and marketers dealing with encoded links in production.