State of
CMS

The annual survey for everyone building or publishing online.

Survey is open

Let's find out which tools web creators and marketers want to use, which have the best retention ratings, and much more.

Let's find out what tools and features you love

State of JS, HTML, CSS ask developers which tools they use, which they stop using, and why. Content management has no yearly survey like this.

This year we would like to set a baseline for the years to come.

  1. IWhomakes and manages websites now, and for whom.
  2. IIWhich CMSspeople use, try and leave, and how happy they are.
  3. IIIWhy changeand what the change costs.
  4. IVWhat people tryand what stops them.
  5. VContent creationwho edits, and how fast a page goes live.
  6. VIPainsWhat makes website creators scream.
  7. VIIAIWhat AI does in CMS work today.
  8. VIIIWhere work livesVendor cloud, Git, own servers.

Why now?

Choosing a CMS used to be a ten-year decision. Moving meant months of content migration, rebuilt templates and broken links, so most people stayed, happy or not. That is no longer true.

  1. -

    Switching costs fall toward zero

    Dries Buytaert, the founder of Drupal, thinks that website migration costs are going to zero. What will this mean for builders?

  2. -

    People are on the move

    Developers, designers and editors try new tools faster than ever: site builders, headless, Git-based, or no CMS at all. Loyalty is no longer the default.

  3. -

    The CMS itself is changing

    AI tools build whole sites from a prompt, and some teams ask an agent to change a page instead of logging in to an admin. What counts as a CMS is open again.

  4. -

    Measure the move as it happens

    Previous surveys of CMS platform usage covered one vendor or smaller niches. As more and more people report moving, we think 2026 is the year to start a new annual survey that covers all.

Did you switch this year, or are you about to? Tell us why.

Take the survey

Open source

The anonymized results from the survey will be freely available on GitHub.

We will create a visual representation of them, and we look forward to seeing what the community does with the data.