Check three RTL-readiness dimensions per component
Each component is checked for logical CSS property usage, direction-neutral icon handling, and direction-aware text alignment — the three most common sources of RTL breakage.
Free MVP localization tool
RTLReady
Check which components in your interface are ready for right-to-left languages like Arabic and Hebrew, and which will need layout adaptation.
- Calculated instantly from your inputs
- No signup or data submission
- A focused next step for MVP planning
Your entries remain in this browser session and are not sent to MVPHub.
Your inputs
Audit components for right-to-left readiness
Enter one component per line as Component | uses logical CSS properties (yes/no) | icons are direction-neutral (yes/no) | text alignment is direction-aware (yes/no). List every major component or layout pattern in your interface.
Your calculated result
Your result
0/100
Planning score
Recommended next actions
How it works
Score readiness per component and overall
Each component gets a readiness score from its three checks, rolled up into an overall interface RTL-readiness score.
Rank components needing the most rework
Components failing the most checks are surfaced first, since they represent the biggest effort if you plan to support RTL languages.
Frequently asked questions
What are "logical CSS properties"?
CSS properties like margin-inline-start/end and padding-inline instead of margin-left/right — logical properties automatically flip direction based on the page's text direction, physical properties do not.
Do all icons need to flip in RTL?
No — directional icons (arrows, chevrons showing "next/back") should flip; symmetric icons (search, settings gear, trash can) should not. Getting this wrong in either direction looks broken.
Do I need to support RTL if I have no current plans for Arabic/Hebrew markets?
Not urgently — but building with logical CSS properties from the start costs little extra and makes future RTL support far cheaper if you ever expand into those markets.
Does this test actual rendering in an RTL browser mode?
No — you self-assess each component against the three checks. For final verification, test the actual build with the browser or OS set to an RTL language.
How we compare
| Capability | MVPHub | Assuming RTL support if the site "just displays" reversed | A full internationalization (i18n) engineering audit |
|---|---|---|---|
| Checks logical CSS, icon direction, and text alignment specifically | ✓ | × | ✓ |
| Ranks components by rework effort needed | ✓ | × | — |
| Full engineering review of the actual codebase | × | × | ✓ |
| Instant, no i18n engineering engagement required | ✓ | ✓ | × |
MVPHub gives a fast self-assessment across the most common RTL breakage points. A full i18n engineering audit reviews the actual codebase, which this self-assessment does not replace.