Arabic localization for a digital product rests on two decisions: which Arabic the product speaks and how the interface behaves when it runs right to left. Most product teams should write the interface in Modern Standard Arabic, add regional wording only where the voice needs to feel local and design a mirrored layout from the start. El Turco localizes software, websites, games and e-commerce content into Arabic with native linguists under ISO 17100, backed by an in-house project management and QA team.
This primer is for product managers and designers preparing an Arabic launch. It explains the difference between MSA and the main dialect groups, what right-to-left layout changes in a design system, how to handle numbers and mixed-direction text and which checks belong before translation starts.
Which Arabic should your product use?
Modern Standard Arabic (MSA) is the formal written standard shared across the Arabic-speaking world. People use regional dialects in daily life and those dialects differ in vocabulary, pronunciation and some grammar. The main dialect groups product teams meet are Gulf, Levantine, Egyptian and Maghrebi Arabic.
Choosing a variant is a product decision, not only a translation decision. The variant sets the voice of the product, the glossary, the style guide and the reviewers you need.
| Option | Best for | Trade-off | What the team maintains |
|---|---|---|---|
| MSA only | Interface text, help content, legal, finance and life sciences | Can feel formal in casual copy | One Arabic locale and one glossary |
| MSA with regional wording | Consumer apps, e-commerce and marketing in a priority market | Needs a clear rule on where regional wording is allowed | One base locale plus market overrides |
| Full dialect | Chatbots, social features and campaigns for one market | Speaks directly to one audience and less to others | A separate style guide and reviewers for each dialect |
When is MSA the right default?
MSA is the right default for interface text, settings, account and payment flows, help centers, legal terms and anything regulated. One MSA version can serve users from Morocco to Oman, which keeps a single locale to maintain. The trade-off is warmth: MSA in casual onboarding screens can feel stiff.
When does a dialect make sense?
A dialect makes sense when the product voice is conversational and the audience sits in one market. Consumer marketing, social features, chatbots and casual games aimed at one country often read better with Gulf or Egyptian wording. Maghrebi Arabic differs most from MSA and mixes in French loanwords, so business content for North Africa usually stays in MSA.
Do you need one Arabic locale or several?
Many products ship one Arabic locale (ar) and add market locales such as ar-SA, ar-AE or ar-EG only where prices, digits, calendar defaults or legal text differ. Keep the base translation shared and override only the strings that change per market.
What does right-to-left layout change in a design?
Right-to-left (RTL) layout is the mirrored arrangement of an interface for scripts that read from right to left, such as Arabic, Persian and Sorani Kurdish. Mirroring does not mean flipping the whole screen like an image. Designers decide element by element what follows reading direction and what stays fixed.
What should flip?
- Alignment: text, labels and form fields align to the right.
- Navigation: side menus open from the right and back arrows point to the right.
- Element order: breadcrumbs, tabs, steppers and carousels run from right to left.
- Progress: progress bars and sliders fill from right to left.
- Directional icons: back and next arrows, chevrons and list indent icons.
What should stay as it is?
- Media playback controls such as play, rewind and fast forward.
- Logos, brand marks and product screenshots.
- Clock faces and charts with a time axis, unless your team decides otherwise.
- Phone numbers, card numbers, codes and URLs, which run left to right inside RTL text.
- Icons of physical objects such as a checkmark, a camera or a calendar.
How should the design system prepare?
Build mirroring into the design system rather than into each screen. In code this means setting dir="rtl" and lang="ar" on the document and using logical CSS properties such as margin-inline-start instead of margin-left.
Typography needs attention too. Arabic has no uppercase letters, so all-caps styles used for emphasis do not carry over; use weight or color instead. Arabic needs a font with full shaping support. The script also needs more line height for tall letters and diacritics.
How should mixed-direction text, numbers and dates be handled?
Bidirectional text is text that mixes right-to-left and left-to-right runs in one line. Arabic interfaces contain it everywhere: brand names, URLs, code, model numbers and many figures run left to right inside Arabic sentences. Without direction handling, a full stop or a placeholder can land at the wrong end of the line.
- Isolate user-generated and variable content with the HTML bdi element, dir="auto" or Unicode isolate characters, so a Latin name inside an Arabic sentence keeps its place.
- Agree the digit style per locale. Maghrebi locales use Western digits (0-9) and many Gulf apps do too. Eastern Arabic digits are common in Egypt and the Levant and in much printed Gulf material.
- Dates run day, month, year in most Arabic locales. Confirm whether the Hijri calendar should appear next to the Gregorian calendar, which is common in religious and government contexts.
- Check the first day of the week per locale, since it differs across Arabic-speaking markets.
Which checks belong before translation starts?
Many Arabic launch problems trace back to the build and the source strings rather than the translation. Run this checklist on the first build with a handful of real Arabic strings.
- Rendering: Arabic letters join and appear in the right order in every font, framework and notification template.
- Plurals: strings with counts support the six CLDR plural categories Arabic uses (zero, one, two, few, many and other) through ICU message format or your platform equivalent.
- Gender: second-person strings have gendered variants or avoid direct address, since Arabic verbs and adjectives change for a male or female reader.
- No concatenation: full sentences live in one string with named placeholders, because word order and agreement change in Arabic.
- Context: each string has a note or screenshot showing where it appears.
- Space: buttons, tabs and notifications allow longer text and taller lines.
- Direction: the build sets RTL from the locale and does not rely on styles that hardcode left and right.
How should product teams decide variant and scope?
Work through these criteria with your localization partner before the glossary and style guide are written.
- Audience spread: if users are spread across many Arabic-speaking countries, start with MSA. If one market drives most usage, consider regional wording for that market.
- Content type: keep regulated, legal, financial and medical text in MSA. Consider dialect only for conversational and marketing copy.
- Product voice: a playful brand may need regional wording, while a banking or health product usually suits neutral MSA.
- Maintenance cost: every extra dialect adds a style guide, reviewers and test passes to each release.
- Build readiness: if the product cannot render RTL yet, fix direction support first.
- AI and conversational features: chatbots and speech products need data in the dialects users actually speak, not only MSA.
How should Arabic be tested before release?
Linguistic quality assurance (LQA) is the review of localized text in the running product by native speakers. For Arabic, LQA is where mirroring errors, broken shaping, truncation, wrong digits and agreement problems become visible. Plan LQA as part of the release schedule, not as a final check after strings are locked.
- Give reviewers a staging build or test accounts that reach every key flow, including checkout and error states.
- Agree issue categories in advance: mirroring, bidirectional text, rendering, truncation, terminology and register.
- Ask for a screenshot and a suggested fix with every issue, then run a regression pass on the next build.
- Include store listings, notifications and transactional messages, which users see outside the product.
How El Turco handles this
El Turco localizes software, websites, games and e-commerce content into Arabic with native linguists who agree the variant with each client before translation starts. Scoping covers target markets, register, digit style, file formats and release cadence. Translation follows TEP under ISO 17100 in RWS Trados, memoQ, Phrase, XTM or your own platform.
Before any file returns, What's Wrong?, the translation QA tool from Still Needs a Human, verifies placeholders, tags, terminology, numbers and string length. Native reviewers then check mirroring, bidirectional text, truncation, plural forms and digits in your build and log each issue with a screenshot. New strings can move through your TMS or localization platform. Unreleased content is handled under NDA and ISO/IEC 27001. Pilots are free. Pricing is per-word, hourly or project-based, quoted after scoping. Turnaround is agreed at scoping.