# General Translation Integrations: Translating content
URL: https://generaltranslation.com/en-GB/docs/integrations/storyblok/guides/translating-content.mdx
---

title: Translating content
description: How to translate Storyblok stories from the General Translation Dashboard and review the results summary.
related:
  links:
    - /docs/integrations/storyblok/guides/managing-translations
    - /docs/integrations/storyblok/guides/using-translated-content
    - /docs/integrations/storyblok/guides/configuring-storyblok

---

Use the Storyblok integration's management page to translate stories into your target locales. General Translation reads each story's draft, translates the supported fields, and writes the results back into the story as a draft.

## Select stories and locales [#select-stories]

Open the integration from **Project > Integrations**, then:

1. Choose one or more entries in the **Story** selector. It is searchable and supports select all and select none. Stories are labelled with their full slug.
2. Set the **Source locale**. It defaults to your Project's default locale.
3. Confirm the **Target locales**. They default to the space's configured languages that map to supported General Translation locales, excluding the source locale. Remove or add locales as needed.

You must select at least one story and one target locale before **Sync and apply** is enabled.

## Auto-enable supported fields [#auto-enable]

Storyblok only stores a field-level translation when the field is marked `translatable: true` in its component schema. Tick **Auto-enable supported fields** to have General Translation mark supported `text`, `textarea`, `markdown`, `richtext`, and `table` fields as translatable before syncing.

Leave it unticked if you have already enabled those fields in Storyblok. See [Configure Storyblok](/docs/integrations/storyblok/guides/configuring-storyblok#enable-fields).

## Run Sync and apply [#sync-apply]

Click **Sync and apply**. For each selected story and target locale, General Translation:

1. Reads the story's draft content and extracts translatable fields.
2. Queues translation jobs and polls until they finish.
3. Merges the completed translations back into the story.
4. Writes the merged content back to Storyblok as a draft. Nothing is published automatically.

Existing translations are imported during the run, so previously translated values are reused instead of being translated again. See [Managing translations](/docs/integrations/storyblok/guides/managing-translations).

## Read the results summary [#results-summary]

When the run finishes, the management page shows a summary. Depending on the run, it may include:

* **Succeeded** and **Failed** counts.
* The **Story** and the number of **Fields** extracted.
* **Skipped** field count.
* **Jobs**, **Target locales**, and **Stories** counts.
* **Enabled fields** and **Updated components** (when **Auto-enable supported fields** was ticked).
* **Draft writes** (previewed) and **Applied writes** (written back to Storyblok).
* A grouped **Skipped fields** list.

## Understand skipped fields [#skipped-fields]

A field is skipped when it cannot be translated. The summary groups skipped fields by component, field, type, and reason. The reasons are:

* `missing_component_schema` — the block's component has no schema the integration could read.
* `unsupported_field_type` — the field type is not translatable (for example, an asset or link).
* `non_string_value` — the field's value is not in the format the type expects (for example, a `richtext` field that is not a rich text document).
* `missing_nested_component` — a nested `bloks` item is not a valid component.

For the full list of translatable types and skip reasons, see [Supported content](/docs/integrations/storyblok/reference/supported-content).
## Next steps

- /docs/integrations/storyblok/guides/managing-translations
- /docs/integrations/storyblok/guides/using-translated-content
- /docs/integrations/storyblok/guides/configuring-storyblok