# General Translation Integrations: Translating content
URL: https://generaltranslation.com/en-GB/docs/integrations/payload/guides/translating-content.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: How to translate localised Payload CMS fields for one document, a global, or the whole site.

Use the plugin controls in the Payload admin panel to translate text into the target locales from your Payload config. You can translate a single document or global, or start one run for every supported item.

## Before you start [#before-start]

Complete the [Quickstart](/docs/integrations/payload/quickstart), then save the source content you want to translate. The translation controls follow the signed-in user's Payload access rules.

## Translate one document [#translate-one]

1. Open a document or global with localised fields.
2. Save any pending changes.
3. Choose **Translate** to open the **Translations** drawer.
4. Select the target locales.
5. Choose **Translate into …**.

The button is unavailable while the form has unsaved changes. The plugin reads the default locale as the source and excludes it from the target list.

Each document appears in General Translation under its Payload identity. Collections use `collection/id`; globals use their slug. Changing a document title does not change this identity.

## Translate the whole site [#translate-site]

1. Open **Translations** from the Payload admin navigation.
2. Select the target locales.
3. Choose **Translate into …**.

The site-wide run includes every collection document and global with supported localised content. Payload's own internal collections are excluded. The coverage table shows which locales currently contain text for each item.

The plugin processes each document independently. A failure in one document or locale does not discard translations that completed successfully.

## Choose target locales [#target-locales]

The plugin lists every configured Payload locale except the default locale. A locale is available only when General Translation recognises its code or [`customMapping`](/docs/integrations/payload/reference/plugin-configuration#custom-mapping) maps it to a supported code.

Locale selection is remembered for each Payload user. Unsupported codes remain visible in the admin panel but cannot be selected for translation.

## Review the result [#review-result]

The plugin writes translated values into the corresponding Payload locale:

* Collections and globals with drafts enabled receive a draft.
* Content without drafts is saved directly.
* The plugin never publishes.

Review each locale through Payload's normal editing and publishing workflow. See [Supported content](/docs/integrations/payload/reference/supported-content) for field behaviour, exclusions and character limits.

## Next steps

- /docs/integrations/payload/guides/managing-translations

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.