What Is Decap CMS?

Updated

Decap CMS is an open-source, self-hosted content management system that stores your content in your own Git repository instead of a separate database. It gives non-technical editors a web-based interface with structured fields, rich text, and live preview, while developers keep full version history and control through Git. It fits best if you run a static site or Jamstack project (Hugo, Next.js, Gatsby, Jekyll, and similar) and want editorial tooling without handing your content to a third-party platform.

How it works

Decap sits between your editors and your repository:

  • Editors log into a web UI, fill in fields, and save. They don't need to touch Git directly.
  • Decap commits the resulting content files (typically Markdown) to your Git repository.
  • Your static site generator rebuilds from those files and deploys as usual.

Because content lives in the repo, every edit is a commit. You get branch workflows, diffs, and rollback through the same system your team already uses for code.

What you get

Capability What it means in practice
Friendly editor UI Structured fields, rich text, and real-time preview so non-technical contributors can work confidently
Editorial workflow Content moves through draft → review → publish statuses before going live
Git-native history Full version history and branch workflows, with deployment checks in the same pipeline
Flexible content modeling Define collections, nested structures, relation fields, and slug behavior to match your project
Single YAML config Configure collections, fields, workflow rules, and media handling in one config.yml
Extensibility Custom widgets, editor components, and plugins when defaults aren't enough

Who it's for

Decap is strongest when you want an efficient developer and editorial experience, Git-native implementation, ownership over your content, and a flexible, extensible platform. It's a good match if:

  • Your site is already built on a static site generator or Jamstack architecture.
  • You want content stored in your own repository rather than a provider's database.
  • You have non-technical contributors who need a visual editor.
  • You want to avoid running and maintaining a separate CMS backend.

It's a weaker fit if you need a hosted database-backed CMS with server-side rendering, or if your team has no Git-based deployment pipeline at all.

Licensing and cost

Decap CMS is MIT-licensed and described as free and open source, and the project states it will remain free. It is self-hosted, so you run the editorial UI against your own repository rather than paying a platform for content storage.

Getting started

The project describes setup as simple and free, and points to its documentation and an interactive demo. The core steps are:

  1. Add the Decap CMS admin interface to your site.
  2. Write a config.yml defining your collections, fields, and media handling.
  3. Connect it to a supported Git provider so editors can authenticate and commit.

For exact setup steps, configuration options, and provider-specific authentication, use the official docs at decapcms.org rather than guessing at menu locations or field names.