Arabic social media content, in your dialect

Write a post in Modern Standard Arabic and send it to an audience in Riyadh. Everyone will understand it. Nobody will feel it was written for them.

That is the problem translation does not solve. Fusha is correct, respected and understood from Morocco to Oman — and neutral enough that it reads like an official notice rather than a brand talking. Literal translation from English makes it worse: the sentence structure stays English, and the reader feels it even when they cannot name why.

What does "in your dialect" actually mean?

Dialect content is written from the start in one market's vocabulary and sentence shape — not fusha with a few words swapped. The difference shows up in the first line. "وش رايك" in Saudi Arabia, "شو رايك" in the UAE, "إيه رأيك" in Egypt. All three mean the same thing, and only one reads as local in each market.

Why fusha alone isn't enough

Fusha is not a mistake. It is the right choice in specific places, listed below. But in everyday content it costs you two things:

• Closeness. A post that reads formally reads as an ad, and ads get thumbed past.
• Search accuracy. People search the words they say, not the words newspapers print — "كابشن" far more than "تعليق", "السوشيال ميديا" far more than "وسائل التواصل الاجتماعي".

Where each one belongs

The working rule: dialect for closeness, fusha for authority.

• Dialect: everyday posts, stories, replies, launches — anything meant to sound like it came from a person.
• Fusha: official statements, terms, reports, corporate content, and anything one message has to carry across several markets at once.
• English: the terms a market genuinely doesn't translate — platform and product names. Writing them in Arabic letters is the fastest way to make copy read as translated.

How to choose a market dialect

Most brands don't need twenty dialects. Most need one or two, chosen in this order:

1. Find where your paying customers actually are — not where you'd like to be. Check revenue before you look at a map.
2. Pick one primary market and write for it fully. One market in a real dialect beats five in flat fusha.
3. Make fusha the default for everything else, not another market's dialect. The wrong dialect is worse than neutral.
4. Have someone from that market read it before you publish. Grammatically correct and locally odd are different things.
5. Watch replies, not likes. The right dialect produces comments in the same dialect — the clearest signal available to you.

The markets that genuinely differ

Arabic dialects aren't one gradient. They're families, and the distance between families is larger than the distance inside one:

• Gulf: Saudi Arabia, UAE, Qatar, Kuwait, Bahrain, Oman, Yemen. Close in rhythm, far apart in vocabulary — "وايد" is Emirati, "شنو" is Kuwaiti and Qatari, "ترى" is Saudi.
• Iraq: "شنو", "هسه", "أكو", "ماكو" — near the Gulf to the ear, independent in use.
• Levant: Jordan, Palestine, Lebanon, Syria. "بدّي", "كتير", "منيح" work across all four; the tone differs.
• Egypt: the most widely understood, thanks to decades of media — "إزاي", "علشان", "دلوقتي", "أوي".
• Sudan: "شنو", "دحين", "زول", "سمح" — its own family, not a branch of Egyptian.
• Maghreb: Morocco, Tunisia, Algeria, Libya. Furthest from fusha and most internally varied — "بزّاف" and "دابا" are Moroccan, "برشا" and "توّا" Tunisian.

Three tells that copy was translated

• English punctuation. The Arabic comma "،" and question mark "؟" aren't cosmetic; a Latin comma in Arabic text reads as a typo.
• Mixed numeral systems. Latin digits inside text that otherwise uses Arabic-Indic numerals. Pick one and hold it across the post.
• An English sentence wearing Arabic words. "We are excited to share that we have launched" translated literally is not Arabic. Arabic says: "أطلقناه اليوم".

What dialect does not do

Dialect makes copy sound local. It does not make copy good — a weak post in Saudi dialect is still a weak post. And if your audience spans several markets and you have nobody to review each dialect, easy modern fusha is a correct decision rather than a compromise. The reverse — a dialect written without local review — reads worse than neutral.

Technical details people forget

Right-to-left is not only text direction. Arrows, icons and progress bars need to mirror with it, while numbers still run left-to-right inside the sentence. And platform limits apply to Arabic exactly as they do to English: Instagram truncates feed captions at roughly 125 characters and has capped hashtags at five since late 2025, with its own guidance pointing at three to five relevant tags (reference). Arabic eats those limits faster, because the average Arabic word is longer than its English equivalent.

