
Most InDesign workflows assume left-to-right text: lines start on the left, pages bind on the left and page one sits on the right of a spread. Arabic and Hebrew reverse all three. An English file needs specific changes before RTL text goes in, and when nobody makes them, the translated file comes back with broken lines, misplaced punctuation and pages in the wrong order.
This article covers the settings you need: which InDesign install to use, how to set up an RTL document, how paragraph styles handle direction, and what to check when a translated file comes back broken. It focuses on Arabic and Hebrew. Farsi and Urdu use the same settings, with the differences noted below.
Agencies and project managers sending or receiving files for Arabic or Hebrew translation. Reading Arabic is not required: every check below is a setting or a visible sign.
RTL features depend on how InDesign is installed. Since CS4, every install includes the Adobe World-Ready Paragraph Composer, which joins Arabic letters. The rest of the Middle Eastern features (right-to-left binding, story direction and kashida justification) come only with an install in a Middle Eastern language option, such as English with Arabic support or English with Hebrew support, chosen in the Creative Cloud desktop app.
The World-Ready composer joins Arabic letters, but right-to-left binding, story direction and kashida justification are missing from the interface. Not suitable for production RTL work.
Full RTL interface: right-to-left binding, story and paragraph direction, kashida justification and the Digits menu. It installs alongside the standard version, so both can stay on the same computer.
To check which install you have, open File → Document Setup. If there is no binding option, the install has no Middle Eastern features.
Before changing any settings, it helps to know what InDesign has to do differently for Arabic and Hebrew compared with Latin.
Hebrew letters don't connect, so its shaping is simpler. Arabic, Farsi and Urdu need the Adobe World-Ready Paragraph Composer, which handles letter joining, ligatures and contextual forms. Without it, Arabic appears as disconnected letters.
Binding direction is a document setting. It decides which side the spine is on, which side counts as the front, and the order of pages in the Pages panel.
New document setup: RTL
File → New → Document, choose the size and Intent (Print or Web) as usual, and click Create.File → Document Setup and click the right-to-left Binding button. The spine moves to the right, which is correct for Arabic and Hebrew books and multi-page documents.Binding can be changed later in File → Document Setup. After the switch, check every spread: page numbers, running heads and anything placed on a specific side of the spread will need adjusting.
Every paragraph in InDesign has a direction: left to right or right to left. Direction is separate from alignment and controls:
The Paragraph panel has two buttons for it: Left-to-Right Paragraph Direction and Right-to-Left Paragraph Direction. Arabic and Hebrew body text needs right to left.
| Setting | Where to find it | Correct value for Arabic/Hebrew |
|---|---|---|
| Paragraph Direction | Paragraph panel | Right-to-Left Paragraph Direction |
| Composer | Paragraph panel menu | Adobe World-Ready Paragraph Composer (Arabic, Farsi, Urdu and Hebrew) |
| Justification | Paragraph panel → Justify | Justify with Last Line Aligned Right |
| Story Direction | Story panel | Right to Left |
| Digits | Character panel → Digits | Arabic: Hindi (Eastern Arabic, ٣) or Arabic (Western, 3), as the client requires. Farsi: Farsi. Hebrew: Default. |
When Paragraph Direction and Composer are set in a style, every paragraph using that style gets them. In translated files, where the CAT tool reapplies the source styles, this is the reliable way to keep RTL settings consistent.
Create a structured project brief in your browser before contacting a DTP provider. Add your file format, page count, languages, deliverables, and common production risks. It runs in your browser: nothing is uploaded or stored, and no sign-up is needed.
Prepare Project BriefYou can use the generated brief with DTP Services Berlin or any other agency.
The composer is InDesign's line-breaking and shaping engine. Latin text works with the Adobe Paragraph Composer or the Single-line Composer. Arabic, Farsi, Urdu and Hebrew need the Adobe World-Ready Paragraph Composer (or its single-line version).
Without it, in Arabic text:
Hebrew letters don't join, so the visible damage is smaller. The World-Ready composer is still needed for correct cursor behaviour and punctuation placement in mixed Hebrew and Latin text.
Look at a line of Arabic text. If the letters stand apart instead of joining into words, the wrong composer is active. Switching to the Adobe World-Ready Paragraph Composer recomposes the text immediately.
Not every font that lists Arabic support works for production. For print work, a font needs:
Reliable choices for Arabic: Adobe Arabic (ships with Creative Cloud), Noto Naskh Arabic (free, Google), Lateef, Scheherazade New (SIL, free), Sakkal Majalla. For body text at small sizes, Adobe Arabic and Noto Naskh Arabic are the safest bets.
For Hebrew: Adobe Hebrew (ships with Creative Cloud), Noto Sans Hebrew, David CLM, Frank Ruehl CLM. Adobe Hebrew is a common choice for layouts that pair Hebrew with Latin text.
This happens often when a client sends a brand font that covers only Latin. Applied to Arabic text, such a font shows boxes or question marks; it cannot partly work. If the brand has no Arabic version, agree on a substitute with the client before work begins.
A typical Arabic layout contains brand names in Latin, product codes, URLs, phone numbers, prices and sometimes English phrases, all inside RTL paragraphs.
InDesign applies the Unicode bidirectional (Bidi) algorithm to this automatically. The paragraph direction sets the base direction, and Latin sequences inside the paragraph run left to right within their own run. You usually don't need to force this by hand.
Where it breaks:
If a short sequence displays in the wrong direction, select it and set Character Direction: Left to Right in the Character panel. It is a manual fix on individual characters, so use it sparingly.
When a translated file comes back with the wrong RTL configuration, you will see one or more of these:
| Symptom | Likely cause | Fix |
|---|---|---|
| Arabic letters appear disconnected | Wrong composer (not World-Ready) | Select all text, switch to the Adobe World-Ready Paragraph Composer |
| Text runs left to right inside the frame | Paragraph direction set to left to right | Select all paragraphs, click Right-to-Left Paragraph Direction |
| Red plus sign at the frame's out port | Overset text: the translation needs more space than the frame allows | Enlarge the frame or reduce the type size; see the overset text article |
| Text highlighted pink | Font missing on this computer and substituted | Install the font, or replace it with an Arabic-capable font |
| Punctuation at the wrong end of the line | Paragraph direction left to right with RTL text | Correct the paragraph direction; recheck the composer |
| Numbers appear right to left as strings | Eastern Arabic digits without direction context | Check the Digits setting in the Character panel; confirm paragraph direction is right to left |
| Spine on the wrong side | Binding still left to right | Change Binding in File → Document Setup, then check every spread |
If you send an existing LTR file for Arabic or Hebrew translation, the DTP side has to rework the layout. Preparing the source file reduces that rework and its cost.
Character counts say little about space on the page. Arabic needs more vertical space than Latin text, and short strings such as labels and buttons change length far more than running text: IBM figures cited by the W3C put strings under 10 characters at two to three times the English length. Test fixed frames with real translated text before the design is signed off.
RTL layout in InDesign comes down to a few settings. The common mistakes are a standard English install without Middle Eastern features, paragraph direction left at left to right, the wrong composer for Arabic, and Latin-only fonts. Each is quick to fix once you know where to look.
Set binding and story direction at the start. Binding can be changed later in Document Setup, but every spread then needs checking, so setting it up front costs less.
If you send files to a translation vendor for Arabic or Hebrew, send an IDML, provide the font, specify the digit format and state the binding direction in the brief. A short brief covering these four points prevents most of the rework.
RTL typesetting is a narrow specialism. lpn.network is one of the few places to search specifically for freelance Arabic, Hebrew and Farsi InDesign specialists.
DTP Services Berlin lays out Arabic, Hebrew, Farsi and mixed-direction documents for agencies in the DACH region and beyond.
Get in touch