Bilingual Brand Design: Building One System for Arabic and English

In the Gulf, most brands are bilingual by default. A brand that works in English and treats Arabic as a translation layer looks exactly like what it is — and the audience notices immediately.

Designing one coherent system for both is a different job from designing one and converting it. Here is what actually changes.

The scripts behave differently

Direction. Arabic reads right to left. That is not just mirroring: it changes where the eye enters a composition, which means the hero element, the logo position and the reading order of a layout all shift. Flipping an English layout produces something that technically reads correctly and feels wrong.

Connected letterforms. Arabic letters join, and their shapes change depending on position in the word. You cannot letter-space Arabic the way you can Latin — adding tracking breaks the connections. Any “tighten the tracking” instruction that works on the English version will damage the Arabic one.

Vertical proportion. Arabic has a taller effective body relative to its cap-height equivalent, with ascenders and descenders that swing further. Set at the same point size, Arabic typically appears larger and needs more line height. Matching point sizes across the two scripts produces a mismatch; matching optical size is what you want.

No capitals. Every emphasis technique that depends on uppercase — all-caps labels, small caps, capitalised headings — has no Arabic equivalent. Emphasis has to come from weight, size or colour instead, which means the design system needs those alternatives built in from the start.

What this means for the logo

A bilingual mark is two lockups, designed together.

The Arabic wordmark should not be a font set in the nearest matching typeface. It should be drawn to carry the same weight, rhythm and personality as the Latin version — the same feeling, not the same shapes. That usually means custom lettering or significant modification of an existing face.

Practical decisions to make explicitly:

• Do the two versions ever appear together, and if so in what order and at what relative size?
• Which is primary in which market?
• Does the icon mark stay identical across both? (Usually yes, and this is what holds the identity together.)
• How do the two lockups balance optically, given the different proportions?

Getting the relative sizing right is fiddly and matters a lot. Matched point sizes almost always look wrong; the Arabic usually needs to sit slightly smaller to appear equal.

What this means for typography

You need a genuine Arabic typeface with the weights your system requires, chosen alongside the Latin one rather than after it. Not every family has a good Arabic companion, and this constraint should be part of the original shortlist.

Then define, in the guidelines:

• The Arabic type scale — usually different numbers from the Latin scale, tuned so both look the same size
• Line heights, generally more generous for Arabic
• Which weights pair across the two
• That letter-spacing rules apply to Latin only

What this means for layout

Design both, do not mirror one. Build the layout so the grid works in either direction, then lay out each language properly within it. Icons with directional meaning — arrows, progress indicators — flip. Logos, numerals, clock faces and most photographs do not.

Leave room. Arabic translations of the same content are often shorter in character count but need more vertical space. A headline box sized precisely to the English will break.

Watch mixed content. Numbers, Latin brand names and units inside Arabic text create bidirectional runs that need care. This is where most automatic conversions visibly fail.

Marketplace and packaging specifics

On Amazon.ae and Noon, the whole listing image set needs to work right-to-left. That is not a flipped export — the hero element belongs on the other side of the frame because that is where the eye lands first.

On packaging, panel order changes, and regulatory panels frequently have to appear in both languages with specified prominence. Confirm those requirements before design starts rather than retrofitting them.

The part to get right procedurally

Work from copy supplied by a native speaker. Not machine translation. A designer who does not read Arabic cannot catch a rendering error, a broken ligature, or text that has been reversed by a tool that did not understand the script — and all three are common.

Build the review step in: an Arabic-reading reviewer signs off the final artwork before it ships. That single step catches the errors that embarrass brands.

We design bilingual systems as one thing rather than two, and we work from your copy or your translator’s — we do not machine-translate, and we will not approve text we cannot verify. See brand identity design, or the Abu Dhabi and Riyadh pages for how this plays out in those markets specifically.