Feature Requests

Currently translated texts shows only in one colour. It would be great if we could have the option in the translation text edit field to add a colour style to highlight selected words or sentences.

Currently, RTL behavior in Framer mirrors layouts too aggressively, which causes unintended layout changes and reduces control in real production use cases. From real-world multilingual projects, the expected workflow is: Maintain layout stability by default Apply selective mirroring only where needed At the moment: Elements like layout alignment, distribution (e.g., horizontal “Start → Right”), and spacing are automatically flipped in RTL This creates inconsistencies, especially in navigation and structured layouts Typography, spacing, padding, and alignment lack per-locale control Users often need to rely on custom scripts or workarounds to manage RTL/LTR behavior Key needs Per-locale control for: Text alignment Typography Spacing/padding/gaps Flex/stack distribution Ability to disable automatic mirroring globally or per element More predictable behavior for layout alignment in RTL (e.g. horizontal stacks not flipping unexpectedly) Better control over which elements should mirror vs remain fixed Real issue example Layout distribution set from “Start → Right” flips incorrectly in RTL Navigation and structured components behave inconsistently Requires manual overrides or external scripts to fix Why this matters Framer already supports localization, but advanced multilingual sites require fine-grained control over layout behavior, not just automatic mirroring. Better RTL handling would significantly improve: production workflows scalability of multilingual sites consistency across layouts

It's currently impossible to have external links specific to a locale. I would want my english version pointing to the english version of the website linked, the french to the french... etc.

Fantastic feature but from all I am seeing it is very inflexible and very unsustainable especially for a young business. Its either one locale with a pro plan or $200 a month for more. Which essentially means even on a pro plan you are only left with the option to pay $200, as one language in most cases wont suffice for a business if its even thought about localizing in the first place. I was also told my business does not need a business plan so access to that is out of the picture as I would assume many others are in the same place. Can I please suggest to add: Ability to add more locales with at least manual translations on the pro plan. Maybe charge for AI translations separately, as Linguana does? (Not being able to add more than one locale to even manually translate is just absurd, it takes away from the whole feature) An assortment of pricing options according to the needs of the user such as how linguana or weglot does. This can be based on AI translations, locales, plans, etc. I strongly think this will lead to more consumers utilizing this feature, cause clearly there is a strong need for it, but when alternatives are almost 1/10th the price it is definitely worrying.

Currently mixed fonts are not taken over to another locale. It would be great to have this feature since workarounds are labor-intense and have their own disadvantages.

When a Text element is set to Fill, its alignment cannot adapt automatically to RTL/LTR based on locale. This forces creators to duplicate text layers for Arabic and English just to control alignment. A conditional Text Align based on locale or layout direction, similar to conditional visibility, would greatly improve RTL support in Framer.

I’m working with a defined brandkit (tone, language rules, terminology) and currently don’t have a reliable workflow for translations in Framer. The AI Translate field is limited to 250 characters, which is not sufficient to apply consistent brand rules. Good translations require more context and structured guidance, otherwise results become inconsistent (tone, terminology, language rules). As an alternative, I tried creating translations externally and importing them. This is only feasible via Managed Collections through the API. However, in this setup, Editable Fields no longer behave as expected, which means I lose the ability to manage assets like images directly in Framer. This creates a trade-off: either use AI Translate with limited control or use external translations and lose CMS editing flexibility What’s currently missing is a workflow that allows: applying a brandkit consistently to translations importing or syncing translated content while keeping full editing capabilities in the CMS (including assets) It would be helpful to understand if there are plans in this direction, for example: more flexible or structured AI Translate rules or a proper import/sync workflow that works with Editable Fields

I want the dropdown of the framer language switcher to be a better Ui and with customization options.

The native cookie banner currently only supports two consent regions (EU and World) determined by browser language and timezone. This isn't reliable for compliance, for example, it can't distinguish a Spanish-speaking visitor in Spain (GDPR) from one in Mexico (no GDPR). It would be great to have actual geolocation-based consent detection built into the native cookie banner, so the correct consent mode is applied based on where the visitor actually is, not just their browser settings.