Butter CMS Reviews: 4.7/5 — Highly Rated

Butter has a lot of potential to take the CMS market by storm. The platform is very versatile and powerful, but the team at Butter is what makes it great. They are responsive and very committed to making their product great and are always making sure their clients have the best experience by making continual improvements and actually listening to customer needs.

It's excellent for developers but not the greatest for designers. There is no WYSIWYG integration and code can often be trickier to implement than it should be. Though there are workarounds, it feels like there are some missing tools that could make the process smoother.

Butter has given us the ability to leverage aspects of our online presence that we struggled with before. For example, we have developed a much more robust UI experience by leveraging components for stronger customer traction.

Support is fantastic! The response time is very quick and helpful. The tools are easy to use.

We have had to make some adjustments to caching issues so we can force pulling new content sometimes.

They make it easy for our markets to translate content on our site in their own languages.

ButterCMS is endlessly configurable. Over the past year, our team of engineers has developed dozens of custom components within Butter to support a variety of user experiences and interface options. In addition, our business users have quickly learned how to use the tool and set up countless web pages with little to no development support required.

There are some quirks to the tool that can result in users having to duplicate efforts across multiple pages. For example, it is not as easy as you'd think to clone a page and make small variations for other versions of that page. Sometimes it requires you to rebuild elements of the page again instead of just leveraging what you already have. Not having a live preview of your changes to the UI can also require several rounds of publishing / republishing to get right.

ButterCMS has been a game-changer for our business. Rather than relying on developers to make all site changes, this tool has empowered our business users to more fully own site merchandising.

As an engineering leader, I'm most concerned about the technical effort required to implement tools. Butter was dead-simple - set it up, grab the API key, and call their endpoints when needed.

The only tricky thing was a minor issue; we wanted to be able to filter/search all of our posts/content or grab all of the headers so we could display a "home page" for our blog, but they didn't have that ability at the time. It might have been implemented since, but it was performant enough to load all of our content simultaneously.

If you're looking for a simple, lightweight, cost-effective CRM for a small-medium size business, Butter is it. We tried a few others and they were either way too heavy/complicated or didn't have basic features.

ButterCMS is an easy to use (headless) CMS system. In a very short period, you can set up a complete site. Very good documentation. Very helpful and friendly support.

Understanding the difference between the different subscriptions was not straightforward.

We needed a short-to-market headless cms system for our mobile app.

Butter CMS is very easy to use the built-in API client make calling the API a breeze. As an architect, butter cms gives me more flexibility to use the cms as in ways that can not be used in a traditional CMS like WordPress. A good example is hybrid apps, we let parts of the website to be updated by butter (ie. button names, heading, wording for a page) this allows our business to do a change without any downtime to our clients. Also, Butter CMS allows us to build very reusable view components that can be added to the website without coding, just some very simple configuration on our end.

*Not dislike or deal-breakers but my wish-list that I believe would take ButterCMS to the next level* The write API if very lacking and not part of ButterCMS API Client, and documentation is not there yet(if you understand API shouldn't be a trouble for you). We were able to get things to work, but it was a lot of frustration at times. Repeater needs to be able to have repeaters a list of lists of lists of objects. If you think of Components as objects and Repeaters as List then you will understand why a user would want of list of objects or a list of lists. These two above make it hard to create things like dynamic tables, or questionnaires. The references tool is too much clicking, especially for non-technical people. a good example. I want a repeater that has a component in it <- this is powerful, that can be used to make a table, or layouts, because now you have a List<T>, ICollection<T>. This is very important to a dev to make very dynamic content. -Below are nice to have- Needs a built-in Site Map component. Needs a built-in Navigation component. Needs SEO for pages, just like how the Blog works (it's very useful). Write API for the ButterCMS Client. Still Good Work.

A good example is hybrid apps, we let parts of the website to be updated by butter (ie. button names, heading, wording for a page) this allows our business to do a change without any downtime to our clients. Also, Butter CMS allows us to build very reusable view components that can be added to the website without coding, just some very simple configuration on our end.

The UI is quite intuitive, clear, and neat. Customer support is beneficial and friendly. APIs such as 'write' and 'image' are helpful. The preview feature is pretty cool. There was a solution for every feature we wanted to implement.

