Developer Tools
Netlify CMS
Former name of Decap CMS, an open-source Git-based editing interface for static sites.
What it is
Netlify CMS was renamed Decap CMS in February 2023. The maintained project is an MIT-licensed React single-page application placed in a site's admin path; it presents an editing UI over content stored in Git and communicates with supported Git hosts through their APIs. Authentication, repository permissions, content schema, media handling, previews and build/deploy behavior still have to be configured and secured as one delivery chain.
Key features
Git-backed editor
Reads and writes configured content files through a supported repository backend.
Content collections
Defines file or folder content models and editor fields in YAML configuration.
Editorial workflow
Represents drafts and approvals using branches plus pull or merge requests.
Custom UI extensions
Supports custom previews, widgets and editor plugins for project-specific authoring.
Strengths and trade-offs
What works well
- Git-native content: Editorial changes are stored alongside site content with repository history and review options.
- Static-generator flexibility: The project is designed to work across static-site generators rather than require Netlify hosting.
- Editorial workflow: Drafts can map to branches and pull or merge requests before publication.
- Extensible editor: Teams can define collections and fields and add custom previews, widgets and editor plugins.
Where it falls short
- Renamed product: Current documentation, packages and support use Decap CMS, so the Netlify CMS name is legacy.
- Authentication setup: Direct Git backends can require an OAuth proxy, while Git Gateway introduces an additional identity and gateway dependency.
- Repository coupling: Content editing depends on Git-host APIs, permissions, branches and rate or service availability.
- No full delivery platform: Site builds, hosting, backups, asset strategy and deployment controls come from separate services and configuration.
Who it is for
Static-site teams that want a browser editor while retaining Git as the content source of truth.
Our verdict
Evaluate this product under its current Decap CMS identity. Choose it when Git-backed content is intentional, then test authentication, least-privilege repository access, editorial branches, media, previews and deployment failure recovery end to end.
Closest alternatives we track
Same category, ordered by verified starting price.
What we checked
- Public APIOffers a documented API you can build against.Yes
- Mobile appHas a native app for iOS or Android, not just a mobile website.No
- Open source / self-hostableSource is open and the tool can be run on your own infrastructure.Yes
- SSO (SAML)Supports SAML single sign-on on at least one plan.No
“Not checked” means exactly that — we have not verified it, and we do not guess.
Evidence and freshness
Status: Official sources reviewedReviewed: 2026-08-24
- Decap CMS Docs — Overview ↗
Checked 2026-08-24 · Supports: Netlify CMS rename, open-source React application, Git workflow, static-site-generator support, GitHub GitLab and Bitbucket APIs, content storage, custom extensions
- Decap CMS — Introducing Decap ↗
Checked 2026-08-24 · Supports: February 2023 rebrand, maintainer transition, continued support intent, Git-based CMS identity
- Decap CMS Docs — Backend overview ↗
Checked 2026-08-24 · Supports: Git-host API dependency, repository and branch configuration, OAuth proxy requirement, backend API stability caveat
- Decap CMS Docs — Git Gateway ↗
Checked 2026-08-24 · Supports: Git Gateway behavior, Netlify Identity option, self-hosted gateway option, JWT and PKCE configuration, repository permission reconnection
- Decap CMS Docs — Editorial workflows ↗
Checked 2026-08-24 · Supports: default direct commit, draft review and approval mode, branch and pull-request mapping, GitHub GitLab and Bitbucket support, squash merge option
- Decap CMS — Source repository ↗
Checked 2026-08-24 · Supports: maintained repository, single-page admin application, YAML content model, release history, MIT license, open-source status
Limit: Official Decap CMS documentation, project announcement and source repository were reviewed; ToolCompare did not install the CMS, test a Git host or OAuth proxy, audit Git Gateway, validate repository permissions, run an editorial workflow, test media or previews, inspect accessibility, or exercise build and deployment recovery.