Installation and upgrading

To initiate a new Studio without installing the CLI globally:

npm create sanity@latest

To upgrade a v3 Studio, run this command in its folder:

npm install sanity@latest

The Translate the studio UI #1603 issue has been one of our most popular feature requests on GitHub. Now we can finally close it, because we have launched Studio UI localization.

• Multilingual support: You can now configure the Sanity Studio user interface to use languages other than English. We're starting with many languages, including Spanish, French, Norwegian, German, Portuguese, Korean, Turkish, Icelandic, Thai, Vietnamese, Swedish, Finnish, Czech, Italian, Japanese, Chinese, and Polish. Don’t see your preferred language? It's easy to request additional language plugins!
• AI-Translated language plugins: These initial translations are generated by AI — we're inviting the community (that’s you!) to help us improve and maintain these translations for accuracy and cultural relevance. Interested? Read more about how to contribute over on GitHub.

This is our first step towards a fully global studio. The support for localization will grow, starting with our official plugins. We appreciate your patience and contributions as we expand these capabilities!

• Choose your language: Visit github.com/sanity-io/locales to find the plugin for your desired language. If it's not listed, we’d love you to request it - we can do a first auto-translated pass, and you can help us review and improve the automated translations.
• Plugin setup:
  • Ensure you are using Sanity version 3.22.0 or newer
  • Install the plugin for your desired language (npm install @sanity/locale-nb-no)
  • Import it (import {nbNOLocale} from @sanity/locale-nb-no
  • Add it to your studio's plugins array (plugins: [nbNOLocale()])
  • You’ll find full instructions on the locale plugin’s README!
• Documentation:
  • How to localize the Studio UI
  • How to internationalize a plugin

We're eager to hear from you and welcome any feedback. This is just the beginning, and your insights are invaluable in making Sanity Studio even better.

As a product company, we have to prioritize what to work on. Ideally, those decisions are based on a healthy amount of vision (how we think things could be better) and insight (how people use the product). We have had a good amount of the former but less of the latter.

With this release, we’re introducing telemetry data collection in the CLI and Studio. Participation is optional, and you can easily opt-out by running npx sanity telemetry disable, setting the DO_NOT_TRACK=1 environment variable, or visiting Account Settings in Manage. For more details on what data is collected, how it’s being used, and how consent is handled, go to sanity.io/telemetry.

• Adds experimental support for using Bun as package manager when creating new Sanity projects (bun create sanity)
• Adds the ability to customize the suffix added to auto-generated GraphQL filter types (Filter by default), by configuring filterSuffix in the GraphQL configuration of sanity.cli.ts

• Fixes issue where annotation popover would open in the wrong location when selecting annotation text in the Portable Text editor
• Fixes removal of marks in the Portable Text editor, not always cleaning up unused mark definitions
• Fixes issue where Portable Text editor would crash when attempting to use annotations on text over multiple blocks
• Fixes issue in which new empty text blocks were added when adding a non-text block in the Portable Text editor
• Fixes an issue where selecting a custom API version in the Vision tool would sometimes crash