Question 1

What is URL encoding?

Accepted Answer

URL encoding (percent encoding) converts characters that are not allowed or have special meaning in URLs to a % followed by their two-digit hexadecimal ASCII code. For example, a space becomes %20 and an ampersand becomes %26.

Question 2

When do I need URL encoding?

Accepted Answer

You need URL encoding whenever you pass special characters (spaces, &, =, ?, #, +) as values in query strings, form submissions, or API parameters. Without encoding, these characters would be interpreted as URL syntax rather than data.

Question 3

What is the difference between encodeURI and encodeURIComponent?

Accepted Answer

encodeURI encodes a complete URL and leaves structural characters (/, :, ?, #, &) intact. encodeURIComponent encodes everything including those structural characters, making it suitable for encoding individual query parameter values.

Question 4

Why does a space sometimes appear as + in URLs?

Accepted Answer

The + sign is an older, HTML form-specific way to encode spaces in application/x-www-form-urlencoded data. Standard percent encoding uses %20. Both are widely used, but %20 is correct in URIs per RFC 3986.

Question 5

Is URL encoding the same as Base64 encoding?

Accepted Answer

No, they serve different purposes. URL encoding converts individual characters to %XX hex format for safe inclusion in URLs. Base64 encoding converts binary data to a set of printable ASCII characters for transport in text-based protocols.

Question 6

Can I encode an entire URL?

Accepted Answer

You can, but typically you should only encode individual query parameter values. Encoding a full URL will also encode the scheme, slashes, and dots, making it invalid as a URL. Use the full URI mode if you need to encode a URL while preserving its structure.

Question 7

Is my data sent to a server?

Accepted Answer

No. All encoding and decoding is performed locally in your browser using the built-in encodeURIComponent and decodeURIComponent JavaScript functions. No data is transmitted or stored.

Question 8

What characters are not encoded?

Accepted Answer

Unreserved characters — letters (A–Z, a–z), digits (0–9), hyphen (-), underscore (_), period (.), and tilde (~) — are never encoded because they are safe in URLs. All other characters are percent-encoded.

ترميز / فك ترميز URL

كيفية استخدام ترميز / فك ترميز URL

حول ترميز / فك ترميز URL

المميزات الرئيسية لـ ترميز / فك ترميز URL

الصيغ المدعومة

أمثلة

حالات الاستخدام الشائعة

استكشاف الأخطاء

الأسئلة الشائعة

ما هو ترميز URL؟

متى أحتاج إلى ترميز URL؟

ما الفرق بين encodeURI وencodeURIComponent؟

لماذا تظهر المسافة أحياناً كـ + في URLs؟

هل ترميز URL مثل ترميز Base64؟

هل يمكنني تشفير عنوان URL كامل؟

هل يتم إرسال بياناتي إلى خادم؟

ما الأحرف التي لا يتم ترميزها؟