Launched this week
RTLAuto
Bidirectional design automation for Figma
21 followers
Bidirectional design automation for Figma
21 followers
RTLAuto helps Figma teams adapt product interfaces between LTR and RTL without rebuilding every screen by hand. It mirrors layouts, handles BiDi text, protects semantic icons and complex artwork, creates direction-aware component variants, and can translate selected text with Google, Gemini, or OpenAI. Built for teams shipping multilingual products across both left-to-right and right-to-left experiences.
Hi Product Hunt! 👋
I'm Muhammad, the creator of RTLAuto.
We built RTLAuto to give Figma teams a repeatable LTR ↔ RTL workflow for production design systems.
Supporting both directions often means manually rebuilding layouts, fixing components, checking icons, and cleaning up mixed-language interfaces screen by screen. It's time-consuming and difficult to keep consistent as products grow.
RTLAuto focuses on production-ready workflows: mirroring layouts, handling BiDi text, protecting semantic icons and complex artwork, creating direction-aware component variants, and optionally translating selected text.
It's built for teams shipping multilingual products, regional interfaces, and enterprise design systems without rebuilding every screen by hand.
Thanks for checking it out! I'd love to hear your feedback and answer any questions throughout the launch. 🚀
the icon-preservation and layout mirroring answers are the obvious hard part, but the sneakier gotcha in real RTL work is embedded LTR content inside RTL text - phone numbers, dates, prices, English brand names sitting inside an Arabic or Hebrew sentence. those are supposed to stay LTR even though everything around them flips. does RTLAuto detect and protect those runs automatically, or is that still something a designer has to manually flag after the mirror pass?
@galdayan Yes, RTLAuto automatically preserves embedded LTR content inside RTL text, including numbers, dates, URLs, email addresses, and Latin-script brand names, so no manual tagging is needed in typical workflows. Only rare edge cases with unusual formatting may require a quick review.
It's live now I'd love to hear how it works with your files :
https://www.figma.com/community/plugin/1623814570395556605
@muhammad_mousa_ixdf_ good to hear it's handled by default rather than opt-in, that's the kind of thing that's easy to forget to flag manually every time. will try it on an actual mixed-language file since I don't have a Figma RTL project handy right now
@galdayan Thanks, Gal. That’s exactly why we made it the default. A mixed-language file is actually a great test case, even without a dedicated RTL project. I’d be interested to hear how it handles your real content and any edge cases you encounter.
@muhammad_mousa_ixdf_ will do, probably going to grab a bilingual PDF I have lying around with hebrew and english mixed in the same paragraph. if that holds up without manual tagging I'll be pretty convinced
The direction-aware component variants saved me from rebuilding an entire dashboard today. BiDi text handling on real product copy was smoother than the manual flips I have been doing.
@erafettin155441 That dashboard use case is exactly what RTLAuto was built for. Glad the BiDi text and variants workflow helped on real product copy.
finally a plugin that flips my Figma files to arabic without mangling the icons we spent weeks aligning. the bidirectional text handling actually understood our mixed content out of the box
@bayramblrn Thank you, Bayram! Preserving carefully aligned icons while handling mixed Arabic and English content was one of the biggest reasons we built RTL Auto. Really glad it worked smoothly for your files 🙌
Does it keep things in sync if I update the original LTR frame afterwards, or is it more of a one-time conversion?
@elanurjjly Yes. If the original components are updated and those changes are published to the Figma library, the updated direction-aware variants will be available to files using that design system after they accept the library update. This keeps both LTR and RTL directions aligned through the component library workflow, rather than relying on a one-time screen conversion.
Tried it on a Figma file with mixed text and icons and the mirror worked without breaking the directional arrows. Saving it as direction-aware variants is genuinely useful, would have saved my team hours last sprint.
@osmanivfv Great to hear the directional arrows stayed intact. Protecting semantic icons while mirroring layouts is one of the core parts of the workflow.
finally something that handles my semantic icons without breaking them, ran a couple screens through it and the mirroring actually feels right instead of the usual flip-and-pray result.
@feridel6ld Exactly. The goal is not just to flip a screen, but to preserve the meaning of icons, artwork, and direction-sensitive details while making the layout feel native.