Where Does Decap CMS Store Config and Content?
Decap CMS is configured by admin/config.yml, with content and media living as files in the git repo itself.
Last updated
Decap CMS stores nothing of its own. The admin/config.yml file in your site repo declares the backend, the media folders, and every collection. Folder collections map to directories of Markdown files. File collections map to explicit single files like settings or an about page.
Media uploads commit into media_folder in the repo, while public_folder controls the src URLs the site serves. Since the repo is the database, branching and pull requests are the content workflow, and the CMS never needs a backup separate from git.
Where Decap CMS stores this, by platform
admin/config.yml
Declares backend, branch, media folders, and collections. Folder collections need a folder path, file collections need explicit file paths.
./images/uploads
Typical media home for root static generators. Match it to where your generator serves static files, and set public_folder to the served prefix.
Frequently asked questions
How do media_folder and public_folder differ?
Set media_folder for the repo path and public_folder for the served URL. Hugo style sites need static prefixed paths, while root static sites do not.
Folder or files collection for my content type?
Use a folder collection with a folder path for repeatable entries like posts, and a files collection with explicit file paths for one off pages.
Can Decap write to my local repo instead of GitHub?
Yes with local_backend for development. Production writes always commit to the hosted repo branch, even when you run the admin UI locally.
Notice an outdated path? Let us know.