Sanity Reviews: 4.7/5 — Highly Rated

Sanity's UI is very user-friendly. The ability to drag and drop and schedule content has been incredibly helpful to our content marketers

As of now we haven't created a way to easily export dev data to a production environment. Likely just a us not being mature enough with our implementation to date.

We've never been able to schedule content with our previous content management systems. Something so simple is so helpful!

* Fetch content fast from Sanity API through CDN. * Flexible content portal. Can expand outside what it offers with React components. * Fast and helpful support from the Sanity team.

* Bugs might take time to fix when brought up to the Sanity team.

It mostly great for fetching content fast from different regions and having a flexible content portal.

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.

Sanity is incredibly flexible. The developers in our team have created many custom components that allow me, as a Content Editor, to use Sanity Studio relatively easily to build highly complex forms with complicated logic fast without the help of a developer. Sanity is so flexible that we so far always have succeeded in doing exactly what we need to, even when that is creating extremely complex content and functionality.

There is not much to dislike about Sanity, but our team has started to worry about the hard technical limit restraining how many unique attribute paths the data structure can contain. As we have created very complex data structures and keep adding new complexities, we are moving ever closer to this hard limit. And we still don't know how to solve this problem.

For our governmental organisation, using Sanity has given us much more control over our own forms and all changes go a lot faster than previously. This is a new experience for us. Before, even relatively small changes had to be ordered from external developer consultants and took weeks to get implemented, but now I have full control of all content and functionality in our forms myself, so I can easily and quickly change texts or rebuild the forms as I see fit without asking any developers for help.

The GROQ query language is both easy to use and flexible. Portable Text (Sanity's version of a rich text field) is lovely to work with, allowing easy editor experiences. The free tier is also substantial enough for most testing and evaluation.

I would prefer not to need to use React to create custom input fields; however, this is a minor complaint. There are also occasional glitches and slowdowns in the Studio editor.

Allowing clients to edit the content for their websites. Sanity enables me to create a customised editor that feels personal to the client's project. It also allows me to use different approaches for different clients (e.g. a full page-builder for one and a stricter schema for another).

The simplicity of creating the API. And don't have to worry about migrating data when I change my frontend later.

Connecting one data to another and Relationship building needs to be simple. At-least for me as a beginner.

I no longer worry about data base maintenance and architecture. I lost many data in the past due to the complexity.

Portable Text - that is what i really like, i can add a new button and link any entry i want groq - more power than graphql. Can use as simply as possible or build complex queries. Feels like you have complete control with the build-in API. Studio aka Admin panel - simple spa, so we can host studio with different datasets. One for QA, one for stage, one for prod and etc. slack community

groq - more power - more handwriting (ts types) studio ui - different than other admin panels. Not a big problem, but some clients may be confused no special video field, only common file or image

Build a comfortable, stable admin panel for clients to work as Headless CMS with nextjs. Because content is based on schema files, we can reuse some parts between projects.

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

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.

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.

Excellent documentation and ease of set up.

It can be a bit slow and tedious in the actual CMS editor portion, though that could be the way I've set it up.

Gap I felt existed for people who didn't need a full on CMS but needed some flexibility in terms of adding content.

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 easy to scaffold a site and deploy it to Vercel or Netlify so you can start building immediately. Sanity studio (cms admin) is easy to use. File-based routing and defining content types in json mean you can model, create and view your content quickly. The docs are detailed and easy to follow.

You can't self-host the content/database - not a big deal for most use cases. The previews are a really strong feature but they are difficult to manage if you are using reference types - like a page composed of other components with separate content

I use sanity with NextJS on Vercel to build client websites. In the end, the client has a super fast site with a CMS admin they can master in an afternoon. I'm looking forward to trying a similar approach with Sanity and Astro

The best part of choosing Sanity as our CRM has been the super in-depth support from the dedicated Slack and the forum. So many members are eager to help each other solve complex problems there.

There is a learning curve with GROQ, like any new language. Maybe the startup-docs could be a little better. I'd love to see more in-depth tutorials like the one where SuperRooster migrated from WP to Sanity.

The whole studio and backend are intuitive and easy to work with. This makes managing content and creating custom layouts more efficient than the alternatives. Its also sleek, which is probably good for dev headspace!

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.

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.

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 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.

Sanity provides you with easy database management and creation of schemas in a simplied way which makes the work a lot easier even if you are just starting with this platform.

I didn't felt any such downside to dislike. My experience with using Sanity in my project was great. Most importantly, how easy it's to query over the database.

I was working over a project where I need to deal with images in a categorically organized way and that's where Sanity played a big role in solving my problem in much simplified way.

I decided to try Sanity for a personal project. I found it quick and easy to set up and customize for my needs. The realtime previews are great while editing.

The documentation could be improved upon.

I was interested in finding a CMS to integrate with my React project. I enjoyed the flexibility and ease of use to quickly build out my app.

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.

Solid well thought out product, good UI with the flexibility to build nearly any data structure. GROQ queries are very powerful

i18n is serviceable but needs some polish

Creating a bespoke CMS's that is simple for content managers to use and understand

The community is very accessible and transparent. It is easy to get answers the same day you have issues using the sanity slack. Sanity offers a lot of flexibility and has a feature set that is growing all the time. They seem to prioritize the development of these features based on community feedback, including the recent release of in-place creation of referenced documents.

The documentation, while mostly complete and easy to understand, is difficult to search against. This makes discovery via the docs alone tedious and unreliable.

We are building out large client sites that comprise both structured and editorial, page-builder content, using a combination of next.js and sanity and hosting on netlify.

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

The fact that I have a visual representation of the data.

The prices are not that favourable for people who are in third world countries like me. Maybe come up with a package that caters for us.

Mostly managing blogs is easy and also data using their schema. It is really nice

Sanity gives you the best DX of alle CMS I have worked with. As a frontend devolper its so easy to customize and optimize the studio for the authors. Creating new schemas is a simple as writing a few lines of JSON. The developer documentation has also been very helpful and if you cant find it there, just ask on the slack communiry.

Outdated depencies, no React 18 support yet. Snd that you cant translate the studio YET. There is a big chance authors will experience som input lag on more complex schemas.

Multiplatform, web and mobile. No need for complicated backend and infrastrcture. No need to create a lot small tools for the authors for image optimization, sanity does it for you.