Skip to content

RTL

One attribute mirrors the whole UI. You don’t touch components or change the layout to mirror it. The engine emits logical properties under the hood.

Turn it on

html
<html dir="rtl">

With that, margins, padding, inset, borders, corner radii, and text alignment mirror. In LTR the render is identical to before.


Logical names, no layout migration

Utilities are named after the reading axis, not the side of the screen: ms-* and me-* (margin start and end), ps-* and pe-* (padding), align-start and align-end (alignment), start-* and end-* (inset), border-e-* (the end border), and radius-ss-inherit, radius-se-inherit, radius-es-inherit, radius-ee-inherit, radius-s-inherit, and radius-e-inherit (corners). Under the hood they emit logical properties (margin-inline-start, padding-inline-start, text-align: start), so atomic.css has no physical inline-axis properties (left/right) and the same HTML works in LTR and RTL.

The names are logical (ms-*, ps-*, align-start…), with no left/right equivalents.

html
<!-- You write this (logical names) -->
<div class="ts ms-base align-start">…</div>

<!-- The engine emits: margin-inline-start + text-align:start -->
<!-- → left in LTR, right in RTL, on its own -->

Overlays

Floating positioning (menus, popovers, tooltips) is direction-aware: in RTL, the start/end alignment of top/bottom placements flips (start → the trigger’s right edge). It reads it from getComputedStyle(trigger).direction, so it works per subtree.

Exceptions

Explicit left/right sides and toast corners stay physical by design. When you ask for “right,” you want the actual right.

Typography

In Arabic, Persian, Urdu and Hebrew, headings and labels drop letter spacing and use a line height of at least 1.35, so letters stay joined and diacritics don’t collide. The lang attribute on the page or a block turns this on; dir="rtl" alone doesn’t.


Guarantee

Every page in these docs is also checked with dir="rtl", to confirm that mirroring doesn’t cause overlaps and that LTR doesn’t change.