# General Translation Integrations: Supported content
URL: https://generaltranslation.com/en-US/docs/integrations/google-drive/reference/supported-content.mdx
---

title: Supported content
description: Learn which files the Google Drive integration supports and how translated copies work. Reference for Google Drive content.

---

The Google Drive integration translates Google Docs and Google Slides. It keeps each source unchanged and creates one translated copy for every target language.

## Overview [#overview]

| Topic | Description |
| --- | --- |
| [Supported file types](#file-types) | Google Drive file types supported for translation. |
| [Ways to connect](#access-modes) | Personal and Organization shared drive connections. |
| [Dashboard permissions](#permissions) | Permissions needed to connect and use Google Drive. |
| [Translated copies](#translated-copies) | Where translations are saved and how they are named. |
| [Updating translations](#update-behavior) | What happens when a source changes. |

## Supported file types [#file-types]

- Google Docs (`application/vnd.google-apps.document`)
- Google Slides (`application/vnd.google-apps.presentation`)

Google Sheets, PDFs, Microsoft Office files, images, and folders are not supported.

The integration preserves the structure of Google Docs. For Google Slides, it also adjusts the translated presentation's layout for the new text.

## Ways to connect [#access-modes]

- **Personal account:** each person signs in with Google and chooses the files they want to translate. The integration uses the `drive.file` scope and can access those files and the translated copies it creates.
- **Organization shared drive:** everyone with Project access uses a shared connection set up by an Organization admin. The connection uses the `drive` scope to browse its configured shared drives.

Disconnecting a personal account removes that person's authorization. It does not delete linked files or translated copies.

<Callout type="info">
  **Organization admins:** Shared drive access must be available on your plan. Open **Organization > Connections**, click **Add connection**, then **Set up** for Google Drive; add the displayed email to the shared drive as a **Content manager**, return to the Dashboard, and click **Verify access**.
</Callout>

## Dashboard permissions [#permissions]

| Action | Required permission |
| --- | --- |
| Connect Google Drive to a Project | `project:write` |
| Add or remove files | `translations:content:write` |
| Start or force translation | `translations:content:write` |

Project access and plan features can also limit these actions.

## Translated copies [#translated-copies]

The integration creates one copy for every source file and target language. By default, the copy sits next to the source and is named `<source file name> [<target language in the source language>]`.

For example, an English file named `Launch plan` becomes `Launch plan [French]` when translated into French.

For a Spanish source, the same French copy is named `Launch plan [francés]`. If the language name cannot be resolved, the integration uses the target locale code.

Later runs update the same copy. If that copy was deleted or moved to trash, the integration creates a new one the next time it translates the file.

The connected account must be able to create and edit translated copies. If it cannot edit a copy, the integration stops that file and language instead of creating an unrelated duplicate.

## Updating translations [#update-behavior]

- **Apply changes** reuses existing translations where possible and updates the translated copy.
- **Force retranslation** translates from scratch and replaces translated text and layout changes in the copy.

The integration matches content between the current source and the existing copy. For Google Slides, it also tries to add, remove, and reorder whole slides, but structural updates are best-effort. Review the translated copy when you change slides, tables, or other structural content.