Translate with AI
Add target languages, draft translations with AI directly on the Figma design, and steer the model with your glossary, tone, and project context.
Open as Markdown Full docs bundle
Open this page in
KopiMark drafts translations directly on the canvas. The AI picks up your project’s tone, your glossary, and the surrounding design context — so the output is closer to “good first draft” than to a literal word-for-word swap.
This guide covers the three things you need to know: adding a language, running a translation, and steering the model.
1. Add a target language
Languages are project-level. Open the project, then go to Project Settings → Languages.
-
Click Add language and pick a target locale (e.g.
fr-FR,de-DE). -
Optionally rename it for display — useful if you ship one set of copy to multiple regions.
-
Save. The new language now appears in the editor’s language switcher and in the page-grid filters.
2. Switch the editor to that language
In the editor toolbar, open the language switcher and pick your target. The canvas re-renders with whatever translated copy already exists; untranslated nodes fall back to the source text in a slightly muted tone, so it’s easy to see what still needs work.
3. Draft translations with AI
You can translate one node at a time or in bulk.
One node at a time
-
Click a text node on the canvas with the target language active.
-
In the side panel, click Translate with AI.
-
KopiMark generates a draft using your glossary, project context, and any tone notes. The draft lands in the editor as a normal revision — review it like any other edit and tweak as needed.
Multiple nodes at once
-
Open the Bulk actions panel (in the editor’s right rail).
-
Choose Translate.
-
Pick the language(s) and the scope: current page, selected nodes, or everything untranslated. The progress bar shows “Translated: X / Y” as it goes, with errors counted separately if any fail.
Bulk runs are budget-aware — KopiMark stops cleanly if you’d exceed your plan’s AI translation allowance and shows what remains.
AI translations are metered per month. Free includes 50 / month, Starter 1,500, Team 5,000, Business 15,000. The counter resets on your billing renewal date. See Plans and limits.
4. Steer the model
Three places to make the AI sound more like your brand:
Project translation settings
Project Settings → Translation is where you set:
- Product context — one paragraph describing what your product is. Used as a system hint on every translation.
- Tone — short notes like “warm, second-person, no exclamation marks”. The model treats these as constraints.
- Glossary toggles — which glossary terms apply to this project.
These settings apply to every AI translation in the project. Tweak them and re-run a single node to see the effect before bulk-translating.
Workspace glossary
Bigger picture: your workspace glossary (Settings → Glossary) holds terms shared across every project — brand names, product names, words that should never be translated. The AI honours these as hard constraints, not suggestions.
Glossary terms can specify per-language translations or be marked as “keep in source language” (the typical choice for a brand name).
Per-cell context
For a single tricky string, the editor’s translation side-panel has a Context field where you can paste a one-line hint just for that node. It’s a great way to disambiguate UI labels where the source is too short for the model to guess (e.g. “Save” meaning commit a change, not rescue).
5. Review and approve
Translations are statuses too. Set up a status flow like Drafted → Reviewed → Shipped and assign the Drafted nodes to your reviewer. KopiMark sends them an in-app and email notification with a deep link to the exact node. See Statuses and approvals.
FAQ
Does editing an AI draft count as a new AI translation?
No. AI translations are metered against successful AI completions only. Tweaking a draft, retyping it, or reverting to a previous revision doesn’t burn additional quota.
Can I undo an AI translation I don’t like?
Yes. AI drafts land as normal revisions in the History panel, so you can roll back to the previous translation (or to the source) the same way you’d undo any manual edit.
How does the AI handle glossary terms marked “keep in source language”?
As a hard constraint. The model is instructed never to translate those terms, which is the typical setting for brand names and product names. Per-language translations work the same way — if a glossary term has a target translation, the model uses it verbatim.
What if the source string is too short for the AI to guess the meaning?
Use the Context field in the editor’s translation side-panel. A one-line hint (e.g. “Save” meaning commit a change, not rescue) is usually enough to disambiguate UI labels where the source alone is ambiguous.