Skip to content

RTL icons: which icons should be mirrored?

Learn which icons to mirror in Arabic interfaces, how to implement direction-aware SVGs, and how to verify their meaning and behavior.

By , Founder of Ritla

Guide13 min read

A next-instruction button can move to the correct side of an Arabic interface while its chevron still points the wrong way. Layout direction moved the button's contents; it did not redraw the SVG. Flipping every icon fixes that chevron while creating problems elsewhere: reversed playback symbols, altered equipment diagrams, and reflected lettering.

Mirror an icon when its meaning follows the interface's reading sequence. Preserve it when its direction represents a physical action, a geographic bearing, or an established symbol that does not change with language. Some compound icons need a separately drawn RTL version because only part of the artwork should change.

Material Design's bidirectionality guidance distinguishes back and forward navigation from nondirectional objects, clocks, and media playback. That is the starting rule. The component's actual action decides how to apply it.

Classify the action, not the silhouette#

Use an aquarium maintenance manual as a working example. Its controls let a technician advance through instructions, attach a photograph, play a training clip, and inspect a water-flow diagram. These examples describe a fictional interface, not equipment operating instructions.

The next-instruction chevron represents progress through the manual. Under its RTL navigation convention, next points left and previous points right. The arrow in the water-flow diagram represents a physical connection. Its direction must continue to match that connection, regardless of the interface language.

The same right-pointing shape could therefore require opposite treatment in two places. A rule that selects every arrow-shaped asset cannot distinguish them. An icon named arrow-right identifies geometry; it does not tell the application whether the action is next, east, play, or move the selected object right.

Icon's meaningRTL treatmentWhat to verify
Next or previous instructionMirror for the manual's RTL sequenceArrow, label, and destination agree.
Return to a parent screenUse the RTL back-navigation counterpartThe control still returns to the parent.
Expand a disclosureFollow the component's orientation and stateCollapsed and expanded glyphs match the panel behavior.
Attach a photographKeep the camera's orientationIts position may change without reflecting its shape.
Move an object physically rightPreserve the right-pointing arrowActivation still moves the object right.
Water-flow annotationPreserve the diagram's actual directionArrowheads remain attached to the correct connection.
Download or uploadPreserve the vertical directionThe metaphor still describes the action.
Play, rewind, or fast-forwardPreserve the player conventionTrack controls remain consistent with playback behavior.

This is a component policy, not a list of filenames that every product must copy. A chevron on an expandable sidebar may indicate the edge the panel will occupy rather than a reading sequence. Document that meaning before deciding which way it points. A down chevron for an ordinary collapsed dropdown does not need horizontal reflection.

Keep playback, rotation, and real-world direction intact#

A circular arrow needs more context than “it has an arrowhead.” Reload, history, undo, and rotate are distinct actions. An undo icon can have a directional counterpart in an icon system; a clockwise rotation control must continue to mean clockwise. Do not classify all curved arrows together.

Material's guidance preserves clock and circular refresh orientation. For playback, Microsoft's mirroring guidance likewise keeps fast-forward and rewind symbols in the same orientation in LTR and RTL layouts. Apply the chosen player's convention consistently rather than deriving it from the surrounding page's direction.

In the maintenance manual, changing the language must not change what a rotation tool does to an attached photograph. If the control promises clockwise rotation, its icon, localized label, and operation must all retain that promise. A reflected glyph would communicate the opposite physical operation.

Preserve logos and artwork whose identity includes their orientation. Moving a logo to another side of a header does not authorize reflecting the logo itself. Treat equipment illustrations similarly: mirroring a diagram can relocate connectors or make labels unreadable.

Even when a drawing is decorative, distinguish a design choice from an RTL requirement. A fish illustration can face toward a card's text if the art direction calls for it. That does not mean every fish asset should have an automatic RTL transform. Keep such choices separate from navigation-icon behavior so a later use in an identification diagram does not inherit them accidentally.

Separate icon position from icon orientation#

There are two questions inside a labeled control: where the icon sits relative to the text, and which way its artwork points. Fix them independently.

For an icon before a label in source order, a normal flex row puts it at the inline start: left in LTR and right in RTL. That movement is suitable for a leading camera icon, but the camera's drawing should remain unchanged. A next chevron placed after the label moves to inline end and also needs its directional artwork changed.

An icon's new position is not evidence that its orientation is correct. Conversely, a correctly reflected chevron can still be stranded on the wrong side by a physical margin or positioning rule. Inspect both the control's layout and the asset's transform.

