العودة إلى الرئيسية
المدونة

مرمّز URL

ترميز وفك ترميز عناوين URL

النمط:
النوع:

المدخل (عادي)

0 chars

أمثلة سريعة:

الخيارات

الترميز القياسي: يرمّز الأحرف الخاصة باستثناء - _ . ~

المخرج (مرمَّز)

0 chars

مرجع ترميز URL

الأحرف المحجوزة (يجب ترميزها):

! * ' ( ) ; : @ & = + $ , / ? # [ ]

الأحرف غير المحجوزة (آمنة):

A-Z a-z 0-9 - _ . ~

الترميزات الشائعة:

Space → %20 or +
@ → %40
& → %26
= → %3D
/ → %2F
? → %3F

About the URL Encoder & Decoder

A URL can only contain a limited set of ASCII characters safely — spaces, ampersands, question marks, non-Latin letters, and symbols like # or % all have to be converted into percent-encoded sequences (like %20 for a space) before they can travel reliably through a link, a query string, or an API request. This tool handles that conversion in both directions: paste a raw string and get its percent-encoded form, or paste an encoded URL and get back the readable original. It's built for the moment a developer is debugging a broken redirect, building a query string by hand, or trying to figure out what a mangled-looking link actually says.

Type or paste text into the input, and the tool converts it using standard percent-encoding rules, turning reserved and non-ASCII characters into their %XX byte sequences and decoding them back on request. It handles full URLs as well as individual query string values, so you can encode a parameter before appending it to a link or decode an entire address someone sent you to see what it really points to. Unicode text — accented letters, CJK characters, emoji — is supported in both directions, since these get expanded into multi-byte UTF-8 sequences when encoded.

A common gotcha this tool helps catch: encoding an already-encoded string turns %20 into %2520, and decoding a string that isn't actually encoded can silently strip characters that only look like escape sequences. Because everything runs client-side in your browser, nothing you paste — including tokens, session IDs, or internal URLs — is ever uploaded or logged, which makes it safe to use with sensitive query parameters.

How to encode or decode a URL

Convert text to percent-encoded form or decode an encoded URL back to plain text.

  1. 1

    Choose a mode

    Select whether you want to encode plain text into a URL-safe string or decode an already percent-encoded string back to readable text.

  2. 2

    Paste your text

    Paste the URL, query string, or parameter value into the input field.

  3. 3

    Review the conversion

    The tool instantly converts the input — encoding reserved and Unicode characters into %XX sequences, or decoding %XX sequences back into their original characters.

  4. 4

    Check the result

    Look over the output field to confirm the converted string matches what you expect, especially for special characters and non-Latin text.

  5. 5

    Copy the output

    Copy the encoded or decoded string to use in your link, API request, or code.

Frequently Asked Questions

What is URL encoding?

URL encoding (also called percent encoding) converts characters that are not allowed in URLs into a % followed by two hexadecimal digits. For example, a space becomes %20 and & becomes %26. This ensures URLs are valid and correctly interpreted by browsers and servers.

When should I URL encode a string?

Encode strings when you include them in query parameters, form data, or any part of a URL that might contain special characters like spaces, ampersands, equals signs, or non-ASCII characters. This prevents them from being misinterpreted as URL syntax.

What is the difference between encodeURI and encodeURIComponent?

encodeURI encodes a full URL and skips characters that have special meaning in a URL (like /, ?, #). encodeURIComponent encodes a URL component (like a single query value) and also encodes those special characters. Use encodeURIComponent for individual parameter values.