Transept

Translate

Google Drive, Docs to Docs

Connect Drive once. Pull in a Google Doc, a folder of DOCX files, or a PDF report. Translate. Send the result back as a new Doc — same Drive, same folder structure, same formatting.

Start translating→

Free to begin · No card required

In context✦

For agencies and distributed teams, Google Drive is the institutional default. Documents live in Drive folders, get shared by link, and accumulate review history across collaborators. The standard translation workflow for Drive content has been: download the Google Doc as DOCX, run it through a translator, upload the result back as a new Doc, lose the formatting on the way, fix it by hand. Transept’s Drive integration cuts that loop. Connect once, pick the file or folder, translate inside Transept with full document context, and a localized Google Doc lands back in the same folder — formatted exactly like the original.

Drive to Drive, no downloads

No download, no re-upload, no naming the new file v3_final_translated. The integration treats Drive as the source of truth and writes back to it.

  1. Connect Google Drive

    OAuth from Settings. Grant Transept access only to the files and folders you pick — not your whole Drive.

  2. Import a file or folder

    Pick a Google Doc, a DOCX file, a PDF, or a whole folder. Folders import as a batch; individual files import to the editor.

  3. Translate, edit, QA

    The standard Transept workflow — glossary, styleguide, sentence alternatives, Smart Proofread — runs on the imported content.

  4. Export back to Drive

    A new Google Doc lands in the same folder, named for the target language. Original stays untouched.

Transept Drive integration showing a Google Doc being imported

Where it lands hardest

Agencies

Client documents live in Drive. Translate, deliver, archive — no DOCX email chains.

Distributed teams

A team that drafts in Docs gets localized Docs back, ready to share with regional reviewers.

Schools, NGOs, public sector

Document-heavy workflows where Drive is the institutional default.

Footnotes✦

Questions, answered without the fluff

  • No. The picker scopes access to just the file or folder you select. Revoke anytime from Drive settings or from Transept Settings → Integrations.
  • Docs go in and Docs come out. No download step. DOCX files in your Drive work the same way — Transept reads them in place and writes a new file back.
  • The translated copy lands in a fresh Doc without the source-side comments. The original stays untouched, so your review history is preserved.
  • Not yet — currently it’s a one-way export. Continuous sync is on the roadmap; subscribe to the Journal for updates.
  • No. The Google Drive picker scopes access to specific files or folders only. Transept never sees your other Drive content. Revoke per-file access from Drive settings, or pull the integration entirely from Settings → Integrations in Transept.
  • Currently Docs and DOCX/PDF files in Drive. Slides and Sheets are on the roadmap — Slides especially makes sense for marketing decks and pitch material. Reach out if you have a pressing use case and we’ll prioritize.
  • In the same Drive folder as the source, named with the target language code (e.g. `Welcome_Email-de.docx`). You can change the naming convention or move it after.
  • Yes — both personal Drive and shared (team) drives. Permissions on the translated file inherit from the source location, so review access stays the same.
  • Suggestions are accepted before translation, so the resulting text is the source-of-truth version. Comments stay on the original; the translated Doc starts clean. This preserves your review history and gives the translated artifact a fresh slate.
Related✦

Keep reading around this capability

❧

Docs in, localized Docs out

Start translating→

Free to begin · No card required