Numbers, dates and currency in Arabic interfaces

Format numbers, prices and dates for Arabic users with Intl.NumberFormat and Intl.DateTimeFormat: which digits each market expects, and the traps.

By Sohail Hussain21 November 20265 min read

Decide for each market which digits to show, then let the browser's Intl API do the formatting, with the numbering system and calendar set explicitly rather than left to the locale's defaults. As of October 2026, the locale data in current browsers gives Western digits (0 to 9) for ar-AE and Eastern Arabic digits (٠ to ٩) for ar-SA and ar-EG, and those defaults have changed between versions before. In Arabic, the currency symbol follows the number, month names differ by region, Arabic has six plural forms, and phone numbers always stay left to right.

These details decide whether an Arabic interface feels native or translated. They are part of every Arabic and multilingual website we build, and part of the content checklist in the guide to building an Arabic website.

Which digits should an Arabic site use?

Arabic script is written with two digit styles. Western digits (0123456789) are the same ones English uses. Eastern Arabic digits (٠١٢٣٤٥٦٧٨٩) are separate characters with their own separators: ٬ for thousands and ٫ for the decimal point.

The Intl API picks a style from the locale. Formatting 1234567.891 with the default settings gives:

LocaleDefault digitsOutput
ar-AE (UAE)Western1,234,567.891
ar-SA (Saudi Arabia)Eastern Arabic١٬٢٣٤٬٥٦٧٫٨٩١
ar-EG (Egypt)Eastern Arabic١٬٢٣٤٬٥٦٧٫٨٩١
ar-MA (Morocco)Western, with . for thousands and , for decimals1.234.567,891
ar (no region)Western in current data1,234,567.891

These outputs come from Node.js 24 with CLDR 48 locale data. The plain ar row is the reason to stop trusting defaults: older browsers return Eastern Arabic digits for it. A visitor on an older phone and one on a new laptop can see different digits on the same page unless you choose.

Which to choose is a business decision, not a technical one. UAE business sites mostly use Western digits. In Saudi Arabia and Egypt both styles are common. Ask the client what their invoices, signage and brochures use, and apply that everywhere.

How do you format numbers and prices?

Use Intl.NumberFormat, documented on MDN, and pass numberingSystem so the digit style is your decision:

js
const n = 1234567.891;

new Intl.NumberFormat("ar-AE").format(n); // "1,234,567.891"
new Intl.NumberFormat("ar-SA").format(n); // "١٬٢٣٤٬٥٦٧٫٨٩١"
new Intl.NumberFormat("ar-EG").format(n); // "١٬٢٣٤٬٥٦٧٫٨٩١"

// Choose the digits yourself instead of relying on the default:
new Intl.NumberFormat("ar-SA", { numberingSystem: "latn" }).format(n); // "1,234,567.891"
new Intl.NumberFormat("ar-AE", { numberingSystem: "arab" }).format(n); // "١٬٢٣٤٬٥٦٧٫٨٩١"

The same option can go in the locale tag as a Unicode extension, ar-SA-u-nu-latn, which is handy when a library only accepts a locale string.

For prices, one helper keeps every page consistent:

js
const price = (locale, currency, amount) =>
  new Intl.NumberFormat(locale, {
    style: "currency",
    currency,
    numberingSystem: "latn",
    minimumFractionDigits: 0,
    maximumFractionDigits: 0,
  }).format(amount);

price("ar-AE", "AED", 1250); // "1,250 د.إ." (plus invisible direction marks)
price("ar-SA", "SAR", 1250); // "1,250 ر.س." (plus invisible direction marks)
price("en-AE", "AED", 1250); // "AED 1,250"

In Arabic the symbol follows the number in the text, so on a right-to-left page it appears to the left of the digits. The Arabic outputs also start and end with an invisible right-to-left mark (U+200F), which keeps the symbol in place inside mixed text. To show the ISO code instead of the Arabic abbreviation, add currencyDisplay: "code"; some B2B sites prefer "AED" on both language versions for clarity.

New currency signs are arriving. The Saudi riyal sign was added to Unicode 17.0 in September 2025 as U+20C1, and the UAE introduced a new dirham symbol in 2025. Locale data still outputs the abbreviations, and a sign only displays if your web font includes it, so check font support before using either.

How do you format dates?

Intl.DateTimeFormat, also documented on MDN, handles Arabic month names, digit styles and calendars:

js
const d = new Date(Date.UTC(2026, 9, 30, 9, 0)); // 30 October 2026

new Intl.DateTimeFormat("ar-AE", { dateStyle: "long", timeZone: "Asia/Dubai" }).format(d);
// "30 أكتوبر 2026"

