URL Encoder / Decoder
Component mode encodes every reserved character (: / ? # & = etc.) — use it for a single value like a query parameter.
| Key | Value |
|---|---|
| q | hello world |
| lang | ja |
Related external tools
Some links are affiliate links.
Related tools
Encode text and URLs for safe use on the web, or decode percent-encoded URLs back to readable text. Switch between component mode (for a single value) and full-URL mode (which keeps the URL structure), and break any query string into its key/value pairs. Everything runs in your browser; nothing is uploaded.
How to use
- Choose a direction: Encode or Decode.
- Pick a mode — Component for a single value, or Full URL to keep the URL structure.
- Type or paste your text and copy the result; a query string is broken down automatically.
How URL encoding works
URLs may only contain a limited set of characters, so anything else — spaces, accents, symbols — is replaced by a percent sign and a hex code (a space becomes %20). Component encoding escapes reserved characters like : / ? # & = as well, which is right for a single parameter value. Full-URL encoding leaves those structural characters intact so a whole URL stays valid.
Features
Encode & decode
Convert text to percent-encoding and back again with a single toggle.
Component & full modes
Encode a single value strictly, or a whole URL while keeping its structure.
Query string parser
Paste a URL and instantly see its query parameters as a tidy key/value table.
Clear errors
Malformed percent sequences are reported instead of silently producing garbage.
Fully local
All encoding and decoding happens in your browser — nothing is ever sent to a server.
When to use it
Build query URLs
Safely encode values like search terms or names before putting them into a URL.
Read encoded URLs
Turn a URL full of %20 and %2F back into readable text to see what it really says.
Check parameters
Inspect UTM tags and other query parameters by splitting a long URL into pairs.
Debug APIs
Encode or decode request values while testing an API endpoint by hand.
Notes
- Component mode encodes reserved characters; full mode preserves the URL structure.
- In query strings, a plus sign is treated as a space when parsing.
- Invalid percent sequences (like a lone %) produce an error rather than a wrong result.
- All processing runs on your device; nothing you enter is uploaded.
FAQ
- What is the difference between component and full URL mode?
- Component mode encodes every reserved character, so it is right for a single value. Full-URL mode keeps structural characters like : / ? # intact so an entire URL stays valid.
- What does %20 mean?
- It is the percent-encoded form of a space. Each unsafe character is written as a percent sign followed by its two-digit hex code.
- Is a plus sign the same as a space?
- In query strings, a plus is commonly used for a space, so this tool converts + to a space when parsing parameters.
- What happens with a broken URL?
- If the text contains an invalid percent sequence, decoding fails gracefully and shows an error message instead of a wrong result.
- Is my data sent to a server?
- No. Encoding, decoding and parsing all happen locally in your browser.