Where Does GDLauncher Store Instances?
Where GDLauncher keeps Minecraft instances, mods, and Java runtimes on each desktop OS.
Last updated
GDLauncher keeps a data root per OS with instances, assets, and managed Java underneath. The app resolves mods and loaders per instance, so each folder is self-contained once downloaded.
Custom roots are common because Minecraft data grows fast. The settings page shows the live path, which matters more than any documented default. Back up instance folders rather than the whole root to skip re-downloadable assets.
Where GDLauncher stores this, by platform
%APPDATA%\gdlauncher_next\
Instances plus assets and runtimes underneath. Confirm in Settings; custom roots override this default. Avoid live-synced parents like OneDrive.
~/Library/Application Support/gdlauncher_next/
Same instances layout. Exact folder name may vary by GDLauncher generation (v1 versus v2); check Settings for the live root.
~/.config/gdlauncher_next/
Same layout under the XDG config home. Flatpak and AppImage builds may sandbox this; the in-app path stays authoritative.
Frequently asked questions
How do I confirm my GDLauncher data path?
Open Settings inside GDLauncher and look for the data path entry; the defaults below apply unless changed. Instances sit in a subfolder of that root. Check there before assuming, since custom roots are common on small SSDs.
Where are instance files inside it?
Each instance folder holds its mods, saves, configs, and loader version. Copy the instance folder to back it up. Do not nest the data root inside OneDrive or another live sync folder; locks corrupt downloads.
Notice an outdated path? Let us know.