Where Does Outstatic Store Content and Settings?
Outstatic Markdown content folder, metadata file and dashboard routes in Next.js.
Last updated
Outstatic has no database. Every post, page and collection is a Markdown or MDX file committed to your GitHub repo, edited through a dashboard that lives inside your own Next.js app. The file tree is the CMS.
Collections are folders under outstatic/content, each document a file with frontmatter plus a shared metadata.json index the fetch helpers read. Dashboard code sits at the /outstatic route (commonly app/(cms)/outstatic/[[...ost]]/page.tsx). Project settings and AI keys differ between self hosted and Pro, but content never leaves the repo.
Where Outstatic stores this, by platform
.\outstatic\content
Collections as subfolders (posts, etc.), documents as .md/.mdx plus metadata.json. The dashboard route files live under app/(cms)/ in the same repo. Content deploys when the repo deploys.
./outstatic/content
Same repo relative layout. Use getCollections and the document fetchers on the frontend; they read these folders. Custom fields and Tiptap/Novel editor state serialize into frontmatter.
./outstatic/content
Same files on Linux checkouts and CI. Keep GitHub auth and any Outstatic Pro project key in env, not in content. Editors publish without touching Markdown directly.
Frequently asked questions
where are Outstatic blog posts saved
As Markdown files under outstatic/content/posts/ (or your collection name), one file per document, with metadata.json beside them indexing titles and slugs. Create or edit in the /outstatic dashboard and the change commits to GitHub.
does Outstatic need a database
No. Content is files in your repo and auth is GitHub (plus an optional Pro project key for hosted AI and team features). Back up by pushing the repo. There is nothing else to dump.
Notice an outdated path? Let us know.