TinaCMS

TinaCMS is an open-source Git-based headless CMS that lets editors click directly on text in a live preview and edit it in a side panel — with every change committed back to the repository as a real Markdown, MDX or JSON file. We rate it 78/100 — the best fit for Next.js, Astro and Hugo sites that need a friendly editor for non-developers without surrendering source-of-truth content to a SaaS database.

What is TinaCMS?

TinaCMS was launched in November 2019 by the team at Forestry.io — a Halifax, Nova Scotia studio that had spent years building Git-based CMS tooling for Jamstack sites. The Forestry product was sunset in 2022 to consolidate around Tina, which is now Apache-2.0 licensed with over 13,300 GitHub stars and 690+ forks.

The core idea is simple but unusual: your content stays as plain files (Markdown, MDX, JSON or YAML) in your Git repo, while Tina layers a typed schema, GraphQL API and a React-based visual editor on top. There is no separate content database to back up, and no per-record fee. Your git log is your audit trail.

Key Features of TinaCMS

• Visual editing on a live preview: Editors click on any field on the rendered page and a sidebar form opens. Changes update the preview instantly. Differentiates Tina from Decap CMS and Keystatic, which are mostly form-based.
• Git as the database: Every save is a commit. No external database, no migration scripts when you change schemas — Markdown files in /content are the source of truth.
• Typed schema with GraphQL: Define collections in TypeScript, get an auto-generated GraphQL API, typed queries and IDE-friendly autocomplete.
• Format flexibility: Stores content as Markdown, MDX, JSON or YAML — pick whichever your generator already understands.
• TinaCloud (managed backend): Hosted Git auth, media library, search index and editorial workflow with draft/review states. Removes ops burden.
• Self-hostable backend: The full backend can run on your own infrastructure for teams that don't want a SaaS dependency.
• Framework-agnostic with first-class Next.js support: Works with Next.js, Astro, Hugo, Gatsby, Remix and any static generator. Next.js gets the deepest visual-editing integration.

What Users Say About TinaCMS

The most consistent praise across StackShare, the GitHub Discussions board and Bejamas reviews is that TinaCMS "makes editors stop emailing the dev team." The visual-editing experience is the headline feature and reviewers single out the live preview as feeling closer to a WordPress block editor than to a typical headless CMS. Documentation, the Discord community and quick support response are also frequently praised.

The honest critiques are equally consistent. The most circulated review from drzax flags that the WYSIWYG markdown editor is "underdone": it doesn't render raw HTML in Markdown (a core Markdown feature) and skips extensions like footnotes and definition lists. There is no native i18n — multi-locale sites typically encode locale into the filename or folder structure. Documents are single-user-edit only, so two editors can clobber each other if collaboration isn't coordinated. And TinaCloud, while convenient, is a SaaS dependency that pure Git-based fans prefer to avoid; self-hosting the backend works but is a real ops project.

TinaCMS Pricing

The CMS itself is free and Apache-2.0 licensed forever. Pricing applies to TinaCloud, the hosted backend that runs Git auth, media and the editorial workflow.

Plan	Price	Key Limits
Free	$0	2 editors, basic visual editing, managed Git integration, core media handling
Team	$29/month	Unlimited editors, editorial workflow with draft/review states, priority support
Enterprise	Contact	SSO, custom roles, custom workflows, dedicated support and SLAs
Self-hosted	$0	Run the Tina backend on your own infrastructure — no editor cap, no SaaS dependency

Who Should Use TinaCMS?

Best for: Marketing-led startups and agencies running Next.js, Astro or Hugo sites where a single editor or small editorial team needs a friendly UI for Markdown content. Particularly compelling for documentation sites, blogs and brochure sites that already live in a monorepo.

Not ideal for: Multi-language sites (no native i18n), high-concurrency editorial teams (no real-time multi-user editing per document), or product catalogs with thousands of structured records — Tina shines on dozens to hundreds of files, not tens of thousands.

Pros and Cons

Pros:

• Genuine click-to-edit visual editing — rare in the open-source headless CMS space
• Git as the source of truth: every change is auditable, no separate DB to back up
• Typed schema and GraphQL API mean refactors are safe
• Free tier covers most solo and small-team projects
• Apache-2.0 licensed, with a self-hostable backend option

Cons:

• WYSIWYG Markdown editor doesn't support inline HTML or footnotes — surprising omissions
• No native internationalization (multi-locale)
• Single-user-per-document editing — no live collaboration
• TinaCloud is a SaaS dependency unless you self-host the backend
• Smaller community than Strapi or Contentful — fewer Stack Overflow answers

Alternatives to TinaCMS

If TinaCMS isn't a fit, consider Payload for a TypeScript-native database-backed CMS with deeper Next.js integration, Strapi for a larger plugin ecosystem, or Sanity for a real-time collaborative editor with strong portable-text support.

Verdict: Is TinaCMS Worth It?

Yes — if your stack is already Markdown-and-Git, and your editors keep emailing the dev team to update copy. The 78/100 reflects the genuinely best visual-editing experience in the Git-based CMS category, the appeal of keeping content as plain files in your repo, and a free tier that covers most small teams. We hold back the last 22 points for the Markdown editor's missing features (HTML, footnotes), the lack of i18n and the absence of multi-user collaboration. For multilingual or product-data-heavy sites, look elsewhere; for a Next.js blog or marketing site that needs friendlier editing, TinaCMS is the obvious answer in 2026.

Frequently Asked Questions

Is TinaCMS free?

Yes. The TinaCMS package is free and Apache-2.0 open source. The hosted TinaCloud backend has a free tier for up to 2 editors. Paid plans start at $29/month for unlimited editors and editorial workflow.

Is TinaCMS open source?

Yes. TinaCMS is Apache-2.0 licensed on GitHub with 13,300+ stars. The backend can also be self-hosted.

How does TinaCMS store content?

Content is stored as Markdown, MDX, JSON or YAML files inside your Git repository. Every edit is a Git commit. There is no separate content database — your repo is the source of truth.

How does TinaCMS compare to Decap CMS or Keystatic?

All three are Git-based, but TinaCMS is the only one with click-to-edit visual editing on a live preview. Decap CMS and Keystatic are form-based. TinaCMS also offers a hosted TinaCloud backend, while Decap is purely client-side.

Does TinaCMS support multi-language sites?

Not natively. Multi-locale content is typically handled by the framework (e.g. Next.js i18n routing) and by encoding locale in the file path. Teams that need rich i18n features may prefer Strapi or Contentful.

Can I self-host TinaCMS?

Yes. The Tina backend can run on your own infrastructure — removing the TinaCloud SaaS dependency. Self-hosting is a meaningful infrastructure commitment but is well-documented in the official guides.