Skip to content
Material Design 3
Main Navigation
v3
v2
v1

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

Appearance

Sidebar Navigation

Foundations

Accessibility

Overview: Principles

Overview: Assistive technology

Designing: Overview

Designing: Color contrast

Designing: Structure

Designing: Flow

Designing: Elements

Writing and text: Best practices

Writing and text: Text truncation

Writing and text: Text resizing

Building for all: User needs

Building for all: Co-design

Content design

Overview

Alt text

Global writing: Overview

Global writing: Word choice

Notifications

Style guide: UX writing best practices

Style guide: Word choice

Style guide: Grammar and punctuation

Customizing Material

Devices

Watches: Overview

Watches: Foundations

Watches: Styles

Watches: Layout

XR

Design: Overview

Design: Interaction

Design: Layout

Design: Accessibility

Components: Overview

Components: App bars

Components: Dialogs

Components: Nav bar

Components: Nav rail

Components: Toolbars

Design tokens: Overview

Design tokens: How to use tokens

Interaction

Gestures

Inputs

Selection

States: Overview

States: State layers

States: Applying states

Layout

Overview: Overview

Overview: Parts of layout

Overview: Adaptive design

Scaffold: Overview

Scaffold: Bars

Scaffold: Rails

Scaffold: Panes

Grids & spacing: Overview

Grids & spacing: Grids

Grids & spacing: Spacing

Grids & spacing: Density

Breakpoints: Overview

Breakpoints: Compact

Breakpoints: Medium

Breakpoints: Expanded

Breakpoints: Large & extra-large

Bidirectionality & RTL

Canonical examples: Overview

Canonical examples: Feed

Canonical examples: List-detail

Canonical examples: Supporting pane

Usability: Overview

Usability: Applying M3 Expressive

Material A-Z

Styles

Color

Color system: Overview

Color system: How the system works

Color roles

Color schemes

Choosing a scheme

Static: Baseline

Static: Custom brand

Dynamic: Choosing a source

Dynamic: User-generated source

Dynamic: Content-based source

Advanced: Overview

Advanced: Apply colors

Advanced: Define new colors

Advanced: Adjust existing colors

Color resources

Elevation: Overview

Elevation: Applying elevation

Elevation: Tokens

Icons: Overview

Icons: Designing icons

Icons: Applying icons

Motion

Motion physics system: How it works

Motion physics system: Specs

Easing and duration: Applying easing and duration

Easing and duration: Tokens & specs

Transitions: Transition patterns

Transitions: Applying transitions

Shape: Overview & principles

Shape: Corner radius scale

Shape: Shape morph

Spacing: Overview

Spacing: Applying spacing

Spacing: Tokens

Typography: Overview

Typography: Fonts

Typography: Type scale & tokens

Typography: Applying type

Typography: Editorial treatments

Components

App bars: Overview

App bars: Specs

App bars: Guidelines

App bars: Accessibility

Badges: Overview

Badges: Specs

Badges: Guidelines

Badges: Accessibility

Buttons

All buttons

Button groups: Overview

Button groups: Specs

Button groups: Guidelines

Button groups: Accessibility

Buttons: Overview

Buttons: Specs

Buttons: Guidelines

Buttons: Accessibility

Extended FABs: Overview

Extended FABs: Specs

Extended FABs: Guidelines

Extended FABs: Accessibility

FAB menu: Overview

FAB menu: Specs

FAB menu: Guidelines

FAB menu: Accessibility

FABs: Overview

FABs: Specs

FABs: Guidelines

FABs: Accessibility

Icon buttons: Overview

Icon buttons: Specs

Icon buttons: Guidelines

Icon buttons: Accessibility

Segmented buttons: Overview

Segmented buttons: Specs

Segmented buttons: Guidelines

Segmented buttons: Accessibility

Split button: Overview

Split button: Specs

Split button: Guidelines

Split button: Accessibility

Cards: Overview

Cards: Specs

Cards: Guidelines

Cards: Accessibility

Carousel: Overview

Carousel: Specs

Carousel: Guidelines

Carousel: Accessibility

Checkbox: Overview

Checkbox: Specs

Checkbox: Guidelines

Checkbox: Accessibility

Chips: Overview

Chips: Specs

Chips: Guidelines

Chips: Accessibility

Date & time pickers

Date pickers: Overview

Date pickers: Specs

Date pickers: Guidelines

Date pickers: Accessibility

Time pickers: Overview

Time pickers: Specs

Time pickers: Guidelines

Time pickers: Accessibility

Dialogs: Overview

Dialogs: Specs

Dialogs: Guidelines

Dialogs: Accessibility

Divider: Overview

Divider: Specs

Divider: Guidelines

Divider: Accessibility

Lists: Overview

Lists: Specs

Lists: Guidelines

Lists: Accessibility

