Where Does VitePress Store Config and Output?
VitePress config in .vitepress, build output in dist, and cache in node_modules for docs sites.
Last updated
VitePress keeps everything inside your docs project. Config lives in .vitepress/config.*, content stays in Markdown beside it, and the built site lands in .vitepress/dist.
Cache sits in node_modules/.vite when the dev server runs. None of this is per user. Move the project folder and the whole site moves with it. This layout matches across OSes.
Where VitePress stores this, by platform
[SiteDir]\.vitepress\
Config, theme and dist output all under here. Delete .vitepress\dist and .vitepress\cache to force a clean build. Keep config.* in git; ignore dist.
[SiteDir]/.vitepress/
Same in-folder layout. Node modules and Vite cache stay under the project root. Moving between Mac and PC needs only a fresh npm install.
[SiteDir]/.vitepress/
Same arrangement. CI builds output to .vitepress/dist by default, so point your host at that folder. Exclude node_modules and dist from version control.
Frequently asked questions
Which VitePress files belong in git?
Keep Markdown, public assets and .vitepress/config plus theme files. Ignore node_modules, .vitepress/dist and .vitepress/cache. Dist is pure output and rebuilds on every deploy.
Where is the built VitePress site?
In .vitepress/dist under your docs root after running vitepress build. Serve or upload that folder. The dev server never writes it; only build does.
Notice an outdated path? Let us know.