Sanity Reviews & Product Details

Clear ways of displaying data and navigating the studio console

There's a small bit of learning curve up front -- teams should make sure to go through the training, especially for developers. But the time investment is worth it (so not really a negative)

Sanity enables our business and content teams to create new content and experiences while still having design-driven templates that are enforced with rules and guardrails

Converting an object relation diagram into schemas and associations is intuitive and straightforward. Another nice feature of Sanity is the ability to use GROQ for multiple tasks: roles and permissions, data import and querying.

Localization takes a bit of time to get configured with plugin(s) but is easy to work with afterward. The Vision Plugin for Sanity has been incredibly helpful for debugging and testing during the localization process.

Sanity is helping us streamline our content creation flows across multiple, Headless Shopify Stores and truly allowing content authors to preview their content before publishing.

I enjoy the customization aspects of Sanity. I love that you can create components and use custom serializers to interpret input within your code. I also enjoy being able to create custom actions within the Desk tool.

Integration between different environments could be better. For instance, we have a development and production environment that are mirrored. It would be great to copy a document from one domain to another without copying and pasting.

Sanity helps the devs in our workspace spend less time updating content and more time working on new technologies. We often have marketing asking us for changes, and we have begun to point them to Sanity so that they can make them without having to relay the information through multiple other teams.

Easy setup and out-of-the-box hosting without configuration of database or anything. Also, synchronizing data between development and production is very nice.

It would be beneficial if you could have secured documents (or, better also secret Fields) in a dataset to store secret information without exposing them publicly. Also, Backups are not easy to set up, the GitHub action plugin is full of bugs and does not work very well.

The biggest benefit for me and our company is, to have a cms that I don't need to write complete from zero but still have the possibility to make it custom and look like we wrote it only for our needs.

Sanity is super easy to set up and customize; and allows you to collaborate easily with people who don't need to understand the code part of development

I guess a downside is that I won't get to try other content systems since I reach for sanity every time

The Fast and easy set up as well as amazing documentation at super helpful for devs like me who freelance and don't have a content team

I like that it's very flexible in defining the structures for your content and that it can be hosted in Sanity Studio online without needing to spin up my own server.

The user interface seems a little boxy to me. But I guess that can be changed with custom CSS.

It's allowing me to add custom content to my products from my Shopify store.

I like that Sanity allows you to model your content using JSON, and extend the cms with react. The editor interface, as well as the backend database and API is automatically generated from your schema. The Sanity client, CLI and Groq query language are all super nice to use. The community support in the Sanity Slack channel is awesome too!

One possible downside of using Sanity is that the database is a database as a service. Database admin folks may want more control. Although the studio is open source, there is a degree of vendor lock in because you have to use the hosted database as a service out of the box.

Sanity makes it easy for developers to implement a custom CMS explicitly designed for the content editing team's needs. It allows you to consume your content as data in multiple places, such as websites and mobile apps. You could even give a third-party read access to your api. As a small team, deploying a CMS and database quickly without worrying about managing a server yourself is a huge productivity boost.

It's great that you can start from a blank canvas or re-use a previous studio to tailor your needs on a project-by-project basis to create a bespoke experience.

When creating your desk structure, it is hard to understand the documentation as to what each setting does, especially with how nested your panels become and the need to use 'intent'. Perhaps providing more graphics to show examples would make this easier to work with.

Coming from WordPress and working with React, it's excellent not to need a server to maintain and to be able to build any features you need into the studio itself.

Sanity makes it easy for our team to combine simple data structures into very complex ones at a rapid pace. Sanity Studio is relatively easy to customize to our needs by writing custom components. They have a Slack community setup which makes it easy to ask for help and meet other users of Sanity.

All in all, I don't have many complaints about Sanity as a product. There is a limitation in the product itself, which is troublesome for our team because of the complex structures we are creating. Each pricing plan has a hard technical limit restraining how many unique attribute paths the data structure can contain. We are a bit too close for comfort in reaching this limit and are struggling to figure out how to stay within the required limits long-term. This may be a deal-breaker in the future. We are on the previous version of Sanity, so this might have changed in the newest version, but the built-in TypeScript support is minimal, requiring us to mostly write all the types manually by hand.