Use gap when the spacing belongs between flex items. Use logical margins when spacing has a specific inline relationship. Avoid reflecting the entire control to move its icon: that also reflects the label and every other painted detail.

The browser does not infer the semantics of an SVG path. In the brief's measured Chromium 151 behavior, SVG drawings do not mirror merely because the page is RTL. HTML direction does affect layout. W3C's structural direction guidance explains the role of dir; RTL flexbox covers the surrounding row behavior.

Mirror only the next-instruction glyph#

This button belongs to an Arabic section of the maintenance manual. Its SVG is a right-pointing chevron in the source artwork, and the visible label means next instruction.

html
<section lang="ar" dir="rtl" aria-label="دليل صيانة الحوض">  <button class="manual-next" type="button">    <span>التعليمة التالية</span>    <svg class="manual-next__icon" viewBox="0 0 24 24"      width="24" height="24" aria-hidden="true" focusable="false">      <path d="M8 5L15 12L8 19" fill="none"        stroke="currentColor" stroke-width="2"        stroke-linecap="round" stroke-linejoin="round" />    </svg>  </button></section>

The button's existing application handler advances the manual. The markup here demonstrates its label and icon, not the manual's state management.

Problem: styling the row without changing the glyph:

css
.manual-next {  display: inline-flex;  align-items: center;  gap: 0.625rem;} .manual-next__icon {  flex: none;}

The label and chevron occupy the expected RTL row order, but the chevron still points right. It conflicts with the manual's leftward next-instruction convention.

Better: keep those rules and add an orientation rule scoped to this control:

css
.manual-next__icon {  transform-origin: center;} .manual-next:dir(rtl) > .manual-next__icon {  transform: scaleX(-1);}

The English layout and its right-pointing source glyph stay as they were. The Arabic button reflects only the SVG. MDN documents scaleX(), including horizontal reflection with a negative scale factor.

The selector tests the HTML button's semantic direction. That makes the control, rather than the SVG's document type or an unrelated ancestor, the direction boundary. For an icon-only version, keep this same ownership rule and give the button an accessible name.

To verify it, render this control under dir="ltr" and dir="rtl", with the corresponding translated labels. Check the chevron's point and activate the control in both versions. A changed silhouette does not establish that the handler reaches the next instruction.

Respect nested direction and avoid double mirroring#

A broad rule such as [dir="rtl"] svg reaches every SVG anywhere under that ancestor, including inside a nested LTR section. It can also reflect nondirectional icons, charts, and logos. Adding more exceptions makes the selector harder to reason about.

The scoped selector above uses :dir(rtl) on the owning button. MDN's :dir() reference explains that it follows semantic direction, including inherited direction, rather than CSS direction alone. If the button belongs to a nested dir="ltr" component, the RTL rule does not apply to it.

Keep the distinction when debugging. An Arabic lang value identifies language; it does not establish RTL direction. A CSS-only direction override can affect layout without making this selector match. Fix the direction contract at the component boundary instead of adding another transform to compensate. See dir versus CSS direction.

Also check whether the icon package has already selected or reflected an RTL variant. A left-pointing RTL asset plus scaleX(-1) points right again. The cascade can look correct while two separate layers cancel each other out.

Choose one owner: the icon component selects the finished directional asset, or the component renders canonical artwork and applies a reflection. A library that handles direction internally may be that owner. Verify its behavior in the installed version before adding application CSS.

For a portal-rendered toolbar, inspect direction at the toolbar's actual DOM location. The button's framework parent does not establish inherited HTML direction if the rendered node is mounted elsewhere. Pass direction to that boundary when needed.

Keep the interface direction separate from the language of a content label. A maintenance instruction may include an English model name or an untranslated document title. That text does not make the manual's next action an LTR action. Put direction handling for the foreign text around that text, rather than applying dir="auto" to the whole navigation control and letting its first strong letter decide the arrow's orientation. Bidi isolation covers that text boundary.

Swap assets when reflection would change the wrong details#

A document icon may combine lines representing text, a corner fold, and a status badge. The text layout may need an RTL counterpart while the badge or another detail keeps its original orientation. A whole-image reflection cannot express that distinction.

Apple's Arabic design guidance shows selective changes to symbols, including maintaining a prohibition slash's orientation while adapting other parts. This is a reason to use authored counterparts rather than a universal transform. Check the conventions of the icon family you ship; different families can make different artwork decisions.

