doppel

Client files. Translation-ready.

Another language. The same attention to detail.

Turn your clients’ Google Docs and Slides into translation-ready files. Work in your CAT tool, then create a translated copy with the formatting preserved.

doppel can only open files you choose in the Google file picker and the copies it creates. It can’t browse the rest of your Drive.

A Google Slides promo deck in English
Source · EN
The same deck in French, with the layout intact
Counterpart · FR
The same Google Slides deck, before and after. Translated text needs more room than the source, so the layout review refits it.

A client link is the beginning of the job.

Your clients work in shared documents and presentation decks. Your team works in translation tools. doppel connects the two, so you can prepare the text for translation and bring it back into a copy of the original.

The workflow

From source to counterpart.

  1. 01 / Prepare

    Choose a Google Doc or Slides deck and export the text as XLIFF.

  2. 02 / Translate

    Use your CAT tool and your established translation and review process.

  3. 03 / Return

    Import the translated XLIFF to create a translated copy. Review the result and any reported exceptions before delivery.

The details belong in the translated file, too.

Preserve supported formatting, links, images and document structures as text moves between the source and your translation workflow. See reported limitations rather than assuming every element was translated.

When the source changes, see what changed.

Export new or edited content and import the translated updates onto the copy. Keep the handoff moving when the client revises the source.

Built around your translation process.

Exchange XLIFF 1.2 or 2.0. Keep translation and review in your team’s tools. Add machine translation through your own Intento account when it fits the job.

Optional machine translation

Machine translation through your own Intento account.

When a job calls for machine translation, doppel sends the text through Intento using your agency’s key, so your engine choices and provider agreements still apply.

  • Your account, your contracts

    Connect your own Intento API key. It is checked with Intento, stored encrypted and only used for your team’s translations.

  • Routing or a named provider

    Use Intento’s routing to pick the engine for each language pair, choose a provider such as DeepL, or select a custom routing from your account.

  • Pre-translate or go direct

    Pre-fill the XLIFF for post-editing in your CAT tool, or create a machine-translated copy of the file in one step.

  • Protect brand names

    Keep a never-translate list of brand, product and people’s names so they are left exactly as written.

doppel for FigmaBeta

Design files, translated in place.

A plugin for Figma Design and Figma Slides. Pick the frames or slides, choose a language, and doppel creates translated copies beside the originals with the type styles, links and layers intact.

  • Figma Design frames and Figma Slides decks, translated into copies beside the originals.
  • Type styles, colours, links and layer structure are kept; text set in components and instances is translated too.
  • The same XLIFF 1.2 and 2.0 exchange as the rest of doppel, so Figma text can go through your CAT tool.
  • The layout review measures the translated text, refits what it safely can and lists what needs a designer.
  • In beta: we’re looking for agencies to try it on real client files and tell us what breaks.

The plugin isn’t listed in the Figma Community. We install it with your team and work through the first files with you.

The doppel plugin open in Figma next to a mobile app design, with the frames, source and target languages and Intento routing on screen
The plugin sits beside the canvas: pick the frames, set the languages and your Intento routing, and it makes the copies.
A mobile product screen in Figma beside its French counterpart: the same photo, rating, size buttons and price, with the interface text translated
A product screen and the French copy doppel made from it. The photo, layout and controls are untouched; the longer French labels still sit inside their buttons.

Practical questions.

Does doppel replace our CAT tool?
No. doppel exports and imports XLIFF so the translation work can stay in your CAT tool. Validate your tool’s XLIFF handling with representative files during evaluation.
Which machine translation engines can we use?
Any engine available through your Intento account. Let Intento’s routing choose the engine for each language pair, pick a specific provider such as DeepL, or use a custom routing you have set up with Intento. Machine translation is always optional.
Does it support Figma?
There is a doppel plugin for Figma Design and Figma Slides, in beta. It translates frames and slides into copies and exchanges XLIFF like the rest of doppel. It isn’t in the Figma Community directory: get in touch and we’ll set your team up.
Will everything be translated?
Some elements are unsupported, such as pending suggestions, tables of contents, charts and WordArt. doppel reports what it could not translate; final linguistic and layout review remains part of delivery.
Does it change the original file?
No. The import creates a translated copy of the original.

Give client files a dependable route through translation.

Sign in with Google