Everything people ask before translating a Framer site.

A Framer plugin that translates your pages and creates real translated pages inside your own project. You pick the pages and the target languages, the plugin scans every text node, translates it, and duplicates your page structure at /fr, /de, /es.

No. Page Translator creates regular Framer pages, so it works without the Locales add-on. Framer charges $20 per month per locale, roughly $720 a year for three. Page Translator is €29 once, for unlimited languages. The trade: native Locales also give you server-rendered hreflang, translated slugs and translated metadata, which this plugin does not.

Any Framer plan. The translated pages are ordinary pages in your project, so no paid add-on is required.

31 target languages are available out of the box. On Pro you can also define a custom language with your own code and label, then translate it through the copy/paste LLM mode.

Yes. The free plan covers 1 target language, up to 5 pages, and one instant translation run. DeepL and LLM modes are included. Enough to translate a small site and see the result on your own pages before paying anything.

It works on the static pages of any Framer site. CMS collections such as blog posts and case studies are handled by the sister plugin, CMS Translator.

No API key. Instant mode runs the AI translation inside the plugin. Pick your pages and languages, click Translate, and the translated pages are created. It is the default mode.

Yes, in Advanced mode. Paste your DeepL key and the plugin runs the whole pipeline automatically. DeepL closed its old 500,000-per-month free API plan to new signups: new accounts get a one-time 1,000,000-character credit that does not reset.

Yes. The copy/paste mode extracts every text node into a structured prompt. Paste it into the AI you already pay for, paste the returned JSON back into the plugin, and the pages are generated. No extra subscription.

To protect terms that must never be translated: product names, proper nouns, technical jargon. Add them in the Glossary panel and they apply automatically in both DeepL and LLM modes.

Yes, on Pro. Create a custom language entry with a code and a label, then use the copy/paste mode with ChatGPT or Claude for that language.

Yes. They are real Framer pages. Edit any text, component or layout directly. On Pro, Sync re-translates upstream changes at the text-node level without overwriting your manual edits.

Sync tracks what changed since the last translation. Change 3 paragraphs on /home and Sync detects those 3 text nodes and re-translates only those. The rest stays untouched. Sync is a Pro feature.

Inside your own Framer project. Weglot serves translated versions on a subdomain or a subdirectory, and Linguana hosts them on its own infrastructure. Page Translator writes real pages into your project, so they are yours.

Yes. They are real pages at real URLs, so search engines crawl and index them like any other page on your site. Google also states that localized pages are only treated as duplicates if the main content is left untranslated. Indexing and hreflang are separate: see the hreflang answer below.

Yes, on Pro, but read how. Framer renders the served lang attribute and hreflang from its paid native Locales and locks them, so no plugin can write them into the published HTML. Page Translator injects hreflang link tags with a script that runs in the browser, and sets lang and text direction client-side. Google renders JavaScript and can pick the tags up; other crawlers are less reliable at it. You will find the setting under Settings, hreflang.

Yes. Arabic and Hebrew get the correct text direction, set client-side. Note that text direction and the lang attribute serve accessibility and browser translation prompts. Google states it does not use the lang attribute to detect a page's language.

Your page structure, duplicated under the locale path: /fr, /de, /es and so on.

Yes. After the first translation the plugin auto-generates a Language Switcher code component. Insert it on the canvas in one click. It has three display modes, and colors, borders, typography, shadow and animations are customizable.

It only resolves links on the published site. On the canvas it shows a toast reminder instead.

€29, once. That covers unlimited languages, unlimited pages, unlimited instant translation, batch translation, Sync, the Language Switcher, client-side hreflang injection and priority support.

No. One payment, and all future updates are included. Framer Locales costs $20 per month per locale, which is roughly $720 a year for 3 extra languages, and we found no annual discount on the locale add-on.

No. Pro covers unlimited languages for the same €29.

1 target language, up to 5 pages, one instant translation run, DeepL and LLM modes, and real page duplication. No card, no expiry.

CMS Translator is €19 on its own. The Translation Pack bundles both plugins for €39, which saves €9.

If the Pro version does not work as described, you can request a full refund within 14 days of purchase. Because the translated pages stay in your Framer project even after you uninstall the plugin, a refund covers a fault, not a change of mind. Email me with your order number, or the email you used at checkout. Refunds are processed through Polar and take 5 to 10 business days, and your Pro licence is then deactivated.

Read the full refund policy →

No. Page Translator handles static pages. CMS Translator creates a synced translated mirror of any collection, re-syncable in one click.

Locales is the most integrated option, and stronger on SEO plumbing: server-rendered hreflang, translated page paths and metadata per locale, native RTL, CMS included. It costs $20 per month per locale, so about $720 a year for three. Framer does not document what happens to locales if you stop paying. Page Translator is €29 once, the pages are ordinary pages in your project, and they stay if you stop, but its hreflang is injected client-side, it translates slugs only in DeepL mode, and it never translates page titles or meta descriptions.

Both are subscriptions with word or credit caps, and both serve hreflang server-side. Weglot runs on any platform and gives translators a dashboard and a visual editor; its entry plan covers one language, three languages means the Business plan at about €290 a year. Linguana is cheaper, focused on no-code platforms, and translates slugs and meta tags. Neither documents publicly what happens to translated content after cancellation. Page Translator does one thing: real translated pages inside your own Framer project, paid once.

Nothing. The pages are part of your Framer project, not an overlay or a proxy. Uninstall the plugin and every page stays exactly where it is.

Yes. It is built on the Framer plugin API and does not work on other platforms.

Text baked inside a component stays invisible to the plugin until it is exposed as a component property. Open the component, select the text layer, and expose it as a property.

Check the key is valid with the Validate button in the plugin, check your DeepL quota, then retry.

Paste the raw output back into ChatGPT or Claude and ask it to return only valid JSON, no commentary. Paste the cleaned version back into the plugin.

hreflang is a Pro feature. Check that your licence is active, then open Settings, hreflang, and generate them. Also check that plugin custom code has not been disabled in your Framer site settings: the tags are injected by a script that lives there, and a plugin cannot re-enable it for you.