# Arabic-First AI: Why Dialects, Datasets, and Deployment Matter > Source: > Published: 2026-10-31 13:39:32+00:00 # Arabic-First AI: Why Dialects, Datasets, and Deployment Matter **Companion models:** [MasryGPT-Chat-1.5B](https://huggingface.co/ISLAM-PO/MasryGPT-Chat-1.5B) · [datasets](https://huggingface.co/ISLAM-PO) · [portfolio](https://aslamalkarywk7.github.io/aslamalkarywk7/) Arabic is spoken by ~400 million people across 20+ countries, yet most "Arabic" AI is really **Modern Standard Arabic (MSA)** — the language of news, academia, and religion. Nobody texts in MSA. Egyptians say "ازيك؟", not "كيف حالك؟". Moroccans say "labas", not "كيفك". The gap between the Arabic that models are trained on and the Arabic that people actually speak is one of the largest unaddressed problems in applied NLP. This essay argues that **Arabic-first AI** requires three things: **dialect-aware models**, **dialect-rich datasets**, and **deployment paths that fit local infrastructure**. I write from the perspective of a full-stack developer who has built and shipped both the models and the products around them. ## 1. The MSA Trap Most Arabic LLMs (Qwen, Jais, AceGPT, ALLaM) are trained and evaluated on MSA-heavy corpora. The result: - **Fluency mismatch.** A model that scores well on MSA benchmarks sounds stiff and translated to a dialect speaker. - **Cultural loss.** Idioms ("عيش وملح"), humor, and register are not MSA. You cannot translate "يا باشا" into a formal register without losing the warmth. - **User trust.** A chatbot that replies in MSA to an Egyptian user feels like talking to a bureaucrat, not a person. In my own MasryGPT evaluation, base Qwen scored **4.7/5 MSA fluency** but only **3.1/5 Egyptian fluency**. After one epoch of dialect fine-tuning, Egyptian fluency rose to **4.6/5** — at the cost of a small MSA regression (−10%). That tradeoff is real and worth naming honestly. ## 2. The Dataset Problem Dialect data is scarce, noisy, and legally messy: - **Volume.** MSA corpora (OSCAR, Arabic Wikipedia, news) are large. Dialect corpora are tiny and fragmented. - **Quality.** Dialect text on social media is full of typos, code-switching, and transliteration ("3ajibni" instead of "عجبني"). Cleaning it is non-trivial. - **Provenance.** Real chat logs (WhatsApp, Facebook) are the gold standard but require anonymization and documented consent. Synthetic generation (lexicon-based) is safer but risks producing "textbook dialect" — a dialect that no one actually speaks. - **Coverage.** Egypt's Cairo dialect dominates; Upper Egypt (Saidi), Levantine, Gulf, and Maghrebi dialects are even more underrepresented. **What I built to address this:** | Dataset | Purpose | | `arab-dialects-20-countries-3m` | Broad dialect coverage across 20 Arab countries | | `arabic-history-and-dialects` | Historical + dialectal Arabic | | `documents-Egyptian-Arabic` | Egyptian-Arabic document text | | `arabic-to-code-8-langs-3m` | Arabic instructions → code in 8 languages | The 3M-row dialect dataset is the backbone; the MasryGPT training set (80k) is a curated subset focused on Cairo speech. ## 3. Dialect-Aware Modeling: Lessons from MasryGPT Key takeaways from fine-tuning `Qwen2.5-1.5B-Instruct` on 80k Egyptian examples: - **Small models can learn dialect.** A 1.5B model reached 4.6/5 human fluency in one epoch. You do not need 70B to sound Egyptian. - **QLoRA is enough.** 18.5M trainable parameters (1.18%) on 4-bit base, trained in 2h13m on free T4s. The barrier to entry is low. - **Loss plateaus tell the truth.** Loss flattened at step 1,500 → the dataset was saturated. More epochs would have memorized, not generalized. This is the most important diagnostic I check. - **Idioms are the hard part.** Overall fluency was high, but idiom correctness ("عيش وملح") stayed at 40%. Idioms need dedicated, high-quality data — roughly 5k pairs — not more volume. - **Tradeoffs must be reported.** MSA fluency dropped 10%. Hiding this would be dishonest and would break downstream users who need both. ## 4. The Arabic-to-Code Frontier A second, less discussed problem: **Arabic as an instruction language for code generation.** Most code LLMs are trained on English prompts. An Arabic-speaking developer who thinks in Arabic must mentally translate before prompting — friction that slows adoption. My `arabic-to-code-8-langs-3m` dataset targets this directly: Arabic instructions mapped to code in 8 programming languages. Combined with a dialect model, this enables a fully Arabic developer experience: think in Masry, get code. ## 5. Deployment: Local Realities Arabic-first AI must run where Arabic speakers are: - **GPU scarcity.** Many Egyptian teams have no A100s. A 1.5B model in 4-bit (~1.2 GB VRAM) runs on a T4, a laptop, or even a phone via GGUF/Ollama. - **Latency & cost.** Self-hosting a small model beats paying per-token API fees for high-volume Arabic chatbots. - **Offline & privacy.** Government, banking, and healthcare use cases in the region often require on-prem deployment. Small models make this feasible. - **Integration.** As a full-stack developer, I wire models into real products: Next.js frontends, Prisma/Postgres backends, LangChain for RAG, vector search for grounding. The model is only 20% of the work; the other 80% is product engineering. ## 6. What's Missing (Honest Gaps) - **Evaluation standards.** There is no widely accepted Arabic-dialect benchmark. My "4.6/5" is a 3-speaker internal review, not an independent benchmark. The field needs shared eval sets. - **Reproducibility.** I have not yet published the 80k training JSONL. Until the dataset, generation script, and filtering rules are released, the numbers are an internal pilot. - **Dialect breadth.** Cairo dominates my data. Saidi, Levantine, Gulf, and Maghrebi need the same treatment. - **Safety & bias.** Dialect models can amplify regional stereotypes and vulgarity. Filters and red-teaming are underdeveloped for Arabic. ## 7. A Call to Action If you are building Arabic AI: 1. **Report dialect fluency separately** from MSA fluency. Do not let one number hide the other. 2. **Publish your datasets** (or at least their generation recipe). Reproducibility is the bottleneck. 3. **Start small.** A well-fine-tuned 1.5B beats a poorly-prompted 70B for dialect tasks, and it deploys anywhere. 4. **Build the product, not just the model.** RAG, validation, UX, and monitoring matter more than the checkpoint. Arabic-first AI is not a translation problem. It is a **culture problem**, and culture lives in dialects. The models that win will be the ones that sound like the people they serve. *Author: Islam Al-Nashar — Full-Stack Developer & AI builder. [GitHub](https://github.com/aslamalkarywk7) · [Hugging Face](https://huggingface.co/ISLAM-PO) · [Portfolio](https://aslamalkarywk7.github.io/aslamalkarywk7/)*