Loading & progress

Loading indicator: Overview

Loading indicator: Specs

Loading indicator: Guidelines

Loading indicator: Accessibility

Progress indicators: Overview

Progress indicators: Specs

Progress indicators: Guidelines

Progress indicators: Accessibility

Menus: Overview

Menus: Specs

Menus: Guidelines

Menus: Accessibility

Navigation

Navigation bar: Overview

Navigation bar: Specs

Navigation bar: Guidelines

Navigation bar: Accessibility

Navigation drawer: Overview

Navigation drawer: Specs

Navigation drawer: Guidelines

Navigation drawer: Accessibility

Navigation rail: Overview

Navigation rail: Specs

Navigation rail: Guidelines

Navigation rail: Accessibility

Radio button: Overview

Radio button: Specs

Radio button: Guidelines

Radio button: Accessibility

Search: Overview

Search: Specs

Search: Guidelines

Search: Accessibility

Sheets

Bottom sheets: Overview

Bottom sheets: Specs

Bottom sheets: Guidelines

Bottom sheets: Accessibility

Side sheets: Overview

Side sheets: Specs

Side sheets: Guidelines

Side sheets: Accessibility

Sliders: Overview

Sliders: Specs

Sliders: Guidelines

Sliders: Accessibility

Snackbar: Overview

Snackbar: Specs

Snackbar: Guidelines

Snackbar: Accessibility

Switch: Overview

Switch: Specs

Switch: Guidelines

Switch: Accessibility

Tabs: Overview

Tabs: Specs

Tabs: Guidelines

Tabs: Accessibility

Text fields: Overview

Text fields: Specs

Text fields: Guidelines

Text fields: Accessibility

Toolbars: Overview

Toolbars: Specs

Toolbars: Guidelines

Toolbars: Accessibility

Tooltips: Overview

Tooltips: Specs

Tooltips: Guidelines

Tooltips: Accessibility

On this page

Bidirectionality & RTL ​

Design products that adapt to languages that read right-to-left (RTL)


Over 2 billion people read and write in right-to-left (RTL) languages like Arabic, Hebrew, Farsi, and Urdu. Layouts should support both left-to-right (LTR) and RTL languages through mirroring and other best practices to ensure content is easy for global audiences to understand and navigate. Consider the holistic experience including global writing, localizing voice and design principles for culturally appropriate icons.

Material's components are built to support RTL, such as naming elements and tokens as "leading" and "trailing." However, extra configuration may be needed to achieve specific RTL situations.

Mirroring ​

When a layout is changed from LTR to RTL (or vice-versa), or flipped horizontally, it's often called mirroring. UI elements and text that typically appear on the left in LTR aligns to the right. Reading flow starts from the top right corner, instead of the top left.

Not all elements mirror with RTL languages. For example, graphs and charts maintain a LTR directionality for Persian and Urdu.

Layout in LTR and mirrored for RTL language.
A mirrored layout in an RTL language reverses the alignment and ordering of elements

Text rendering ​

Correct text rendering is foundational for a great user experience, and it's critical for readability and usability. Text rendering has two parts:

  1. Alignment: How the edges of the text box are placed alongside other elements
  2. Directionality: How text and other elements flow within a text box, like left-to-right or right-to-left

In RTL languages, text is usually right-aligned, and elements flow from right-to-left.

Common issues with RTL language rendering are text entry, cursor position, punctuation, phone numbers, and URLs.

Improperly rendering text in RTL languages can create cognitive overload and negatively impact user sentiment and trust.

Text field incorrectly displaying the word order of an email address and cursor placement.
Don't

Don't reverse the order of the email username and domain (@google.com). The domain should always be to the right of the username. Usernames can still be written RTL, with the cursor moving to the left.

Note: This example isn’t translated to illustrate a common issue with text rendering.

Dialog window incorrectly displaying word order decreasing readability.
Don't

Don't apply LTR directionality to RTL content, because it may scramble word order. To ensure readability across all languages, the content should have both RTL alignment and directionality.

Note: This example isn’t translated to illustrate a common issue with text rendering.

Icons & symbols ​

In RTL languages, directional UI icons, like back and forward, should be mirrored. However, in Hebrew, timelines and media controls on a page should retain left-to-right directionality.

The meaning of icons and symbols can vary significantly across cultures. For additional guidance, refer to design principles for icons.

Back and forward icons in LTR and RTL.
Back and forward icons are mirrored in RTL
Send and question mark icons in LTR and RTL.
Send buttons are mirrored in RTL. Help icons are mirrored in some RTL languages, like Urdu and Persian.

Time ​

Linear representations of time are often mirrored in RTL language experiences.

Linear progress indicators should move from right to left for most RTL languages, except Hebrew where it should remain LTR.

Circular representations of time remain the same.