The complex data structures we create with Sanity are later interpreted by our frontend code, autogenerating an entire website where users fill in Forms or Applications with extremely complex logic behind the scenes. All of this logic is also created by extending the Sanity Studio experience. Creating an "admin"-like interface like this from scratch would require a lot of work, but Sanity allows us to move forward quickly, and it is easy to customize to our needs.

Easy to get started with schemas and content. No need to setup your own server, database, cdn. Very helpful and nice community and employees makes asking questions a nice experience.

Would like more fine-grained control over permissions, for instance some private documents in the same database. The groq syntax can get messy when I use references, for instance I use internal links several places and I feel I have to nest in far to get it working. The studio feels sluggish at times. I've had some problems creating custom plugins, and I feel the documentation is a bit lacking in that part. Might be better in v3 though.

Hosting data for my websites, both professional and personal. Easy to get up and running because I don't have to set up a server etc. Easy to collaborate with others about the content.

The customisation process of Sanity is so easy and fast. I also love that images can be stored and cropped/hotspotted in Sanity, so we don't need a different platform to host all our images on. Once you get the hang of Sanity and how to build schema's, it's pretty easy to create custom objects and even your own modules. The coworkers that use it for data entry all say it is very easy to use and publish.

Typescript still has a bit of teething issues, but it has come a long way in the last couple of weeks. The biggest downside to me is the customer service in regards to questions. With the Github discussions and Sanity Slackm you would assume that questions are answered really quickly, but it takes a long time before I get an answer, if I get an answer at all.

We use Sanity for multiple websites. The fact that it is so easy to set up makes the life of a developer so much nicer. The open source aspect of Sanity makes it really interesting, because it is always growing and changing with new plugins.

The flexibility Sanity offers by writing schemas and combining it with custom components when needed. This flexibility is quite important when working with customers that doesn't always know what they want up front.

It's not a dislike, but I do think that some additional documentation is needed, especially for groq syntax and perhaps more real word examples on how to use groq queries with complex schemas.

Again, I think the flexibility you get by approaching the Studio config/setup, like developing an app rather than making do with a more pre-defined structure found in competing products. Also, I like the power you get by using groq, even if it's a bit confusing initially.

I think the flow of how items are built up makes sense and it is rather straightforward.

It would be nice if there was better training guides on how to pull data from sanity using GROQ. I didn't find the documentation incredibly helpful.

It is providing a great content management tool.

The customization and control you have as a developer, as well as the overall developer experience.

Asset support, I wish there was a better way of handling media (especially video) than to have to rely on external services (like MUX) which adds complexity and cost.

Internal product solutions. Sanity helps streamline the process while making it enjoyable to work. I've be found that setup for new project is a little slower but well worth it in the end.

Sanity has amazing documentation that is easy to understand!

Some of the plugins that you can install from the Sanity website conflict and make upgrades difficult.

It is helping our company to manage our content and provides a easy interface for our users.

Ease of implementation, highly customizable and incredible community.

Nothing major so far, the experience has been really good.

Ability to answer customer's customization requests and ease of use.

The best about sanity is managing the content as you want, so flexible.

Nothing, for now, everything is good and I like it

Managing content, easy creation, flexible schema, excellent performance

I like it because it is very schematic, which means it is easy to understand and write.

Sometimes being too schematic can result in being a little rigid. It can result in very long, nested files

Giving access to modify pages to no devs less workload for us and more efficiency in updating soma data

Being able to structure our content in the way we need. It gives us the flexibility of a database without having to maintain one. This allows almost infinite flexibility.

Like any CMS, it takes time to learn the ropes and how things work together. The flexibility brings complexity and maintenance, which is the trade-off you need to accept.

Currently, using it to power an online magazine. I love being able to maintain all aspects of the site from the articles to items in the shop. You can use it as a one-stop shop.

Editing my website has become extremely easy

I wish there was more creative control on my website

I've solved the ability to edit my website without having to use a complex backend