Butter CMS is alright in every way. Having a root preview URL without slugs is something that can be nice.

Easy content management with control of meta description and SEO. Managing icons from one source. Having a preview of the data before actually integrating it.

As a developer, working with a headless CMS has been great. I haven't had any issues with performance or reliability, and customer service has been incredibly helpful.

There are a few additional features that would be nice, but in my experience with a few other CMS options, Butter isn't behind the times at all.

We have multiple places on our site that require somewhat frequent content changes. These would be a pain in the butt for me, as a developer, to maintain. With Butter, I was able to set up those pages so that my non-tech team can be in complete control of the content.

It's a simple and quick way to share blog entries! My favorite feature of ButterCMS is the ability to schedule posts so that I can remain on top of all of my responsibilities. ButterCMS' ability to schedule out content allows me to plan ahead for future content.

ButterCMS has a lot of excellent features, however one thing I'd want to have modified is the font sizes of header 1 and header 2 so they don't seem so similar once the blog is published. When I'm reading posts all day, it's often difficult for me to recognize the difference between the headers because the sizes are so similar aesthetically.

We can publish high-quality blog content on our website, and ButterCMS allows us to make our blogs look professional and well-organized, with no visual difficulties.

If you want to create content that looks good, fast, Butter is for you. If you produce a lot of articles, formatting and designing each one is laborious and wastes a lot of time, time that could be spent planning, strategising, tracking, or just enjoying a cup of coffee now and then.

If you want to create more dynamic content that is, for instance, interactive, Butter is somewhat limited.

Butter takes the hassle out of posting content, streamlining a lot of processes and not chucking a million bells and whistles in your face. Can highly recommend for any individual or start-up looking to get their content strategy on the road.

Butter CMS provides a range of easy-to-use client libraries and a REST API for developers. The team is very responsive to questions or concerns.

Over the years, we've seen some performance issues with the API when using advanced features. Their support team has been quick to investigate and support in these instances.

ButterCMS helps us to provide a simple-to-use WYSIWIG for content creators to avoid needing a technical resource to publish new copy or images on our site.

Extremely easy to tag all entries with metadata that will make documentation and searching a breeze! I love that we can keep things separated by collections based on our needs!

The look of the GUI seems a little bare. The GUI provides everything you need, but the style looks a little outdated. The GUI doesn't affect the use of the tool by any means, though.

Having a central repository for our resources instead of being separated on different servers with their respective sites is a massive benefit. Production and performance have increased due to this as well.

As a developer, I used butter as a CMS to integrate with a Ruby/Jekyll stack. The documentation was easy enough to follow and the content comes in an easy to manipulate format. This made it great to fully customise the pages I was working on. It made it a lot easier to create new style of pages with great content. As a content creator, Butter is great and super easy to use to create website pages, blog posts and also update pre-existing content. The non-technical people I worked with found it a breeze to learn and use.

I think I would have liked more documentation into how to integrate at the beginning. There was a little bit to figure out. When I would research, I would find many blog articles from Butter explaining about "being able" to do these things, but not so much as to "how".

Definitely getting non technical people, able to create content on the website, without having to use confusing applications or even dive into the code itself. The Auto-updates from an API driven solution is also a plus.

To make our platform more international, we are doing localized translations. As a CS manager, I don't know anything about code, with Butter CMS I just need to enter the program, translate our webpage to Chinese, and preview to see if the translation, fonts, etc., of the web pages are OK. That's it! Super easy and flexible!

For me I think everything is fine because I am just working on the translation, I don't need to worry about the tech things. However there we few times when I check the Chinese pages, it showed me in Russian, there might be a bug, I reported it to my team. I think they contacted the support team of Butter CMS. Now I did not encounter any problems. So far so good :)

Website localization. I need to translate our webpage from English to Chinese. It's very easy to use, and I can always preview the website during my translation process so that I can edit immediately when I realize something goes wrong.

As a marketer, the thing I like most is the fact that I can quickly make changes to copy and SEO related content really quickly in a completely custom website, cutting out the engineering work that would previously have been needed. IN addition, if we need more customizable components on a site, engineering can quickly addd them as well.

Can't say I am a fan of the internal UX for making changes.

I was not able to rpeviouslty make updates to a custom site without getting FE involved. Now I can. This means that we can get marketing changes pushed to production much faster.

ButterCMS is very intuitive and allows different people across the company to make changes on the live website without having to make any code changes and that's brilliant.

There could be a way to nest components and to duplicate them, to allow for more flexibility.

Small copy changes would require an engineer spending hours to make the changes, have them approved and deployed. Now with ButterCMS that can happen instantly. ButterCMS is also a modern way to organise our site and test different variants.

Easy to use. Nice UI. Lots of features. Ability to create reusable components.

Moving content and schemas between staging and production has to be done manually.

We are using it as our content and cdn for assets for our production application. It makes it very easy to make updates to our websites.

- Easy to set up. - Very flexible and customizable. - Customer service reply quickly and will accommodate most of the customer's specific needs.

It would be great to add in feature to move content between environments.

We don't have to deploy to production for simple copy changes, but we can just easily change them from butterCMS without any hassle.

Configuration of Butter is pretty simple and straightforward. We are able to use it to essentially maintain multiple versions of our app by customizing content for specific clients. As a Product Manager, it saves a lot of time for my engineers as I can go in and update/change items myself instead of relying on them to alter hardcoded copy.

We primarily use the Collection function, and there are a couple things that are just a bit annoying about it. Nothing that we can't work around, but: 1. Because we have a lot of content in some of our collections, it sometimes takes a while for them to all load and I have to refresh a few times. 2. You can't open items in a new tab. If you want to view multiple items at the same time for editing or to compare configurations, you have to use "inspect" to get the URLs to open items in a new tab. 3. There's no export option for items.

Dynamic content in our app, language localization, reducing reliance on engineers for content changes.

- Easy to set up a development integration and moreover it's easy to use (our stack is React & TypeScript) - ButterCMS gives us the flexibility to work with our content the way we need (e.g it can be a small section with just some button/input labels or it can be the whole page with lots of different components and SEO metadata) - Simple friendly UI/UX

I love the component feature, but it feels like it lacks some kind of centralized place, where you can manage all your components. Also when a user makes some breaking change in the component structure it would be great to have the ability to interactively go through each usage to do patches.

We have a lot of pages with dynamic content that can be easily updated without developer involvement. It's worth mentioning that the component feature is a real deal!

- Logical, simple and clean interface makes it really easy to publish content - Working with our devs, we've been able to customise the back end to suit our needs - So much quicker than previous system!

- May seem simplistic if you're used to something like Wordpress, but stick with it!

It's managing our on-site content, from our static pages to blog content. Easy to load information, organise it and quick to publish, which is great in a fast-paced content environment!

A great CMS platform - easy to navigate and great for freelancers and remote staff. Everything lives in one place for all involved to see. Just drop in draft to get immediate results on how to maximize copy for SEO and targeted audience.

No complaints. No bells and whistles - if that is something you are looking for. Straight forward.

How to maximize SEO, highlight subject matters and draw in more readers, audience.

We primarily use butter for marketing purposes, using it for content growth. The best thing about Butter is that it's easy to stand up (transition speed was key for us). Furthermore, we like how the foundational elements of pages can be changed over time seamlessly. This was reassuring, knowing that we could make fast decisions early on and iterate as our content/marketing strategy shifted.

To fully leverage Butter you need to be or have front-end developer support. This is not a platform for "non-technical" folks looking for a WYSIWYG platform out of the box. Once you get it set up, adding content is super simple, but it takes an initial setup period.

Butter solved our content scaling and design flexibility needs.

Perfect documentation and simple powerful API

Search API for blog post is not implemented in JAVA library. Please implement Create/Delete function on screens for managing categories/tags (blog posts).

Our own blog - value based content for our customers. Benefit for us was clear: we do not need to develop our own database and full management. Blog API provide not only simple "save" of title/description -> but also SEO tags, categories and tags. ButterCMS own CDN for images is also benefit (we do not need to implement our own storage for images in posts).

