Arabic typography mistakes we see on business websites
The Arabic type errors that make business sites look careless: fallback fonts, letter-spacing, fake italics, cramped lines, broken images, and fixes.
By Sohail Hussain21 November 20266 min read
The Arabic typography mistakes we see most on business websites are Arabic text falling back to a system font because the brand font has no Arabic, letter-spacing and fake italics applied to a script whose letters join, text set too small with line heights copied from the English design, Arabic baked into images by software that cannot shape it, and punctuation thrown to the wrong end of the line by mixed-direction text. Each is cheap to fix. Each tells an Arabic reader the site was built for someone else.
Most of these come from one cause: the site was designed in English and Arabic was poured into the same styles later. This post lists the mistakes and the fixes. Choosing the fonts in the first place is covered in best Arabic web fonts, and the full build in the guide to building an Arabic website. Typography is reviewed on every Arabic and multilingual website we deliver before it goes live.
Why does the Arabic text look like it belongs to a different website?
The Arabic is in a fallback font. The brand's Latin typeface has no Arabic letters, nobody chose an Arabic companion, and the browser falls back to whatever Arabic font the device has. The result differs on Windows, Mac and Android, and matches the brand on none of them. Fix: choose an Arabic font deliberately and load it on Arabic pages.
A display font is used for body text. A decorative Kufi or calligraphic face looks striking in a large heading and is tiring in a paragraph. Fix: keep decorative faces to one or two large headings, and set text in a readable modern sans or Naskh.
The design asks for weights the font does not have. An English design with semibold (600) headings, paired with an Arabic font that has only 400 and 700, makes the browser substitute the nearest weight or synthesise one. Headings then look heavier or lighter in Arabic than in English. Fix: check the weights each font actually has and map the design to them.
Why do the Arabic letters look broken or stretched?
Letter-spacing. Arabic letters join. Tracking that suits English capitals, on buttons, small labels and headings, either pulls joined letters apart or breaks the connections altogether, depending on the browser. It is often inherited from a component style nobody thought to check in Arabic. Fix: set letter-spacing to zero for Arabic text.
Fake italics. Arabic has no italic convention, and most Arabic fonts have no italic style. Ask for font-style: italic and the browser slants the upright letters, which reads as a rendering error. The same happens with fake bold when a weight is missing. Fix: disable synthesis for Arabic and emphasise with weight or colour. MDN documents the font-synthesis property that controls this.
Tatweel used for decoration. The tatweel character (ـ, U+0640) stretches the joining stroke between letters. Typed into headings to make words wider, it looks dated, and it is a real character in the text: "شـــركة" is a different string from "شركة" for find-in-page and any code that compares text.
Justified text. Browsers mostly justify Arabic by widening the spaces between words. In narrow columns that leaves visible gaps, and support for justifying Arabic by extending letters instead is limited. Fix: align body text to the start of the line.
These rules cover most of it:
:lang(ar) {
letter-spacing: 0;
font-style: normal;
font-synthesis: none;
}
html:lang(ar) body {
font-family: "IBM Plex Sans Arabic", sans-serif;
font-size: 1.125rem;
line-height: 1.8;
text-align: start;
}
html:lang(ar) h1,
html:lang(ar) h2,
html:lang(ar) h3 {
line-height: 1.4;
}
One catch: :lang(ar) has the same specificity as a single class. A component rule such as .eyebrow { letter-spacing: 0.1em; } that comes later in the stylesheet still wins. Search the stylesheet for letter-spacing and italic and check each one in Arabic.
Why does Arabic look cramped or cut off?
It is too small. At the same pixel size, Arabic usually looks smaller than Latin text. A design that sets both languages at 16px leaves the Arabic looking like the small print. Fix: set Arabic 5 to 15 percent larger, judged by eye against the English.
The line height is the English one. Arabic letters have tall ascenders, such as alef and lam, deep descenders, and dots and marks above and below the letters. A heading line height of 1.1, normal in English design, makes two-line Arabic headings collide. Fix: give Arabic its own line heights, around 1.6 to 1.9 for body text and at least 1.3 for headings, depending on the font. Our line height calculator gives a starting point from font size and line length.
Fixed heights clip the text. Buttons, badges and navigation items with a fixed height and overflow: hidden cut off descenders and dots. In English nothing seems wrong; in Arabic the bottom of every word is missing. Fix: use padding instead of fixed heights.
Labels designed for short English words. "Home" fits a narrow tab. Its Arabic equivalent may not. Design components to wrap or grow, and test them with the real Arabic copy.
What goes wrong with Arabic in images and pasted text?
Arabic in images made with tools that cannot shape it. Arabic letters change shape depending on their position in a word, and software without Arabic support draws them as separate letters, often in reverse order. The result is unreadable, and the person who made the banner, not reading Arabic, cannot tell. Fix: put Arabic text on the page as real text over the image. If it must be part of the image, export it from software with proper Arabic support, and have a native speaker check the file before it is published.
Text in images has other costs too: it cannot be translated, searched or read by screen readers, and it needs a new image for every wording change.
Text pasted from PDFs and old systems. Arabic copied out of some PDFs arrives as "presentation forms", Unicode characters for each letter's individual shape, instead of the standard Arabic letters. It looks right on screen. It breaks search, copy-paste and the font's own shaping, and it may render differently in another browser. Pasted text can also carry stray direction marks and zero-width characters. Paste suspicious copy into our Unicode character inspector: standard Arabic letters sit between U+0600 and U+06FF, and Arabic characters from the presentation-form blocks, U+FB50 to U+FDFF and U+FE70 to U+FEFF, are a sign of a bad copy.
Why does punctuation end up on the wrong side?
Mixed-direction text without isolation. An Arabic sentence ending with an English brand name can show its full stop at the wrong end of the line. A phone number can show its plus sign after the digits. Fix: wrap embedded English in a bdi element and give phone numbers, emails and URLs dir="ltr". RTL web design has the details.
Latin punctuation in Arabic text. Arabic uses its own comma (،), question mark (؟) and semicolon (؛). Text typed on an English keyboard, or produced by careless translation, uses the Latin ones, which look wrong in Arabic. Fix: put the punctuation rule in the translation style guide and check for it in review.
Mixed digits. Prices in Western digits next to dates in Eastern Arabic digits, because they came from different sources. Pick one style for the whole site.
How do you catch these mistakes before launch?
Check the Arabic pages the way an Arabic reader sees them:
- Open each template on Windows, a Mac, an Android phone and an iPhone. Fallback fonts show up as differences between devices.
- In the browser's developer tools, check the rendered font for Arabic text. Both Chrome and Firefox show which font was actually used, which is not always the one in the CSS.
- Search the stylesheet for
letter-spacing,italic, fixedheightvalues andtext-align: justify. - Run a sample of every page's copy through the Unicode inspector.
- Have a native speaker read the rendered pages, not the translation document. Most typography errors are invisible in a Word file and obvious on screen.
The W3C's Arabic and Persian layout requirements document is the detailed reference for how Arabic text should be set, if your designer or developer wants the full rules.
Was this guide useful?