spec sheet · stores & files

Google Drive and Transglot, keep source and locale files together.

Connect your Google account through the consent screen, then choose a folder and locale-file mapping. Sync source files and send translated locale files back to your selected folder.

Locale files in both directions

Direction: Locale files in both directions
Plan: Starter and up
Scope: locale files in one folder, in any supported format
Authentication: your Google account, connected once by consent
Get started: Connect from your workspace’s integration settings.

Create your project Setup

stores & files

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect your storage
Open your workspace’s Google Drive integration and connect your Google account through the consent screen.
connect
Map files and locales
Choose the project, folder and source-file format. Configure the locale mapping and target-file paths.
files
Start a sync
Use Sync now to read source files and process translations for the mapped target locales.
sync
Check the written files
Start Sync now. Read the run result, then check the target-locale files written into the configured folder.
deliver

Target-locale files or objects are written to the destination paths you configure.

what moves

What you can translate and deliver.

Point it at a Drive folder and a source file name pattern. The source file is pulled and parsed through the same format registry the CLI uses, pushed into the project like any other source, and each target locale is written back into the folder as its own file.

What you can translate and deliver.
Surface	What to expect
Source and scope	locale files in one folder, in any supported format
Translated output	Target-locale files or objects are written to the destination paths you configure.
Keep in mind	Sync runs are started manually from the workspace. The connector works within the configured folder or bucket prefix.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

your Google account, connected once by consent.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Open your workspace’s Google Drive integration and connect your Google account through the consent screen.
Choose the project, folder and source-file format. Configure the locale mapping and target-file paths.
Start Sync now. Read the run result, then check the target-locale files written into the configured folder.

same project, more possibilities