Skip to content

Optional analytics, session recording and advertising stay off unless you accept. You can reject them and use Transglot. Change your choice anytime in Cookie preferences. Cookie Policy

All integrations
spec sheet · stores & files

Amazon S3 and Transglot, deliver locale files to your bucket.

Add bucket-scoped credentials, choose your file paths, and save the locale mapping. Sync source files and write translated locale files back under your configured Amazon S3 prefix.

Locale files in both directions
Direction
Locale files in both directions
Plan
Starter and up
Scope
locale objects under one bucket prefix, in any supported format
Authentication
an IAM access key and secret, plus the region, bucket and prefix
Get started
Connect from your workspace’s integration settings.
stores & files
the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

  1. Connect your storage

    Open your workspace’s Amazon S3 integration and select the Transglot project.

    connect
  2. Map files and locales

    Add an IAM access key and secret scoped to the required bucket prefix, then set the region, bucket, prefix and locale-file mapping.

    files
  3. Start a sync

    Use Sync now to read source files and process translations for the mapped target locales.

    sync
  4. Check the written files

    Start Sync now. Read the run result, then check the target-locale objects under your configured prefix.

    deliver
Target-locale files or objects are written to the destination paths you configure.
what moves

What you can translate and deliver.

Point it at a bucket and key prefix. The source object is downloaded and parsed, pushed into the project, and each target locale is written back under the prefix. Writes are plain overwrites, so a rerun that changes nothing costs nothing.
What you can translate and deliver.
SurfaceWhat to expect
Source and scope

locale objects under one bucket prefix, in any supported format

Translated output

Target-locale files or objects are written to the destination paths you configure.

Keep in mind

Sync runs are started manually from the workspace. The connector works within the configured folder or bucket prefix.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

an IAM access key and secret, plus the region, bucket and prefix.

  • A Transglot project with its source and target locales configured.
  • Save credentials in the connection settings so your team can work without copying secrets between files.
  • Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.
  1. Open your workspace’s Amazon S3 integration and select the Transglot project.

  2. Add an IAM access key and secret scoped to the required bucket prefix, then set the region, bucket, prefix and locale-file mapping.

  3. Start Sync now. Read the run result, then check the target-locale objects under your configured prefix.

same project, more possibilities

Connect the rest of your workflow.

Your translations stay in one project as they move between tools.

works with what you already run

41 connectors, already built.

bring your workflow

Your content, ready for every locale.

Connect your tools, translate with your team, and publish reviewed content.