new Intl.DateTimeFormat("ar-EG", { dateStyle: "long", timeZone: "Africa/Cairo" }).format(d);
// "٣٠ أكتوبر ٢٠٢٦"

new Intl.DateTimeFormat("ar-SA", {
  dateStyle: "long",
  calendar: "gregory",
  numberingSystem: "latn",
  timeZone: "Asia/Riyadh",
}).format(d);
// "30 أكتوبر 2026"

new Intl.DateTimeFormat("ar-SA", {
  dateStyle: "long",
  calendar: "islamic-umalqura",
  numberingSystem: "latn",
  timeZone: "Asia/Riyadh",
}).format(d);
// "19 جمادى الأولى 1448 هـ"

Four things to know:

  • Always set the calendar for Saudi Arabia. Older browser data defaulted ar-SA to the Hijri (Umm al-Qura) calendar; current data defaults to Gregorian. Without calendar, two visitors can see dates in two calendars. If a Saudi client needs both, as some official contexts do, format the date twice and show both.
  • Month names depend on the region. The Gulf and Egypt use transliterated names such as أكتوبر for October. The Levant and Iraq use names such as تشرين الأول, and ar-LB or ar-IQ produce them. Pick the locale that matches your readers.
  • Short numeric dates hide characters. ar-AE formats a short date as 30/10/2026 with an invisible right-to-left mark after the day and the month. Prefer dateStyle: "long" on Arabic pages; it is clearer anyway.
  • Times use ص and م for morning and afternoon: timeStyle: "short" in ar-AE gives "1:00 م" for 1 pm. Add hourCycle: "h23" for the 24-hour clock.

How should phone numbers and number inputs work?

Phone numbers stay left to right, everywhere, including inside Arabic sentences. Set the direction explicitly, or the plus sign can end up at the wrong end:

html
<a href="tel:+971501234567" dir="ltr">+971 50 123 4567</a>

Accept the digits people type. Users on Arabic or Persian keyboards may type Eastern Arabic or Persian digits into a phone, quantity or postcode field. Validation that only accepts 0 to 9 then rejects a correct number. Normalise before validating:

js
const toWesternDigits = (s) =>
  s
    .replace(/[٠-٩]/g, (c) => String(c.charCodeAt(0) - 0x0660))
    .replace(/[۰-۹]/g, (c) => String(c.charCodeAt(0) - 0x06F0));

toWesternDigits("٠٥٠ ١٢٣ ٤٥٦٧"); // "050 123 4567"

Give phone, email and number fields dir="ltr" so the typed value reads correctly, and use type="tel" or inputmode="numeric" so phones show a number keypad. The same direction rules apply to email addresses, URLs and product codes; RTL web design covers mixed-direction text in full.

What else trips developers up?

Plurals. Arabic has six plural categories, and Intl.PluralRules returns all of them. An i18n setup with only "singular" and "plural" strings produces wrong Arabic for most counts.

CountCategory from Intl.PluralRules("ar")"Product" in Arabic
0zeroلا توجد منتجات
1oneمنتج واحد
2twoمنتجان
3 to 10few3 منتجات
11 to 99many11 منتجًا
100, 101, 102other100 منتج

The categories repeat above 100: 103 is "few" again and 111 is "many". Use a message format library that supports all six, and have the translator fill every form.

Invisible characters in formatted output. Intl inserts direction marks: U+200F in Arabic dates and prices, U+200E around the percent sign in ar-AE, and U+061C, the Arabic letter mark, in ar-SA percentages. Tests that compare formatted output with a hand-typed string fail for no visible reason. Compare with formatToParts(), or strip the marks first. Paste any output into our Unicode character inspector to see exactly which marks are there.

Server and browser disagreeing. If a page is rendered on the server and hydrated in the browser, and the two have different locale data, the formatted strings differ and the framework reports a hydration mismatch. Passing explicit numberingSystem and calendar options removes most of the difference; formatting only on one side removes the rest.

For how these formatting choices fit into a Next.js build with dictionaries and plurals, see building a multilingual Next.js site.

Was this guide useful?

Questions

Frequently asked.

Should Arabic pages use Eastern Arabic digits?

It depends on the market. UAE business sites mostly use Western digits (0 to 9) in Arabic text. In Saudi Arabia and Egypt both styles are common. Follow the client's printed material and signage, then apply one style across the whole site, including prices, dates and anything a translator types by hand.

What is the difference between Arabic and Persian digits?

They are separate Unicode characters. Arabic uses U+0660 to U+0669 (٠ to ٩); Persian and Urdu use U+06F0 to U+06F9, and the 4, 5 and 6 are drawn differently (۴ ۵ ۶). Users with Persian keyboards may type them on an Arabic site, so normalise both ranges before validating input.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.