Where Does Hoppscotch Store Data and Config?
Hoppscotch desktop app data folders on each OS and the env file for self-hosted backend install use.
Last updated
Hoppscotch splits state between desktop and backend. Desktop apps keep history and settings in per OS user data folders. Windows uses %APPDATA%\hoppscotch, macOS uses Application Support, Linux uses ~/.config/hoppscotch.
Self-hosted backends keep shared collections in Postgres with settings in a .env file. The env file holds secrets beside compose. Back up JSON exports for desktop use and env plus database for backend moves. Desktop state resets safely. Team workspaces sync through the backend database.
Where Hoppscotch stores this, by platform
%APPDATA%\hoppscotch
Desktop history and settings for the Windows app. Collections export as JSON for sharing. Delete to reset local state with the app closed.
~/Library/Application Support/hoppscotch
Same internal layout as Windows. Linux uses ~/.config/hoppscotch instead. Backend data lives in Postgres, not here.
.env (Hoppscotch compose dir)
Backend secrets and database URLs for Docker installs. Keep a copy off the server. Rebuilding with fresh secrets breaks sessions.
Frequently asked questions
how do i back up Hoppscotch collections
Export collections as JSON from the app and commit them. Desktop state lives in per OS app data folders. Self-hosted backends keep shared data in Postgres. JSON exports travel best.
what do i back up for self-hosted Hoppscotch
Copy the .env file with a Postgres dump for backend installs. The env holds secrets and mail settings. Desktop apps need no server backup since data stays local.
Notice an outdated path? Let us know.