URL Encoder / Decoder
Free Β· No sign-up Β· Your files never leave your browser
Percent-encode URLs and query strings, or decode them back. β followed in the tool head by: “Free, no sign-up, your result in seconds β everything runs in your browser and nothing you paste is uploaded.” (Free-tool segment: free + zero risk, and both halves are literally true for this tool.)
A URL can only carry a limited set of characters safely. Spaces, punctuation with a structural job, and non-English text all break links or change their meaning when they travel raw. Percent-encoding fixes that: every unsafe character is rewritten as a percent sign followed by two hexadecimal digits, so a space becomes %20 and an ampersand becomes %26. This tool does that rewriting in both directions: encode a URL or text into its safe percent form, or decode a percent-encoded string back into readable text.
URL Encoder / Decoder
Percent-encode URLs and query strings, or decode them back.
Free, no sign-up, your result in seconds β everything runs in your browser and nothing you paste is uploaded.
This tool uses component encoding: the whole input is treated as one value, so the URL structure characters (: / ? = # and the ampersand separator) are encoded too. That is exactly right for a query-string value or a URL nested inside another URL. It also means a pasted full link comes out fully encoded, not as a still-clickable link β the article below explains when to use it and when not to.
A URL can only carry a limited set of characters safely. Spaces, punctuation with a structural job, and non-English text all break links or change their meaning when they travel raw. Percent-encoding fixes that: every unsafe character is rewritten as a percent sign followed by two hexadecimal digits, so a space becomes %20 and an ampersand becomes %26. This tool does that rewriting in both directions: encode a URL or text into its safe percent form, or decode a percent-encoded string back into readable text.
Your files never leave your device
No uploads, no queues, no waiting
No account, no card, nothing to install
When you actually need this
The everyday case is a query-string value. You are building a search link, a redirect, or a tracking URL, and one value contains spaces or symbols: a product name like “rock & roll”, a return address that is itself a full URL, a city name in Urdu or Arabic. If that value goes in raw, the receiving server reads it wrong: the ampersand starts a new parameter, the question mark a second query string, the space can break the link. Encoding the value first keeps it in one piece.
Decoding is the mirror job. A link arrives in a log, an email, or an analytics report covered in %20 and %3D sequences, and you need to read what it says, check where a redirect goes, or spot why a parameter is malformed. Paste it, decode it, and the original text comes back.
How to use the URL Encoder / Decoder
- Paste your URL or text into the top box β a full link, a query string, or a single value are all fine as input.
- Click Encode β to percent-encode it, or β Decode to turn a percent-encoded string back into readable text.
- Read the status line. A green “β Encoded.” or “β Decoded.” confirms success. A red line explains a failure.
- Click π Copy and paste the result into your link, code, or document.
A worked example
Take this example: `https://example.com/?q=hello world&lang=ur`. Encoding it here gives `https%3A%2F%2Fexample.com%2F%3Fq%3Dhello%20world%26lang%3Dur`. Every structural character is encoded β the colon as %3A, the slashes as %2F, the question mark as %3F, the equals sign as %3D, the space as %20, and the ampersand as %26. A single value behaves the same way: `hello world` encodes to `hello%20world`, and `Ψ³ΩΨ§Ω ` encodes to `%D8%B3%D9%84%D8%A7%D9%85`, its UTF-8 bytes written as percent sequences.
The honest limit: this is component encoding, not full-URL encoding
This tool uses JavaScript component encoding (`encodeURIComponent`) and has no second mode β a deliberate choice worth understanding. Component encoding treats the whole input as one value and encodes everything with a structural job, including `: / ? = #` and the ampersand. So an encoded full link is no longer a working, clickable link. That output is exactly right when the link or text will sit inside another URL β as a query value, a redirect target, or a parameter β because there its characters must not be mistaken for structure.
If instead you have a working link whose only problems are spaces or non-English characters, and you need the link itself to stay clickable, you do not want whole-input encoding: encode only the faulty part, or use a full-URL encoder that preserves the structure characters. This page will not pretend one mode does both.
Two smaller behaviours are worth knowing. First, decoding here does not turn `+` into a space: `a+b` decodes to `a+b`. A plus meaning a space belongs to HTML form encoding, not to percent-decoding β a difference to keep in mind for form-encoded query strings. Second, malformed input fails openly: a lone `%`, bad hex like `%zz`, or a truncated sequence such as `%E0%A4%A` produces the red error “β Invalid encoding: URI malformed” and leaves your previous output untouched, rather than returning a half-decoded guess.
Frequently asked questions
Is this URL encoder and decoder really free?
Yes. Encode and decode as much as you like, with no payment, no account, and no limit. Everything runs in your browser with built-in JavaScript functions, and nothing you paste is uploaded or stored anywhere.
What does this tool encode, exactly?
It applies component encoding to the whole input. Spaces and other unsafe characters become percent sequences, and so do the URL structure characters β colon, slash, question mark, equals sign, hash, and ampersand. Letters, digits, and a small set of safe marks (`- _ . ! ~ * ‘ ( )`) pass through unchanged.
Why did my link stop working after I encoded it?
Because the whole link was treated as one value, its structure characters were encoded too, so browsers no longer read it as an address. That encoded form is meant to be placed inside another URL, for example as a redirect target or query value. To keep a link itself clickable, encode only the value or segment that needs it.
Does a plus sign decode to a space?
No. In this tool `a+b` decodes to `a+b`, and an encoded plus, `%2B`, also decodes to `+`. Treating plus as a space is a rule of HTML form submissions, not of percent-decoding, so a form-encoded string is the one case where you must allow for that difference yourself.
What does “Invalid encoding: URI malformed” mean?
It means the input is not valid percent-encoding: a percent sign is not followed by two proper hex digits, or a percent sequence is a truncated piece of a UTF-8 character, like `%E0%A4%A`. The tool shows the error, leaves your previous result untouched, and waits for you to fix the input β it never returns a partial decode.
Is the text I paste sent to a server?
No. Encoding and decoding use functions built into your browser, on your own device. There is no upload, no account, and no library or file fetched from the network when you use this tool, so it also keeps working on a saved page while you are offline.
Related tools
- Converter & Utility Tools β the full converter and utility toolbox on one page, including this URL Encoder / Decoder.
- Free Tools β every free VeloSpark Digital tool in one place.
Built by Umar Hayat β VeloSpark Digital
More Converter & Utility Tools
- QR Code Generator β free QR code generator: turn any link or text into a scannable QR code in seconds.
- Converter & Utility Tools β the full converter & utility toolbox on one page.
- Free Tools β every free VeloSpark tool, guide and category in one place.
