
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeThe @sanity/components package was part of Sanity Studio v2 and has been deprecated. It's no longer actively maintained or documented, as it was part of the old "Parts system" that was removed when Studio v3 was released.
For Studio v3 and beyond, you should use @sanity/ui instead. This is the modern UI component library that powers Sanity Studio and is what you should use for building custom components, plugins, and studio customizations.
The @sanity/ui documentation includes:
When Sanity Studio v3 launched, they deprecated the Parts system (which included @sanity/components and the part:@sanity/components/* imports). The v3 architecture simplified customization by consolidating everything into the single sanity npm package and using standard ES module imports instead of the Parts system.
If you're working with an older Studio v2 project, the @sanity/components package may still be in your node_modules, but official documentation for it is no longer maintained. You can find some legacy references in the Sanity v2 recipes, but the recommendation is to migrate to Studio v3 to access current documentation and support.
For any custom UI work going forward, start with @sanity/ui and the custom component documentation.
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
Content operations
Content backend


The only platform powering content operations
By Industry


Tecovas strengthens their customer connections
Build and Share

Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag store