Butter CMS Reviews & Product Details

I love having control of my website content without having to use WordPress or another awful CMS. The language option makes localization super easy. Their support is awesome. I made a complicated request and it was taken care of within 24 hours.

On some of the pages it can be problematic to have to scroll down to view all the content boxes.

Allow us to make all the changes we need to the site and nothing more. No WordPress!

I used Butter CMS for a project with one organization that I worked for, and when I had similar requirements at my next job, I immediately recommended it there because I knew that working with it again would be perfect for me. As a developer (formerly) and technical architect with a lot of experience with HTML, CSS, Javascript, and several server-side rendering languages, I prefer to build my UI from the ground up, so using a headless CMS is a no-brainer for me and Butter CMS is the best one I've found. It's been able to provide all of the functionality that I've needed on the projects I've used it on, and it's not overly complex so I don't feel like I'm only utilizing 10% of the product. Similarly, the simplicity implies to me minimal overhead. The documentation is great, and the support team has been excellent regarding both response time (usually same day - within an hour or so, even) and efficacy.

I don't have any particular thing that I "dislike" at the moment. As I mentioned above, the support team is great so any time I've had an issue I've reached out to them and resolved it quickly.

As I mentioned under "What do you like best?" the main problem for me is otherwise having to rely on CMS platforms that take too much control away from the developer and/or require you to essentially learn to use that CMS like you'd learn to write another language. I want to bring to the table my frontend, my backend API's, decisions related to authentication and all of that, and I just want Butter to house my content and provide an interface where the people responsible for content on our website can go and make those changes, and that's exactly what it provides: no more, no less.

I made the decision to switch from Contentful to ButterCMS after doing a bit of shopping around / research of the current HeadlessCMS offerings. ButterCMS is an API first platform, served in JSON in a mostly RESTful way. It was definitely built with developers in mind, which is what makes its integration, setup time, and delivery among the top praised aspects of the platform/service. Here are some of the best features: - Collections and the ability to order fields and items - The Page engine to build static and templated pages - A Blog engine that serves a collection of Posts with SEO in mind - Great documentation in multiple languages and frameworks - Integration with Filestack / CDN - Page Preview - And last but not least, an absolutely amazing Customer Service team, super responsive and helpful! Things that really impressed me: - I reported a bug and it was fixed over the weekend. That's dedication! - Our Marketing team loved the ease in which they can now manage content in comparison to their experience with Contentful - Real conversations with the Co Founder and Customer Success team - Getting informed of new features and being asked for input on what would make this service better Overall, I would highly recommend this over other Headless CMS services I have tried and evaluated.

I think the admin interface is showing its age from a UI perspective, but is generally great from a UX perspective. Regardless, it is very usable and needs little to no on-boarding to using it, which my team loves! There really just isn't much to dislike about this service!

Our team set out to solve the problem of having TWO CMSs run our marketing site. We had a blog in Wordpress and the rest of the site was in React/Gatsby/Contentful. Managing two CMSs was a pain. Matching UI elements in two completely different stacks was a nightmare. The marketing team in particularly dislikes Contentful for various reasons, so I was tasked for exploring alternatives. After integrating with Butter, we were able to get the best features of Wordpress (Preview, Edit history, Blog Engine, SEO) plus the ability to essentially build custom admin forms (Page engine), all through a single CMS. Pulling the site through a traditional SSR application gave us the ability to run our site similar to a Wordpress architecture, which was important to the Marketing Team.

The best thing I like about Butter CMS is their support and engineer teams. They're very helpful whenever you need them. Also I love the API and documentation, very handy with multiple programming language doc, make it a lot easier to integrate.

I would say the speed of the API a bit slow, but then I believe my query was collecting too much data and hence why it's slow. Still, the API-based CMS is very amazing, cannot go back to Wordpress once you starts with ButterCMS!

We want to make it a lot easier to publish our content. Now we can have anyone in our office to update content, and the engineer team wouldn't have to worry anymore.

