A European fintech company launched their mobile payment app in Saudi Arabia in 2023. The product was solid. The marketing budget was seven figures. The Arabic translation was done by a general-purpose agency that had never worked in the Gulf. Within two weeks of launch, the app had been pulled from both Apple and Google stores in Saudi Arabia, the UAE, and Egypt. The problem? The onboarding flow used left-to-right layout with Arabic text overlaid on top of it. Numbers appeared in Western format (1,234.56) instead of Eastern Arabic numerals (١٬٢٣٤.٥٦). The greeting used Modern Standard Arabic in a register so formal it read like a legal document. And the CTA button said something that, while technically correct, carried a connotation in Gulf Arabic that was closer to "submit yourself" than "get started." The brand damage took eight months and a full re-launch to repair.
I was brought in after the pull-down to figure out what went wrong. The answer was: everything, starting with the assumption that Arabic is one language.
Arabic is not one language. This matters more than you think.
Modern Standard Arabic (MSA), also called fusʿha, is what you learn in textbooks. It's what news anchors speak. It's what official government documents are written in. Nobody speaks it at home. Nobody speaks it in a business meeting unless the meeting is very formal and both sides are from different Arabic-speaking countries and need a lingua franca. The everyday Arabic of Riyadh is different from the everyday Arabic of Cairo, which is different from the everyday Arabic of Casablanca, which is different from the everyday Arabic of Dubai. These aren't accents. They're distinct varieties with different vocabulary, different grammar, different idioms, and different cultural expectations.
For translation purposes, the practical split that matters most is this: MSA for formal documents (contracts, regulatory filings, official communications), and dialect-specific or regionally adapted content for anything customer-facing. A marketing email for a Saudi audience written in pure MSA will feel stiff and institutional. The same email adapted with Gulf Arabic vocabulary and phrasing will feel natural and personable. But here's the catch — Gulf Arabic itself isn't uniform. Kuwaiti Arabic uses words that a Saudi wouldn't recognize. Emirati Arabic has Persian loanwords that don't exist in Omani Arabic. The professional Arabic translator doesn't just translate from English to Arabic. They translate from English to the Arabic of the specific market you're entering, and they know the difference.
Cultural landmines: what "respectable" means and why it keeps changing
The MENA region spans 20+ countries with significant cultural variation, but there are some broad categories of content that require careful handling across most markets. I'm not going to give you a comprehensive list — that's what cultural consultants are for — but here are the mistakes I see most often.
Imagery is the big one. A European SaaS company used an illustration of a woman in a sleeveless top on their Arabic landing page. This is unremarkable in Beirut. In Riyadh, it was flagged as inappropriate by multiple users within hours of launch. The company didn't have a content moderation process for their Arabic market, so the complaints accumulated in social media for three days before anyone noticed. By then, the screenshots were circulating in a WhatsApp group with 12,000 members. The fix was simple — swap the image. The damage took longer to contain.
Color associations are subtler. Green is positive across the region (associated with Islam). Red can signal danger or urgency (similar to Western usage) but in some Gulf contexts carries additional connotations related to specific political or social movements. Purple is generally safe but uncommon in traditional design. Black and white are neutral. Gold is prestige. These are broad strokes — the specifics vary by country, by demographic, and by context. The point is not to memorize a color code but to have someone on your localization team who can flag potential issues before they become problems.
Tone and register are where things get genuinely tricky. Arabic has a formality spectrum that doesn't map neatly to English. The English word "you" maps to at least six different Arabic forms depending on the relationship between speaker and listener, their gender, their number, and the social context. A marketing email that uses the wrong "you" doesn't just sound weird — it can be read as disrespectful, condescending, or inappropriately intimate. I saw a B2B SaaS company address potential clients with the informal second-person in their Arabic email campaign. The recipients were C-suite executives in Dubai. The informal register was perceived as presumptuous. Open rates on the Arabic version were 4.7% versus 22% on the English original.
RTL: the technical challenge that most developers underestimate
Right-to-left text rendering is not "just flipping the layout." If that were true, every website with an Arabic version would work. They don't. I've audited roughly 40 Arabic-localized websites and applications over the past three years, and the RTL issues fall into predictable categories.
Mixed-direction content is the hardest problem. Your page is RTL, but you have a phone number in Western digits, an email address (always LTR), a product code with Latin characters, and a paragraph that quotes an English source. The browser's bidi algorithm handles simple cases well. It handles mixed cases inconsistently. Numbers might appear on the wrong side of a colon. Parentheses might flip orientation. Quotation marks might render as mirror images. A phone number formatted as "+971 4 123 4567" in an RTL context can display as "4567 123 4 971+" if the surrounding CSS isn't set up correctly. That's not a typo. That's what the browser does when it doesn't have explicit directionality markers.
UI components break in ways that are hard to predict. Icons that imply direction (arrows, breadcrumbs, navigation chevrons) need to be mirrored. Icons that don't imply direction (status indicators, logos, product photos) should not be mirrored. A hamburger menu icon should stay on the right side of the screen (or move to the left, depending on your convention) but the three lines themselves should not be flipped. Progress bars should fill from right to left. Scrollbars should appear on the left. Data tables need column order reversed. Charts with axes need axis labels repositioned. Date pickers need to default to a Hijri calendar option in some markets.
CSS `direction: rtl` gets you 70% of the way there. The remaining 30% is where your Arabic users will notice every single inconsistency. And they will notice, because they've been using poorly localized Arabic websites for years and they're tired of it. The companies that get RTL right — and there aren't many — earn disproportionate brand loyalty in the MENA market precisely because the baseline expectation is so low.
MENA market cultural guidelines (practical checklist)
This is not exhaustive. It's a starting point for teams that are new to the region and need a framework for thinking about cultural adaptation.
Language register: Use MSA for official/regulatory content. Use regionally adapted Arabic for marketing, UX copy, and customer support. Never use a single Arabic translation across all MENA markets without regional review.
Imagery review: Have a local reviewer check all visual assets before deployment. Pay attention to dress codes, gender representation, religious symbols, and hand gestures. What's fine in Amman may not be fine in Mecca.
Number formats: Eastern Arabic numerals (٠–٩) for content; Western Arabic numerals (0–9) are acceptable in technical and financial contexts in Gulf markets. Be consistent within a single page. Mixing formats looks sloppy.
Date formats: Hijri (Islamic) calendar for Saudi Arabia government and religious contexts. Gregorian is standard for business in UAE and most Gulf states. Offer both when possible. Format as DD/MM/YYYY, not MM/DD/YYYY.
CTA and action language: Have a native speaker review all buttons, prompts, and calls to action. Multiple English CTAs map to the same Arabic word but carry different connotations depending on dialect and context. "Get started" is not "submit yourself."
RTL testing: Test every page in RTL with actual Arabic content, not placeholder text. Check mixed-direction paragraphs, phone numbers, email addresses, data tables, form fields, and navigation flows. Budget 20–30% additional QA time for Arabic releases.
The MENA opportunity is real. The localization isn't optional.
The MENA region's internet penetration crossed 70% in 2024. Saudi Arabia's Vision 2030 is actively courting international tech companies. The UAE's free zones offer zero-tax environments for foreign businesses. Egypt has the largest Arabic-speaking population and a fast-growing startup ecosystem. The opportunity is not theoretical. Companies are entering these markets right now. The ones that get the localization right will have a significant competitive advantage, because most of their competitors won't. The fintech company I mentioned at the start? They re-launched with proper Arabic localization eight months later. Their user acquisition cost in Saudi Arabia dropped by 34% compared to the first launch, because word-of-mouth in Arabic social media was positive this time instead of corrosive.
Artlangs Translation provides Arabic translation across all major dialects and MSA, with dedicated MENA localization teams that handle the cultural, linguistic, and technical challenges of RTL markets. From regulatory filings to mobile app localization, we've done the work that separates a successful MENA launch from a viral brand failure. 230+ languages. One team that actually knows the difference between Gulf, Levantine, Egyptian, and Maghrebi Arabic.
