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

title: Supported content
description: Learn which Google Drive files General Translation translates and how access and translated copies work. Reference for Google Drive supported content.

---

The Google Drive integration translates native Google Docs and Google Slides files. It reads each source file, sends translatable text to General Translation, and applies the result to a Drive copy for each target locale.

## Overview [#overview]

| Topic                                   | Description                                              |
| --------------------------------------- | -------------------------------------------------------- |
| [Supported file types](#file-types)     | Native Drive files accepted by the integration.          |
| [Access modes](#access-modes)           | Personal-account and Organization shared drive access.   |
| [Dashboard permissions](#permissions)   | Permissions required to connect and run the integration. |
| [Translated copies](#translated-copies) | How locale copies are created and updated.               |
| [Update behaviour](#update-behavior)    | Reuse, force retranslation, and structure changes.       |

## Supported file types [#file-types]

| File type     | MIME type                                  | Supported |
| ------------- | ------------------------------------------ | --------- |
| Google Docs   | `application/vnd.google-apps.document`     | Yes       |
| Google Slides | `application/vnd.google-apps.presentation` | Yes       |

The picker excludes other file types, including Google Sheets, PDFs, Microsoft Office files, images, and folders.

Google Docs translation preserves the document structure while replacing translatable text. Google Slides translation applies text to a copy and runs a background formatting phase for the translated deck.

## Access modes [#access-modes]

| Mode                       | Google scope | Available files                                                                  |
| -------------------------- | ------------ | -------------------------------------------------------------------------------- |
| Personal account           | `drive.file` | Files the user selects with Google Picker and files the integration creates.     |
| Organization shared drives | `drive`      | Shared drives that include the Organization's connected translation account. |

Personal access is granted per user. Disconnecting a personal account removes that user's stored authorisation but does not delete linked files or translated copies.

Organization shared drive access is managed under **Organization > Settings > Integrations** and requires the shared drive feature on the Organization's plan. Projects using this mode do not require each user to connect a personal Google account.

## Dashboard permissions [#permissions]

| Action                          | Required permission          |
| ------------------------------- | ---------------------------- |
| Connect the Project integration | `project:write`              |
| Add or unlink files             | `translations:content:write` |
| Start or force translation      | `translations:content:write` |

All actions are also limited by Project access and plan features.

## Translated copies [#translated-copies]

The integration creates one target copy for each source file and target locale. Its default name is `<source file name> [<target language in the source language>]`. For example, an English source becomes `Launch plan [French]`, while a Spanish source becomes `Launch plan [francés]`. The integration falls back to the target locale code when it cannot resolve a language name.

Later runs resolve the recorded target copy and update it in place. If the copy is trashed or no longer available, the integration creates a replacement on a later successful run.

The active Google account or Organization connection must be able to create the first copy and edit later copies. A permission failure stops that file-locale; it does not silently create a duplicate.

## Update behaviour [#update-behavior]

| Mode                  | Existing translations                        | Target copy                                                                     |
| --------------------- | -------------------------------------------- | ------------------------------------------------------------------------------- |
| **Apply changes**     | Imported and reused where possible.          | Updated in place.                                                               |
| **Force retranslate** | Ignored; content is translated from scratch. | Updated in place; translated content and target layout changes are overwritten. |

The integration maps content between the current source and the existing copy. When their structures differ, it updates the corresponding content. Google Slides also attempts to add, remove and reorder whole slides before applying text; structural updates are best-effort, so review the resulting copy.