What is a CMS?

What it means

A content management system is the back office of a website. You log in, type a new blog post or swap a photo, press publish, and the site updates. No code required.

Without a CMS, every change means editing files by hand or paying a developer. That’s fine for a site that never changes, and a chore for one that does.

Plenty of sites still run without one: W3Techs reports that 31.5% of websites use no CMS it can detect.

How it works

A CMS keeps two things apart: your content (text, images, products) and the design that displays it, usually a template or theme.

Content usually sits in a database. When a visitor opens a page, the CMS pulls the right content, places it into the design and sends the finished page to the browser. Change the theme and the content stays; edit a post and the design stays.

Most systems also handle user accounts and roles, drafts and revisions, menus, media and basic SEO fields. Extra features come from plugins or apps.

Here is how the main systems compare, according to W3Techs:

Why it matters when you build a site

Your CMS decides who can update the site, how easy that is, and what happens to your content if you ever leave.

That last point gets skipped. Some systems export content in a standard format; others keep it. Self-hosted WordPress scores 10 out of 10 on our exit scores. Wix scores 3, partly because Wix says blog posts cannot be exported to other platforms.

Think about who will update the site day to day. If that’s you or a staff member without technical skills, the editing screen matters as much as the design.

If you publish often, a good CMS is worth more than a fancy template. Our Wix vs WordPress comparison shows how two very different approaches play out.

How the big builders handle it

• Self-hosted WordPress: a full CMS with posts, pages, categories, tags, revisions and comments, plus custom content types through plugins or code. Content exports to a standard WordPress XML file, though media files are referenced by link rather than included.
• WordPress.com: the same WordPress CMS, hosted for you.
• Squarespace: built-in blog pages. You can run several blogs on one site, but only one can be exported.
• Wix: built-in blog and CMS collections. Collection content can be exported; blog posts can’t.
• Webflow: custom CMS collections on the Premium site plan (20,000 items, 40 collections). Basic has no CMS. CMS content exports and imports as CSV.
• Framer: CMS collections by plan: 2 collections and 1,000 items on Basic, 10 collections and 2,500 items on Pro.
• Lovable, Bolt and v0: no built-in CMS. Content is written into the app, or connected through a headless CMS.

Common mistakes

• Choosing by the editor alone. A pleasant editor is nice. Being able to take your posts with you matters more over five years.
• Outgrowing item limits. A blog or directory can pass 1,000 items faster than you’d expect, which is Framer’s Basic limit.
• Installing a plugin for everything. Each plugin is another thing to update and another possible conflict.
• Giving everyone admin access. Use editor or contributor roles for people who only write content.
• Forgetting that AI-built apps have no CMS. Without one, a simple text change can mean another prompt or a code edit.

Related terms

• Headless CMS: a CMS without its own front end.
• Template vs theme: the design layer a CMS fills with content.
• Plugin: add-ons that extend a CMS.
• SEO: helping your content show up in search.