They really make me feel valued as a customer. They work WITH you. It's not as though it's their way or the highway. They have amazing documentation for a variety of web frameworks (I'm using Gatsby).

The only downside I've experienced so far is that you need the Business Plan for Localizations but like I said previously they were willing to work with me to come to a solution. Also, having the ability to create some structure for all your Collections would be helpful.

I was initially only thinking of using them for my blog content but now all the static information for my entire site is hosted with them. What a great way to organize you content. Localization management is also a huge boon and it brings my site accessibility to a new level.

We were able to seamlessly integrate ButterCMS into our existing Progressive Web App (PWA) to help provide our community with more resources and grow our digital marketing. We are able to publish content regularly to our PWA and grow our marketing efforts.

It would be tough to say that there is anything in particular that we dislike. Our development team was able to hook up to ButterCMS's API relatively easily and get our blog up and running very fast.

We built our PWA using Stenciljs and since it is framework-free and based on web components we wanted something that would integrate seamlessly. Additionally, we wanted something that would allow us to publish new content to our website that did not require developers, designers, and QA testers. We discussed custom building a blog and a CMS but the time and investment was tough to justify because we dedicate most of our time to client work. ButterCMS allows anyone on our team to easily publish new content to our PWA without the need of skilled developers or designers.

The simplicity of Butter CMS is the part we like the most along with how quickly we were able to adapt it for our complex requirements.

Nothing to dislike. It does exactly whats written on the tin and more.

Providing content for our realtime Travel Disruption Insurance product. We needed a headless CMS for storing content in multiple languages. ButterCMS was the best software we found. The technical support from ButterCMS has been among the best we've encountered among all the service providers.

Butter's most obvious benefit is simplicity. It does not require any specialized technical knowledge. It doesn't require digging to find solutions for simple problems. It doesn't need a lot of training to utilize. It's the epitome of plug-and-play simplicity for content creators.

The only problem: I would love if Butter automatically saved progress.

We can quickly: 1. Collaborate. Everyone on the team can see what's coming and what's being worked on. 2. Publish. We can publish straight to our web app's blog seamlessly. 3. Create and change URL slugs. Basic functionality that's easy to access and even easier to utilize. 4. Use simple SEO tools. It does what it's supposed to. No wizardry required. Less is more! 5. End-to-end solution. I don't need plugins or hackneyed daisy chains of mismanaged and deprecated software just to publish content. It's made publishing and drafting content a frictionless experience.

It has a super clean interface, it is easy to use, easy to customise, and just generally ideal. It takes me very little time to create blogs that are very high quality. That's not because I am in any way good at content. Butter just makes everything come together and look great with little effort.

So far, nothing. If I ever have even the smallest concern, I can ping in livechat and get a solid response within minutes. I'm halfway round the planet, and I still get ridiculously good support from the butter team.

It means we can have a powerful, gorgeous blog without spending a tonne on it. It is fantastic for SEO and highly optimised cross-platform, making it the ideal tool for pretty much anyone.

Butter CMS is very easy to install and use, for the developer and content editor. It only took about an hour to fully integrate Butter into my Next.js/React app. The editor is easy and has just enough formatting options to make it powerful, but not so many options as to introduce headache for coordinating with the CSS in my app. Uploading media is easy. Interface and feel are a million times better than WordPress.

Very few complaints. I have asked for image metadata to be available.

I chose Butter because it allows us to easily manage a blog within the context of a custom app of our choice. Butter was the cleanest and easiest of the options I explored.

We were initially attracted to ButterCMS because they seemed to understand the needs of the RoR community with plenty of good, concise documentation. I love that they roll out new enhancements and features often and respond to feature requests. I emailed supporting asking if I could use HTML snippets inside ButterCMS pages and Jake at Butter actually took the time to create a custom screencast just for me!

I really can't think of anything that I dislike about ButterCMS.

This was our first CMS system so we wanted other, non-HTML types, to be able to contribute and update content without knowing how to write code.

Service & support were absolutely excellent!

Cancelling a subscription requires email

We're using ButterCMS as a headless CMS for our website and web application. It could not have been a better fit. Before introducing ButterCMS to my team, they believed there was no such thing as a 'headless CMS'.

If you are doing a modern site or app (node, Angular, React, Vue etc) ButterCMS allows content to be updated without pushing a new build. It is your backend plus an easy interface that even marketing people can figure out. Think of a field value, and Butter lets it be updated externally by others so you don't have to. All their stupid spelling mistakes and content updates can proceed 24/7 without you even knowing. A huge huge benefit for s since we wanted to run an all-Angular shop from products to website. Documentation is complete with clear examples.

This has all been fixed but at first the interface was difficult to understand. There was some jargon like "Workspaces" that took time to visualize.

Everyone can access the site and update content without bothering engineering. They can push immediate updates that get our message out there instantly.

With some easy building blocks like collections, relationships, and basic content fields, you can make about content types that can fit any client. Super easy to use even easier to install. I used Rails to install a blog and their Custom Pages and Fields Their customer service is great. I always work late but they'll message me before 7am with any question I had the night before.

The image loader can be annoying sometimes, there's a lapse in UI since they're using a third party uploader.

I am able to build a website for my client that gives them the ability to easily update their own website and keep it organized.

Using Blog Engine Class Objects is easy to integrate into my ASP.NET code. The documentation provided information about each class object and its attributes. In comparison to other headless CMS products I have tried to integrate with that used complex JSON structures, this one was the most simplest. I created the site and integrated it with the CMS in less than a day.

Pricing for non-personal sites is high. However, if you are building for a personal site, contact their sales team and they will grant you access to a personal plan for free, with a few links on your site.

For a simply blog, it provides a easy to integrate tool for the developer, and an editorial tool that is not as complicated for the author. I have worked with individuals that are looking for a simply interface to enter content without a huge learning curve. ButterCMS provides this. I use ASP.NET to integrate the content into my web template, so all I had to do was load the reference, call the appropriate class object and match up the attributes. There was even an IEnumerable interface that fed into a DataTable to connect to my data-type controls. I had to create a blog for my Master's thesis project, and was able to do it within a few hours.

Coming from a Drupal background, setting up my content was very easy. Probably the easiest thing, though, was how easy it was to get my Vuejs app up and running. I just cloned their sample app, added my info in, implemented my custom Bulma template, and I was up and running.

There's not much to dislike. If I had to pick a nit, when in the UI, even when you are logged in, the main nav still shows the "Log In" link.

Launching my website with a Vuejs front end, this provided me with a simple-to-use back end for my data.

I work as a senior developer for a digital agency and have trialled many different CMS, especially headless CMS recently. Of them all ButterCMS was - by a long margin - the easiest to get up and running with. It took me just under 6 hours from start to finish to build my blogging site (using .NET Core 2.0 MVC), including the time to register for hosting and write my first blog.

The wysiwyg editor could be better. I'd personally prefer a markdown option. Overall though, it provides everything needed for a blog.

Speed of development has to be #1. No more fighting with silly ID's or spending hours trying to figure out how to make routing work with odd identifiers. Butter CMS uses the url slug as the identifier which makes routing in my application a breeze.

The UI to manage content is very simple to use by Content Managers. Content Managers and Administrators can easily manage blog posts, content fields, page types, pages, media library and internationalization. The ButterCMS support and engineering teams are great; they offered us a lot of help to support different requirements for our Customer, including the development of new improvements and features which was extremely useful for the success of the implementation project. The API and documentation are very complete and easy to integrate from different programming languages, in our case we integrated ButterCMS into a Rails 5 application, and the experience for developers was very simple. The performance and scalability of the API are great, we executed performance tests with more than 12.000 requests per minute, and the API worked without latency problems.

When we started to use ButterCMS there were some UI improvements Content Managers identified, however once we sent the improvement list to the Support Team, they implemented different improvements providing a great experience for us and our Customer.

We implemented ButterCMS on an Enterprise Website for one of our Customers that wanted to migrate from a commercial and traditional CMS solution. The website has a lot of pages with different templates, it is available in three languages, and it is deployed on Heroku Salesforce. The main business benefits for the Customer are: * Easy to manage content by Content Manager and Developers. * Flexibility to model different types of content (products, services, pages, FAQs, terms and conditions, landing pages, etc.) * Ability to configure fields for SEO and social networks. * Agility and easy to integrate Content from different applications (web and mobile) using the API. * Reduce the load time for pages, improving the user experience, improving SEO, increasing page views, and generating more leads for sales teams. * Very easy to integrate for Heroku applications using the ButterCMS Add-on. * Cost saving due to the ButterCMS takes care of all the infrastructure maintenance and operation.

Easy to set up, easy to work on, a lot of functionalities... and a GREAT customer service, always ready to help you in everything that you need.

The UI is really clean and easy to use, but I believe that a great feature would be a navigation using tabs, to better organize the pages that have a lot of fields.

We were developing a project in a brand new architeture (using Heroku platform and integrating with Salesforce) with a rails app, and Butter gave us an easy to integrate platform, which turned the process of managing content in the website from days to seconds.

Customer service and support have been incredible from ButterCMS. Seriously it is so nice to see someone care about their product so much!

Whats not to like? I have enjoyed nearly every element of ButterCMS. It does take a little time to get used to the concept of a headless CMS but beyond that, there is nothing not to love about it.

As a growing SaaS company that has multi-channel content needs nothing has made it easier than ButterCMS! Jake and team have created a dynamic, simple to use product. It is crazy simple to stand up content for any website in minutes! Better than this is their great customer support. I have never had to wait more than a few minutes to get my questions answered! That is something that you simply just don't get from other solutions.