If your Framer site has a blog, case studies or a product catalogue, most of your indexable content is not on a static page. It is in a CMS collection.

Translating the static pages and stopping there leaves the bulk of your site in one language. Collections need their own treatment, because they have their own structure, their own URLs, and one trap that surprises everyone.

Why collections are a different problem

A static page is a tree of text nodes. You can walk it, translate each node, and write the result into a duplicated page.

A collection is a table. Each item has fields, and those fields have types: plain text, rich text, slugs, images, dates, numbers, and references to other collections. You cannot translate a collection by walking text nodes, because there are none. You have to understand the schema.

That is why Page Translator handles static pages and CMS Translator handles collections. They are not the same job.

What a synced mirror is

CMS Translator creates a mirror collection: a translated copy of your source collection, linked back to it.

The link is the useful part. When you publish a new article or fix a typo in the source, you open the mirror and click Sync. The plugin re-translates only what changed upstream. Everything else stays exactly as it was, including any edits you made by hand.

That behaviour matters more than it sounds. A tool that overwrites your corrections on every sync is a tool whose corrections you stop making.

The trap: collection references

This is the one thing that catches people.

Collection references cannot be translated directly. If a blog post has a field pointing at an Author collection, or a Category collection, that reference is skipped. The plugin warns you about skipped references during setup.

You reconnect them manually in the synced collection after translation. It takes a few minutes on a small site. On a large one, plan for it, because nobody expects it.

Editing individual items

Machine translation gets the meaning right and the voice wrong. Marketing copy suffers most.

Any translated item can be edited inline from the plugin: open the translated collection, click an item, rewrite the strings, the rich text or the slugs directly.

Your edits survive the next Sync. The plugin only re-translates what changed in the source, so a manual rewrite of your best article is not going to be undone the next time you fix a typo somewhere else.

Use the Glossary for anything that must never be translated at all: product names, proper nouns, technical jargon. It is shared across every translated collection in the project, so you set it once.

What it needs, and what it costs

CMS Translator uses DeepL, with your own API key. 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. If you hit a quota error, either upgrade your DeepL plan or split the translation into smaller batches.

LLM copy/paste mode is not in V1. It is on the roadmap, following the same pattern as Page Translator.

It supports 15 or so built-in languages, and you can enter any ISO code for one that is not in the list.

It works on any Framer plan, Free, Basic, Pro or Scale, and does not require the Locales add-on.

It costs €19 on its own. The Translation Pack bundles it with Page Translator for €39, which saves €9 and covers your whole site, static pages and collections.

What happens if you uninstall

Your synced collection stays in your project as an orphan. The data is preserved. You can bind it to pages normally.

What stops working is the Sync button. Reinstall the plugin and the link comes back.

Where this fits in a multilingual site

Translating collections is one step in a sequence, and it is usually the last one people get to:

Translate the static pages.
Set hreflang, the lang attribute and text direction. There is a guide to hreflang because it is where sites break.
Add a language switcher made of real links.
Translate the collections, and reconnect the skipped references.
Review the items that convert. Leave the long tail alone.

The multilingual SEO guide covers the rest of the sequence.