Where Does Wails Store Config and Output?
Wails wails.json config plus frontend and build output inside your project on each OS.
Last updated
Wails keeps config in wails.json at the project root. Frontend code lives in frontend, Go bindings beside it, and built apps land in build/bin.
There is no per user config. The project folder is portable. Moving machines needs only the repo plus Go and Node toolchains. This mirrors Tauri style layouts.
Where Wails stores this, by platform
[ProjectDir]\wails.json
Config at root, output in [ProjectDir]\build\bin\. Delete build to force a clean package. Keep wails.json plus go.mod and frontend sources in git.
[ProjectDir]/wails.json
Same in-folder layout. App bundles form under build/bin on wails build. Moving between Mac and PC needs only toolchain reinstall.
[ProjectDir]/wails.json
Same arrangement. System webkit deps install separately; project files stay self contained. Exclude build from version control.
Frequently asked questions
Where is the built Wails app?
In build/bin under the project root after wails build. That output is disposable. Source is wails.json plus frontend and Go files.
Which Wails files belong in git?
Commit wails.json, go.mod, frontend and app sources. Ignore build and node_modules. A fresh clone plus deps reproduces the app.
Notice an outdated path? Let us know.