Likewise, a symbol for logical paragraph start should follow paragraph direction, while an explicit “align left” command still means the physical left edge. Do not remap that command to “align right” merely because the toolbar is Arabic. The operation and its translated name decide which symbol is appropriate.

Microsoft's Fluent UI System Icons distinguish assets that can be mirrored from those with unique directional versions in their metadata. That is useful input to an icon adapter, but it does not establish whether your particular use of an arrow means navigation or physical movement.

This small application mapping separates action names from geometry names:

js
const maintenanceIcons = {  'next-instruction': { ltr: 'chevron-right', rtl: 'chevron-left' },  'previous-instruction': { ltr: 'chevron-left', rtl: 'chevron-right' },  'attach-photo': { ltr: 'camera', rtl: 'camera' },  'rotate-clockwise': { ltr: 'rotate-cw', rtl: 'rotate-cw' }}; function maintenanceIconName(action, direction) {  const icon = maintenanceIcons[action];  if (!icon || (direction !== 'ltr' && direction !== 'rtl')) {    throw new Error('Unknown maintenance action or direction');  }  return icon[direction];}

The returned names identify assets supplied by the application's icon registry. The resolver does not render them or add a transform. Configure that registry to treat these selections as finished geometry, otherwise its own automatic mirroring can undo the choice.

When replacing an icon package, review these mappings against the replacement assets. Names such as back, reply, and undo do not guarantee identical directional behavior across packages.

Text metaphors need more than a flipped outline#

Distinguish text drawn as lines from actual characters embedded in the artwork. Ragged lines representing a paragraph can be redrawn to suggest Arabic text alignment. A literal letter, abbreviation, or word must remain readable. Reflecting the whole asset reverses its lettering without translating it.

For the manual's annotation tools, decide whether a paragraph symbol means “align to start,” “align left,” or “change writing direction.” Those commands can look related in an English toolbar while behaving differently for an Arabic paragraph. Compare the operation on the selected paragraph, not only the toolbar's language. A bilingual editor may need to show controls for both writing directions simultaneously.

If a custom symbol relies on an English initial to communicate its action, choose an approved localized asset or a text-free alternative. Do not invent an Arabic initial as a mechanical substitution: it may communicate nothing to the intended reader. Keep the visible control name available while that artwork decision is reviewed.

Likewise, do not turn a help symbol into a mirrored punctuation mark by accident. Select the icon family's approved localized design where one exists. Treating recognizable lettering or punctuation as arbitrary geometry makes the asset less predictable and can leave design and engineering shipping different symbols.

Check font icons and image exports separately#

An icon font is still an asset system. The Material Icons integration guide explains how textual ligature names become glyphs and includes separate RTL treatment. Do not infer that loading the font automatically applies your component's mirroring policy.

Keep a ligature name such as arrow_forward as an implementation token. Translating that token changes the input used to select the glyph; translate the button's label instead. Hide a decorative font-icon element from assistive technology just as you would hide a decorative SVG, and give the owning control its action name.

Test with the font unavailable. Record whether the control retains a readable label and whether an exposed ligature token collides with nearby content. For an icon-only control, the accessible name still needs to exist independently of successful font loading. A visually missing icon and a missing name are separate failures.

For an exported PNG or standalone SVG, check whether the file already contains the reflected artwork. A CSS transform applied to the on-screen icon does not establish the orientation of a separately generated export. Record whether each deliverable is canonical artwork or a finished RTL counterpart so consumers do not reflect it again.

Protect SVG geometry and state transforms#

Horizontal reflection is simple for a standalone chevron. Compound SVGs introduce a reference-box question: around which center does the element reflect?

When transforming an inner SVG group, declare its reference box and origin rather than relying on a default that may use the surrounding SVG viewport. This fragment assumes .manual-glyph is a group inside an SVG and its owning button has the class .manual-directional:

css
.manual-glyph {  transform-box: fill-box;  transform-origin: center;} .manual-directional:dir(rtl) .manual-glyph {  transform: scaleX(-1);}

Here, the object's bounds define its center. MDN's transform-box documentation explains how that differs from the SVG viewport. For some compound designs, reflection around the full view box is intentional; choose the box that preserves the asset's alignment.

Check for asymmetric blank space in the exported view box. Reflecting the drawing can also exchange its apparent side bearings. If a counterpart needs different optical spacing, author it explicitly instead of offsetting every RTL icon with a shared pixel adjustment.

State changes create another trap. If a disclosure's expanded-state rule assigns transform: rotate(...) and its RTL rule assigns transform: scaleX(-1), one declaration can replace the other. Transform operations also depend on their order. MDN's transform reference describes composition.