RTL linear progress indicator filling from right to left and circular progress indicator filling clockwise.
  1. RTL linear progress indicator starts to fill progress from the right
  2. Circular progress indicators move clockwise

Media players

Media controls for video or audio players are always LTR.

Media player with control and progress in LTR and all other content is RTL.
In Urdu, controls and progress for media and a podcast title are shown in LTR, while all other content is RTL

Clocks

For RTL languages, the directionality of time remains LTR, and clocks still turn clockwise. However, the AM/PM symbols for 12h clocks should be placed to the left. The 24-hour clock is often used in countries where the primary language isn't English.

Clock icons, circular refresh icons, and progress indicators with arrows pointing clockwise shouldn't be mirrored.

24-hour clock in RTL.
24-hour clocks in RTL move clockwise, but mirror elements such as buttons
12-hour clock in RTL.
12-hour clocks in RTL move clockwise, but mirror UI elements such as AM/PM and buttons

Canonical layout examples ​

List-detail

The list-detail layout:

  • Is a single-pane at compact breakpointsBreakpoints are opinionated window sizes where a layout changes to match available space, device conventions, and ergonomics (previously window size classes).More on breakpoints, switching between list and detail views
  • Divides the window into two side-by-side panes on large screens
  • Is mirrored in RTL
RTL list layout on mobile.
List-detail mirrored for RTL, where text and other elements are aligned to the right and flow from right to left

Feed

Use a feed layout to arrange content elements like cards in a configurable grid for quick, convenient viewing of a large amount of content. The feed layout is mirrored in RTL.

RTL feed layout.
Feed layout mirrored for RTL, where the order of text, grid, and other elements align to the right and flow from right to left

Supporting pane

Use the supporting pane layout to organize content into primary and secondary display areas. The supporting pane layout is mirrored in RTL.

RTL supporting pane in an RTL language.
Supporting pane to the left of the primary content. Text and other elements within the pane are aligned to the right and flow from right to left.

Component examples ​

Badges

Change the position and alignment of badges for RTL languages.

Small badge on the top left of a folder icon.
Small badge appears on the top left of the icon
Large badge on the top left of an image icon.
Large badge appears on the top left of the icon

Toolbars

Toolbars provide actions related to the current page. For RTL languages, mirror the order of the tools.

RTL floating toolbar.
Mirrored floating toolbar, where the FAB appears on the left

App bars

App bars are placed at the top of the screen to help people navigate through a product:

  • Mirror an app bar's layout in RTL
  • Flip appropriate icons, such as arrows
4 app bars in RTL.
  1. RTL center-aligned, small app bars
  2. RTL medium, flexible app bar
  3. RTL large, flexible app bar

Navigation rail

The navigation rail is placed on the leading edge of the screen, on the left side for LTR, and on the right for RTL.

Nav rail on the right side for an RTL language, and left side for LTR.

Based on the language, a navigation rail is set on a screen's leading edge:

  • Right side for RTL languages
  • Left side for LTR languages

Expanded navigation rail

Expanded navigation rails that open from the side are always placed on the leading edge of the screen, on the left for LTR languages, and on the right for RTL.

RTL expanded navigation rail, including mirrored icons.
RTL expanded navigation rails open from the leading edge and should include mirrored icons

Text fields

Icons in text fields are optional. Leading and trailing icons change their position based on LTR or RTL contexts.

Text fields in RTL with leading and trailing icons.

Icons, symbols, and label text for RTL:

  1. Icon signifier
  2. Valid or error icon
  3. Clear icon
  4. Voice input icon
  5. Dropdown icon
  6. Image

Chips

The leading icon of input chips can be an icon, logo, or circular image.

The trailing icon is always aligned to the end side of the container. It's placed on the right for LTR and on the left for RTL.

Filter chips with checkmark icons in RTL layout.
Filter chips shown in an RTL layout. Note: This example is not translated to help illustrate mirroring.

Swipe gestures ​

Gestures are the ways people interact with UI elements using touch or body motion.

People can navigate horizontally between peer views like tabs and to complete actions.

RTL swiping and gestures should mirror their counterparts in LTR. If a product includes a delete icon revealed when swiped from the right for LTR languages, the same should be possible on the left for RTL languages.

RTL list layout with swipe gesture revealing additional actions.
Swiping reveals additional action in RTL list layout

On Android, predictive back allows people to swipe left or right on the screen to go back or dismiss modal components.

RTL predictive back features should mirror those found in a LTR context.

The predictive back gesture should adjust for RTL languages
Pager
Previous pageBreakpoints: Large & extra-large
Next pageCanonical examples: Overview

Released under the Apache 2.0 or CC BY 4.0

Copyright © 2018-Present Google

https://m3.material.io/foundations/layout/bidirectionality-rtl

Released under the Apache 2.0 or CC BY 4.0

Copyright © 2018-Present Google