New Sanity.io Integration: Launch Multilingual Content Directly from your CMS

Global campaigns move fast, but localization workflows rarely keep up. Moving content between your CMS and translation tools creates delays, formatting issues, and version control risks that slow everything down.
The new Sanity.io integration with Smartcat connects your CMS directly to your localization workflow, so content moves from creation to translation to publishing without manual handoffs.
Why this matters
Marketing and content teams are under pressure to launch in every market at once. But when localization happens outside the CMS, it becomes a bottleneck.
This integration removes that bottleneck by bringing translation into the same workflow where content already lives—so teams can move faster without adding complexity.
What you can do now
Push content to translation without leaving Sanity
Send structured content directly from Sanity to Smartcat, eliminating manual exports and reducing coordination overhead.
Sync translations back automatically
Completed translations flow back into Sanity, ready to publish—no copy-paste, no reformatting, no delays.
Automate workflows at scale
Set up rules to automatically send new or updated content for translation and return it when ready. This keeps content continuously up to date across languages.
Publish faster with fewer errors
Structured content transfers cleanly between systems, reducing formatting issues and rework that slow teams down.
Optional auto-publish
Automatically publish translated content in Sanity as soon as it’s ready, removing extra steps from your content ops process.
How it fits into Smartcat
Smartcat connects content creation, translation, and publishing into one workflow powered by expert-enabled AI Agents. Instead of managing disconnected tools and manual processes, teams can create and launch multilingual content simultaneously—ready for every market from day one.
Here is how to set it up:
Create API key for the Sanity project with Editor permissions.
Set up Locale Mapping between Smartcat and Sanity:
Use locale codes from Sanity, e.g.
en-gbSelect Smartcat Language. It defines how Sanity language will be treated in the translation workflows.
Need help? Book a demo with our forward deployed team.
Who this is for
Marketing teams managing global campaigns
Content operations teams scaling multilingual publishing
Localization managers reducing manual workflows
Web teams responsible for keeping content current across regions