Where Does DevPod Store Workspaces and Config?
DevPod keeps providers, contexts and workspace state in ~/.devpod, while code itself lives with the chosen provider.
Last updated
DevPod's home folder is the control plane: provider credentials, the default context, and metadata about every workspace you created. The actual code stays wherever the provider put it, locally in Docker or out on a cloud machine.
That split decides the backup. Copying ~/.devpod preserves your setup and workspace list, but recreating a workspace still pulls code fresh from Git. Secrets inside provider configs deserve care when sharing dotfiles.
Where DevPod stores this, by platform
~/.devpod
Providers, contexts and workspace metadata. Deleting a workspace through devpod delete cleans the provider side. Removing this folder forgets every workspace without touching their code.
~/.devpod
Same layout on Mac. Docker Desktop workspaces add disk usage inside Docker's own VM, which this folder does not cover. Reclaim that separately from Docker.
%USERPROFILE%\.devpod
Same role on Windows. Provider binaries and SSH keys referenced from here must exist at matching paths or workspaces fail to start.
Frequently asked questions
how do i move devpod to a new machine
Copy ~/.devpod across and reinstall providers with devpod provider add. Workspaces recreate from their Git repos. Re-enter provider credentials rather than copying secrets blindly.
where is my devpod workspace code actually stored
With the provider: Docker volumes or mounts for local workspaces, remote disks for cloud ones. ~/.devpod only records how to reach it, so look at the provider when code goes missing.
Notice an outdated path? Let us know.