The flexibility and the fact that ButterCMS worked with any tech stack plus the documentation/support made it very easy to implement. Our original content server was heavily customized and it was difficult to make updates since no one knew PHP. With ButterCMS, the engineers had a much easy time integrating it into our site. When and if they encountered issues or had questions the super responsive and helpful customer support was always there to help resolve the issues. Also, as a PM working with a remote team of engineers on different time zones, it made my job easier being able to update content on the site directly without requiring a lot of dev work.

Nothing major but the one thing that comes to mind is the text editor. It was a bit difficult to customize blog articles with things like bullets, assign header tags etc without messing up the format. Also I would have liked an integration with photo providers :)

The content on our site was outdated and we needed a way to post blog articles to help users make decisions. By implementing ButterCMS, we were able to improve our SEO rankings which in turn boosted our acquisition and engagement so all in all it was a very good idea.

We've used ButterCMS since day 1 at Bottlecode. We were able to implement our basic content strategy in half a day using ButterCMS and our content team loves the product. I can only recall one day with some intermittent downtime due to their upstream CDN and the team was responsive. Their technical support is top-notch, too.

I'd love more flexibility around creating my own "components" to add to page types as well as validation rules and hooking into our own data, but that's teetering close to custom CMS territory.

We use ButterCMS to power our "Skincare 101" education portal at Bottlecode as well as highly-customized landing pages we use to test creative strategies.

Butter CMS allows me to make content pages quickly and easily while being flexible and powerful enough to allow for the needs of my company. On the rare occasion I have an issue, the team at Butter CMS was very quick to help me find a resolution - even going far as to troubleshoot an issue on my end.

A few more options with blog posts in the API would be great the editor for the raw html/text could be a little nicer but these are very minor complaints.

Essentially, ButterCMS allows for our online sales platform to rapidly make pages for all of our products. The well documented API makes it extremely easy to update our content dynamically and customize it to fit our needs.

Butter made it extremely easy to add a CMS backend to my website. The implementation is as simple as building your content structure on the admin panel, and then using your API key to pull in all the content via HTTP requests (or it's just as easy, if not easier to use Butter's libraries) The ability to use references that link to other content types is extremely powerful, and can even let you move some logic from your app to the CMS. For example, I had to define a mapping of US States to Regions (Midwest, Northeast, etc). Instead of doing this in the application itself, I defined a State content type on Butter, added all 50 states, and then defined a Region content type that was composed of a list of States. Someday we may have to define a "Pacific Northwest" region or break the original ones down to smaller ones, and that change will be seamless thanks to Butter's flexible content types and linking. This type of reference ability allows for less business logic in the application which I love. The customer service is also stellar and they were quick to concisely answer all of my questions about certain features and which feature would suit my individual use case the best way.

I like everything about Butter, but it is a little bit leaner than some other comparable solutions. It more than makes up for this with its cheaper price tag & comparable features to other headless externally hosted CMSs but there are some features I would like to see in the future. For example, there is not a way that I know of to validate input in to the CMS (other than marking a field as required), so your "content inputters" must be diligent.

We are using Butter to add a CMS backend to our existing website. It's been incredibly simple and easy to add the service and pull the CMS data in to our site via their API. We've been able to move almost all of our copy out of the application and in to the CMS, reducing engineering overhead for copy related tasks. We've even been able to move some business logic (which I detailed above) in to the CMS.

The detailed documentation that gets any project up and running within no time is the best aspect of butter. Also the content updates in seconds right after you hit publish, so that you don't need to wait for your project to build.

Butter is best for managing content for blogs & static informative website. It will be good to have dynamic data feature which updates in butter itself based on user inputs.

The biggest benefit is that you don't need to spend days setting up a database, spending the rxtra dimes on it as well as spending extra time on content creation. Butter manages all your data and lets you create content on the fly. It adds value to startups & medium sized business as they might not always have enough staff & budget to do all that.

Simple to config, easy to use. The doc is very clear and the api very fast. I think this is the most easy api I had to use for the past three years and I'm going to tell everyone to use it when they want to create a simple blog application even a complex one. The filter you can use on every call is just sugar in the mouth. Just perfect for me.

The only thing I can ask is to provide filters to retrieve tags (like page_size) and maybe a feature who can tell you the most views articles. - Support next format of img like .webp with jpg fallback (ex).

I can create a blog using a simple API without coding any back-end stuff.