Everything you need to fit localization into your stack
Native file formats, a scriptable API, and first-party tooling —
connect transglot to the codebase and pipeline you already have.
20 file formats
JSON (flat and nested), Android XML, iOS .strings/.stringsdict/.xcstrings, Flutter ARB, Laravel PHP and JSON, XLIFF 1.2 and 2.0, gettext .po, YAML, Java .properties, .NET .resx, CSV, XLSX, and Markdown/MDX.
CLI, GitHub Action & MCP
Pull and push from any shell or CI job with the transglot CLI and the first-party GitHub Action — or let an AI agent drive the same API through the @transglot/mcp server.
REST API & webhooks
Project access tokens, publishable keys, a REST API, and signed webhooks across 10 events, with delivery logs and redelivery.
In-context SDK
Drop @transglot/incontext or @transglot/react into your app to edit copy on the live UI, with screenshots for real context.
A marketplace of two-way connectors
Eight CMS connectors, a Figma plugin, and a GitHub App — each authenticates with your own provider credentials and syncs source and reviewed translations both ways.
CMS & commerce connectors
Content sync — each connector signs in with your own provider credentials. WordPress and Contentful are free on any paid plan; the rest, including the Shopify, WooCommerce, Magento and PrestaShop commerce connectors, the Freshdesk and Help Scout help-desk connectors, the Drupal, Kontent.ai, Prismic and Contentstack CMS connectors, the Confluence docs connector and the Mailchimp and Klaviyo marketing connectors, are per-connector add-ons. Most are two-way; Notion, Ghost, BigCommerce, Help Scout, HubSpot, Mailchimp, Prismic, Klaviyo and Confluence are one-way imports today.
WordPress
Localize posts, pages and registered meta both ways, over your own site credentials.
Free on any paid plan.
Contentful
Sync entries and publish reviewed locales back, using your own Contentful token.
Free on any paid plan.
Intercom
Localize your Intercom Help Center articles and collections, two-way.
Zendesk Guide
Translate your Zendesk Guide help-center articles and keep locales in sync.
Sanity
Localize Sanity documents through the Content Lake, per locale.
Storyblok
Translate Storyblok stories and their nested components.
Webflow
Localize Webflow CMS collection items into every site locale.
Strapi
Localize your self-hosted Strapi 5 content, field by field, per locale.
Shopify
Localize Shopify products, collections and pages into every store language, two-way.
WooCommerce
Localize WooCommerce products and categories into every store language, two-way — never touching your native product copy.
Notion
Import Notion database pages — their title and text properties — for translation, using your own integration token.
One-way import today — publish-back is on the roadmap.
DatoCMS
Localize DatoCMS records into every project locale, two-way, using your own API token.
Hygraph
Localize Hygraph (GraphCMS) content over GraphQL into every locale, two-way, using your own Permanent Auth Token.
Ghost
Import Ghost posts and pages — their title and plaintext — for translation, using your own Admin API key.
One-way import — Ghost posts are monolingual, so there is no publish-back.
Magento
Localize Magento (Adobe Commerce) product copy into every store view, two-way — writing only the target store-view scope, using your own integration token.
BigCommerce
Import BigCommerce product name and description for translation, using your own store API token.
One-way import today — the native multi-language write API is beta and Catalyst-only, so publish-back is on the roadmap.
Freshdesk
Localize Freshdesk solution articles into every language, two-way — writing only the target-language translated article, never the primary, using your own API key.
Help Scout
Import Help Scout Docs articles — their name and text — for translation, using your own Docs API key.
One-way import — Help Scout Docs models each language as a separate site, so there is no publish-back.
HubSpot
Import HubSpot blog post title and body for translation, using your own private-app token.
One-way import today — the per-language write path is a create-variation + patch dance on a published blog, so publish-back is on the roadmap.
App Store Connect
Localize your App Store listing — name, subtitle, description, keywords, promo text and release notes — per market, two-way, using your own App Store Connect key.
Google Play
Localize your Google Play listing — title, short and full description — per market, two-way, using your own service account.
Google Drive
Pull source localization files from a Google Drive folder, translate them, and write the target-locale files back — over your own Google account.
Manual sync today (scheduled sync is on the roadmap); narrow drive.file scope, so we only touch files the app creates or opens.
Dropbox
Pull source localization files from a Dropbox folder, translate them, and write the target-locale files back — over your own Dropbox account.
Manual sync today (scheduled sync is on the roadmap); we write only the target-locale files, never your source.
Amazon S3
Pull source localization files from an S3 bucket prefix, translate them, and write the target-locale objects back — with your own IAM key, signed with AWS Signature V4.
Manual sync today (scheduled sync is on the roadmap); we write only the target-locale objects, never your source.
Drupal
Localize Drupal content (nodes) into every language over JSON:API, two-way — writing only each target-language translation, never the source, using your own site login.
The target-language translation must already exist in Drupal — JSON:API can update a translation but not create one.
Mailchimp
Import Mailchimp campaign subject, preview and content for translation, using your own API key.
One-way import — a Mailchimp campaign is single-language, so there is no publish-back.
Prismic
Import Prismic documents’ text fields for translation, using your own access token.
One-way import — the Content API is read-only and the Migration API cannot set an existing document’s alternate language, so there is no publish-back.
Kontent.ai
Localize Kontent.ai content into every language variant over the Management API, two-way, using your own MAPI key — upserting only each target-language variant, never the source.
PrestaShop
Localize PrestaShop product and category copy into every store language, two-way — writing only the target-language field node, never the source, using your own webservice key.
Contentstack
Localize Contentstack entries into every locale over the Management API, two-way, using your own management token — writing only each target-locale entry, never the source.
Klaviyo
Import Klaviyo email template name and html/text for translation, using your own private API key.
One-way import — a Klaviyo template is single-language, so there is no publish-back.
Confluence
Import Confluence page title and body for translation, using your own email + API token.
One-way import — Confluence has no native per-page translation, so there is no publish-back.
Design
Localize the source of truth for your copy before it ever reaches code — from Figma, Sketch or Adobe XD.
Figma
Push text layers to transglot and pull translations back into Variables and modes.
Plugin — a Figma Community listing is on the way.
Sketch
Push selected Sketch text layers to transglot and pull the translations back onto the layers.
Plugin — not yet on the Sketch directory.
Adobe XD
Push Adobe XD text nodes to transglot and pull the translations back from a panel.
Plugin — Adobe XD is in maintenance mode; not on the Adobe marketplace.
Developer
Wire localization straight into the way you ship.
GitHub App
Continuous localization: extract strings on push and open a pull request with the translations.
Self-host or register the App to enable it.
Automation
Trigger Zapier, Make or n8n flows from transglot events, and drive transglot back over the REST API.
Connect over signed webhooks + the API today; dedicated Zapier/Make/n8n apps are on the way.
Jira
Open a Jira Cloud issue when a translation needs review or a source edit needs attention.
One-way (transglot → Jira); needs your own Jira API token. Free on the Team plan.
GitLab
Continuous localization for GitLab: on push, extract source strings, translate, and open a merge request.
GitLab.com (SaaS) only; push→MR today, no /translate command yet. Free on the Team plan.
Bitbucket
Continuous localization for Bitbucket: on push, extract source strings, translate, and open a pull request.
Bitbucket Cloud only; push→PR today, no comment-command yet. Free on the Team plan.
Azure Repos
Continuous localization for Azure Repos: on push, extract source strings, translate, and open a pull request.
Azure DevOps Services only; push→PR today, no comment-command yet. Free on the Team plan.
Localization that fits your workflow
transglot plugs into the way your team already builds and ships — from the terminal, from CI, or from the editor.
For developers
- Pull and push strings from CI with the CLI or the GitHub Action
- A REST API, project access tokens, and signed webhooks across 10 events
- An MCP server — 15 tools 1:1 over the REST API, so your AI agent can drive localization
- OTA / CDN runtime delivery — fix a prod string without a redeploy
- 20 native file formats, round-tripped losslessly
For localization managers
- Keys, locales, and a review workflow with per-reviewer attribution
- Glossary enforcement with AI candidate extraction and import/export
For agencies & studios
- Per-project style guides and brand voice for every client
- Scoped project access tokens and publishable keys, project by project
Your entire stack — one source of truth
Push and pull strings over a REST API, the transglot CLI, a first-party GitHub Action, or an MCP server your AI agent can call — round-trip twenty native file formats, from i18next JSON to Android XML to XLIFF, and deliver fixes at runtime over the CDN.