How to tell the dialect is working

Don't measure this in likes. A like is mostly a reaction to the image, not the copy. The signals that tell you the language landed:

• The language of the replies. If comments come back in the same dialect you wrote in, the audience read you as one of them. If they come back in fusha or English while you wrote in dialect, the copy didn't convince.
• Direct messages. A DM costs far more effort than a comment. A rise in DMs after a dialect change is a stronger signal than any other number here.
• Saves and shares. A share means "this is about us", and it's more honest than a like because the sharer exposes themselves to their friends' judgement.
• Reaching the end of the post. On longer posts, a rise in the share of readers who finish means the language wasn't getting in the way.

Give the change at least two weeks, and hold everything else steady while you do — timing, post type, image. Change the dialect and the posting time together and you're measuring two things with no way to tell which moved.

One brand, several markets

This is the most common situation and the most commonly botched. The real question isn't "which dialect" — it's "how many accounts":

1. One market carries most of your revenue: write in its dialect and keep fusha for corporate content only.
2. Two close markets — Saudi Arabia and the UAE, say: one account in neutral Gulf, adjusting only the sharp market-specific words.
3. Two distant markets — Gulf and Egypt, or Gulf and Maghreb: separate accounts, or separate campaigns on the same account. Trying to satisfy both in one piece of copy produces copy that belongs to neither.
4. More than three markets with no local team: easy modern fusha, unapologetically. Well-executed neutral beats five clumsy dialects.

When you have nobody to review it

Dialect without local review is a real risk: one word in the wrong place gives the copy away faster than any grammatical error. If you don't have a reviewer:

• Book one freelance reviewer for a single session a month. Reviewing twenty posts in one sitting is cheaper and faster than reviewing each post as it goes out.
• Start with the dialect closest to your own. Your ear catches mistakes in a dialect you know, and misses them in one you learned from television.
• Avoid proverbs and sharp idioms early on. Everyday vocabulary is safe; proverbs are what expose an outsider.
• Borrow your audience's language. The comments on your posts write the correct dialect for you every day, for free. Read them as a source, not only as a metric.

Three mistakes in picking a market

• Using Egyptian for a Gulf audience because it's "understood everywhere". Understood, yes — and attributed to another market. Being understood is not the same as belonging.
• Mixing two dialects in one post. It reads more machine-made than fusha would have from the start.
• Writing in the team's dialect instead of the customer's. Plenty of teams write the way they talk in their own office, then wonder why engagement is soft in another market.

Where to start

1. Pick your one primary market, based on revenue.
2. Rewrite your last five posts in that market's dialect — rewrite, don't translate.
3. Publish and watch the language of the comments for two weeks.
4. If replies come back in the same dialect, lock it in as your default and build from there.

Intilq writes content in the market dialect you choose — per brand, or per individual campaign — then schedules it, publishes it, and collects the replies in one inbox. See features and pricing, or compare it with Hootsuite and Buffer.

If you want the practical side first: how to plan a month of social posts in 30 minutes and your brand voice on autopilot.

Guides for each market

This guide covers the decision; these cover the vocabulary, one market at a time, each with a worked before-and-after:

• Writing social content for Saudi Arabia — the markers, and the weekend problem.
• Writing social content for the UAE — Emirati markers, and who is actually reading.
• Qatar, Kuwait, Bahrain and Oman: four dialects — four markets, and when neutral Gulf is right.
• Writing social content for the Levant — one dialect, two halves, one exception.
• Writing social content for Iraq and Yemen — two markets that get Gulf copy by default.
• Writing social content for Egypt — the most understood dialect, and its trap.
• Writing social content for the Maghreb — why there is no one Maghrebi dialect.
• Fusha or dialect? Choosing your register — when fusha is the better answer.
• Replying to Arabic DMs without sounding like a bot — the four replies you write every day.

For the wider picture — the working week, the platform mix and Ramadan — see Running social media in MENA: a practical guide.