Percent-encode Arabic text, spaces, and symbols so they are safe inside any URL.
Encodes everything, including ? & = # / — safe for a value inside a query string.
The result appears here as you type.
Need the reverse? Try the URL decoder.
A URL can only safely contain a limited set of characters. Spaces, Arabic and other non-Latin letters, and reserved symbols like ? & = # all need to be percent-encoded — replaced with a % and a hex code — so the address is understood correctly by browsers and servers. This tool does that conversion instantly.
The mode you pick matters. “Query value” encodes a single piece of text you are dropping into a query string — a search term, a name, a redirect target — so even a / or & inside it cannot break the surrounding URL. “Whole URL” keeps the structural characters, so you can clean up an address without dismantling it.
Encode a value once, at the moment you place it into the URL. Encoding an already-encoded value produces %2520 in place of a space and usually breaks the link — the most common URL bug there is.
Putting an Arabic search term or a phrase with spaces into a ?q= parameter needs query-value encoding so the link holds together.
A mailto: link with a subject and body, or a pre-filled WhatsApp message, needs its text encoded so line breaks and symbols survive.
When one URL carries another as a ?redirect= value, the inner URL must be query-value encoded so its own ? and & do not leak out.
URL encoding (percent-encoding) replaces characters that are unsafe or reserved in a web address with a “%” followed by two hex digits — a space becomes %20, an Arabic letter becomes a sequence like %D9%85. It lets any text travel safely inside a URL.
“Query value” encodes everything, including / ? & = # — use it for a single value you are placing inside a query string. “Whole URL” leaves those structural characters intact so a complete address stays valid. Pick query-value mode when in doubt about a single field.
Double-encoding happens when you encode an already-encoded string — %20 becomes %2520. It usually breaks the link. Encode a value exactly once, at the point you insert it into the URL, and decode it once on the other side.
No. URL encoding is not encryption — it is fully reversible by anyone, and it changes nothing about privacy or security. It only makes text safe to place in a URL. To protect data you need HTTPS and proper encryption, not encoding.
Yes. Encoding happens entirely on your device with the browser’s built-in functions — nothing you type is sent to a server or stored anywhere.
Dynamic QR codes let you change the destination anytime — no reprinting — and show you every scan: when, where, and on which device. Try the full QRA studio free for 14 days.