Sveltia CMS is an open-source, MIT-licensed Git-based editor written as a rewrite of Netlify CMS, which is now Decap CMS. It keeps Decap’s configuration format, so many existing sites switch with minimal changes. The editor is a single-page app you serve from your own site at /admin, with no backend of your own to run.
What is its status in October 2026?
Active, but not 1.0. The repository sveltia/sveltia-cms had a commit and release v0.253.0 on 26 October 2026, and has about 3,000 stars. The project docs call it beta and plan a 1.0 for late 2026. They also say it is maintained mainly by one developer, so progress depends on that person. That is the main risk to weigh. It is listed with the others in our Git-based CMS comparison.
What does it add over Decap?
- First-class support for multiple languages in content.
- A faster interface that also works on a phone.
- More media storage options: the internal repo folder, Cloudinary, Amazon S3, Cloudflare R2, Backblaze B2 and several others.
- Stock photo search from Pexels, Pixabay and Unsplash.
- Fixes for many open Decap issues, which the project counts on its site.
Which backends and site generators work?
The docs name GitHub, GitLab and Gitea or Forgejo. GitHub performs best because of its GraphQL API. Because it only edits files, it works with Astro, Hugo, Eleventy, Jekyll, Next.js, SvelteKit and other generators that build from content files.
Who does it suit?
Teams on a static site who want a free editor with sound multilingual support, and teams stuck on an ageing Decap setup. Documentation sites, marketing sites and blogs are the natural fit.
Where are the limits?
- No accounts of its own. Editors need an account with your Git provider.
- Scale: Git API rate limits and response times cap how large a site can be.
- Roles: Permissions follow repository access, not fields or locales.
- Beta: Config details can still change before 1.0.
When would we use something else?
If you need a vendor contract and hosted accounts, CloudCannon fits. For on-page visual editing, Tina. For the longest track record and a larger community, Decap itself. For the fastest GitHub-only setup, Pages CMS. For data that many apps share, a full headless CMS.
What can we do for a team using Sveltia?
- Migrate a Decap or Static CMS site: audit the config, switch the editor, and test every collection and widget.
- Set up the GitHub or GitLab login, media storage and preview links.
- Build the static site, as we did when we replaced a slow single-page app with Astro for a US-based Series-B B2B SaaS, cutting LCP from 4.2s to 1.4s. See the Astro and Jamstack case study.
- Plan the move to an API-based CMS if the content outgrows Git.