Encode and decode URL components for safe use in query strings.
Component Encoded
—
Component Decoded
—
URI Encoded
—
URI Decoded
—
About this tool
URL encoding replaces unsafe characters with a percent sign followed by their hex value. Use this tool to encode strings for use in query parameters or to decode percent-encoded URLs. Processing is entirely browser-based.
Runs in your browser — nothing is uploaded; your input never leaves your device. How it works
Quick answer
Enter text or a URL and Tabreon shows all four common encodings at once — component-encoded, component-decoded, full-URI-encoded, and full-URI-decoded — so you can pick the right one for query strings, paths, or whole URLs.
Why use Tabreon for this?
All four encode/decode variants are computed at once, so you don't have to guess which one you need.
Runs entirely in your browser — nothing you type is sent to a server.
No account, no limit on how much you can encode or decode.
How to URL-encode or decode text
1Enter your text or URL. Type or paste the string you want to encode or decode.
2Review all four outputs. Component Encoded/Decoded and URI Encoded/Decoded update live as you type.
3Copy the variant you need. Use component encoding for a single query parameter, or URI encoding for a whole URL.
What is URL encoding?
URL encoding (percent-encoding) replaces characters that aren't safe in a URL — spaces, "&", "?", "#", and others — with a "%" followed by their hex code. Component encoding (encodeURIComponent) escapes every reserved character, making it correct for a single query parameter value. URI encoding (encodeURI) leaves URL-structural characters like "/", ":", and "?" untouched, making it correct for encoding a whole URL.
How Tabreon handles your data
All four encode/decode variants are computed in your browser using its native encodeURIComponent and encodeURI functions — nothing you type is sent to a server.
Key features
Four simultaneous outputs: component encode/decode and full-URI encode/decode
Live results as you type
Clear error messages for malformed percent-encoded input
Common use cases
Encoding a search query or redirect URL before appending it to a query string
Decoding a percent-encoded URL captured from server logs or browser history
Checking whether a URL segment needs component encoding or full-URI encoding
Common mistakes & limitations
Component and URI encoding are genuinely different operations — using the wrong one for your context (for example, component-encoding a whole URL) will over-escape structural characters like "/" and ":".
Frequently asked questions
Component encoding escapes every reserved character and is meant for a single value inside a query string. URI encoding preserves URL-structural characters ("/", ":", "?", "&") and is meant for encoding an entire URL.
No, all encoding and decoding happens locally in your browser.
The input contains a "%" not followed by two valid hex digits, which isn't valid percent-encoding.