Separate ownership with nested elements when necessary: an outer icon wrapper controls direction and an inner glyph controls expanded-state rotation. Then test collapsed and expanded states in both directions. Do not apply that pattern blindly to spinners or physical rotation controls, whose rotation meaning should remain intact.

The same review applies to hover movement. A directional glyph can point left while an inherited hover animation nudges it right. Decide whether that movement represents sequence progress, then adapt the animation separately from the glyph.

Give the control a name that survives mirroring#

The visible label in the maintenance button supplies its name; the decorative SVG is hidden from assistive technology. The WAI button pattern explains accessible naming and activation behavior. Keep a native button for an action and a link for navigation to another resource.

For an icon-only control, label the action in Arabic, such as aria-label="التعليمة التالية". Do not label it “left arrow” or translate an asset filename. The intended action survives a language switch even when the physical arrow direction changes. W3C's functional-image guidance makes the same distinction between an image's appearance and its purpose.

If a tooltip explains the action, translate it as well. Do not assume a tooltip alone supplies a dependable name or a touch interaction path. Check the actual accessible name and the visible explanation independently.

A toggle's state must remain available beyond its icon. A sound control, for example, may change its glyph when muted; reflecting that glyph does not expose whether it is pressed. Use the state semantics appropriate to the control rather than making the screen reader infer state from artwork.

Keep navigation behavior separate from the glyph. A flipped chevron does not reverse an event handler, change a destination URL, or implement keyboard navigation. If a component defines arrow-key behavior, verify it against that component's interaction model. An instruction-advance button does not acquire a custom arrow-key model merely because it displays an arrow.

Debug the rendered icon, not just its source name#

Start with a control whose expected action is known. Record the source asset, its directional variant, the owning element's direction, and every applied transform. This distinguishes a wrong policy from a CSS implementation error.

For the earlier button, run this in browser DevTools after the component is mounted:

js
const manualButton = document.querySelector('.manual-next');if (!manualButton) throw new Error('Maintenance button is not mounted'); const manualIcon = manualButton.querySelector('svg');if (!manualIcon) throw new Error('Maintenance icon is missing'); console.table({  semanticRtl: manualButton.matches(':dir(rtl)'),  computedDirection: getComputedStyle(manualButton).direction,  iconTransform: getComputedStyle(manualIcon).transform,  iconOrigin: getComputedStyle(manualIcon).transformOrigin});

These values explain the selected rule and transformation, not the icon's meaning. A reflection matrix cannot tell you whether the source path was already left-pointing. Inspect the rendered glyph beside its label and activate the control.

If the icon uses a CSS pseudo-element, inspect that pseudo-element's styles instead. If it uses a font glyph, identify the actual glyph and confirm the font loaded. If it uses an external SVG, distinguish the resource's artwork from transforms on its host element. A source filename is insufficient evidence in all three cases.

Check hover, focus, disabled, active, and expanded states. A disabled rule may swap an asset, and an active rule may replace its transform. Inspect a toolbar after an in-page language switch too: an asset chosen once during initialization can retain the old direction even when the label updates.

Verify direction by performing the action#

Build a small review set from the maintenance manual: next instruction, previous instruction, attach photograph, play training clip, clockwise photograph rotation, and a physical water-flow annotation. It contains controls that should change and controls that should remain stable, so an overbroad mirroring rule becomes visible.

Compare the English and Arabic versions with the same instruction selected. Advance once and return once. Confirm the expected content each time, including at the first and last instruction where one action may be unavailable. Check labels and tooltips, not just arrowheads.

Repeat inside a nested LTR panel and after switching languages without a reload. Then narrow the layout until labels wrap or the component uses icon-only controls. The directional policy should persist while the accessible names still identify the actions.

For a compound symbol, review the details that must remain stable: lettering, prohibition slashes, badges, and any representation of physical hardware. A global screenshot reflection is not an expected-result image, because the correct Arabic screen includes both reflected and preserved artwork.

A free Ritla scan can report Directional icon pointing against the sequence its control advances R025; physical-operation icons and selective artwork changes still need review against their intended meaning. Use what to mirror in RTL for related layout decisions and debugging RTL layout problems when icon placement and orientation disagree.

Checks in this guide

See what your Arabic pages are hiding

Paste a URL. Ritla renders the page on desktop and mobile, runs every check, and shows the top issues with screenshot evidence.

Scan a page freeBrowse the checks