Skip to content

Design

Arabic UI Design: 12 RTL Guidelines for Apps and Websites

Mirroring a layout is only the start. Twelve guidelines for Arabic interfaces, from typography and numbers to forms, icons and mixed-language text.

By the CodeElectron engineering teamUpdated 7 min read
Illustration of an interface mirrored for right-to-left reading with Arabic text blocks and aligned icons

Key takeaways

  • Right-to-left design means mirroring layout and flow, but also choosing suitable Arabic typography and handling numbers and mixed text.
  • Mirror navigation, progress and directional icons, but not every icon, such as logos, media controls and clocks.
  • Give Arabic text room: larger line height, careful font choice and no letter-spacing tricks that break joined letters.
  • Test with real Arabic content on real devices; placeholder text hides most problems.

Why RTL needs real design work

Arabic reads from right to left, so the whole interface should feel natural in that direction. A common mistake is to flip the screen automatically and ship it. That often breaks icons, mixes numbers in the wrong order, makes fonts look cramped and leaves forms awkward. Done properly, an Arabic interface feels native, not translated. This matters for conversion as much as for polish: users trust products that look like they were made for them.

Twelve guidelines

  1. 1Mirror the layout. Navigation, sidebars, progress bars, breadcrumbs and carousels flow from right to left.
  2. 2Align text to the start edge, not always to the left or right, so the same component works in both languages.
  3. 3Choose an Arabic-capable font designed for the script and test its weights. Do not rely on a fallback font.
  4. 4Increase line height for Arabic; the script has taller and deeper shapes than Latin and needs more vertical room.
  5. 5Never add letter-spacing to Arabic text. It breaks the joins between letters.
  6. 6Flip directional icons, such as arrows and back buttons, but keep non-directional ones, such as search, logos, checkmarks and media play buttons.
  7. 7Decide on numerals and be consistent. Western digits and Arabic-Indic digits are both used, so match your audience and keep one style per screen.
  8. 8Handle phone numbers, emails, URLs and codes as left-to-right islands inside right-to-left text.
  9. 9Build forms that work: labels aligned to the start, cursor and input direction correct, and validation messages placed beside the field.
  10. 10Design tables and charts for RTL: first column on the right, axes and legends reading naturally.
  11. 11Plan for text length. Arabic and English strings differ in length, so buttons and labels must flex rather than clip.
  12. 12Test with real content and on real devices, including a phone, in both languages.

What to mirror and what not to

Mirror itKeep as is
Navigation order and menusLogos and brand marks
Back and forward arrowsMedia controls such as play and pause
Progress bars and steppersClocks and most real-world objects
Sliders and carouselsCheckmarks, search and settings icons
Text alignment and indentationCode snippets and technical identifiers

Mixed-language content

Real products mix Arabic with English brand names, product codes and numbers. The text engine decides how each run is ordered, and the results can surprise you, for example punctuation jumping to the wrong side or a product code reversing. Use proper direction attributes in markup, wrap left-to-right fragments in isolating elements and test sentences that combine both scripts. Our guide on bilingual websites and RTL SEO covers the technical side.

A worked example

A team ships an Arabic version of its checkout by flipping the stylesheet. In testing, the back arrow points the wrong way, a phone number displays with its digits reversed, labels sit on the wrong side of fields and the Arabic font looks cramped in buttons. The fixes are small: icon flipping rules, a left-to-right wrapper for numbers, start-aligned labels, a better font and more line height. After that, a tester finishes the flow without noticing it was ever a translation. This is an illustrative scenario, not a client story, but these are the usual faults.

Common mistakes

  • Testing with placeholder Latin text instead of real Arabic content.
  • Using one font weight everywhere so Arabic headings look thin or heavy.
  • Fixing the layout but leaving emails and PDFs left-to-right only.
  • Mixing numeral styles on the same screen.
  • Forgetting that screenshots, charts and exported files also need RTL treatment.

Next step

See how design decisions are tested in our UX design process, check form details in checkout conversion fixes, explore our UI/UX design service, or contact us about a bilingual product.

Frequently asked questions

Is RTL design just mirroring the layout?

No. Mirroring is the start. You also need suitable Arabic typography, careful handling of numbers and mixed text, correct form behaviour and testing with real content on real devices.

Should I use Arabic or Western numerals?

Both are common. Choose the one your audience expects, keep one style on each screen and make sure phone numbers and codes display in the correct order.

Do I need a different font for Arabic?

Yes. Use a font designed for Arabic and test its weights and line height. Fallback fonts often look cramped or inconsistent next to your Latin typeface.

Have a question we have not covered?

Ask the team directly. We are happy to talk through your situation.