Where Does the FTB App Store Instances?
Where the FTB App keeps modpack instances and saves on each desktop OS.
Last updated
The FTB App stores modpack instances under a data root per OS, with each instance self-contained: mods, saves, configs, and loader files together. The settings page shows the live root, which overrides any documented default.
Back up at instance granularity. The root also holds caches and runtimes worth skipping. Exact folder names shift between app generations, so trust the in-app path over a guide when they disagree.
Where FTB App stores this, by platform
%LOCALAPPDATA%\.ftb-app-data\instances\
Instances with saves/ and mods/ inside each. Confirm the live root in app settings; custom locations override this default.
~/Library/Application Support/.ftb-app-data/instances/
Same instances layout. Exact root may vary by app generation; the settings page stays authoritative.
~/.ftb-app-data/instances/
Same layout under home. Check settings for custom roots, common on multi-drive setups.
Frequently asked questions
How do I confirm my FTB instance path?
Open the app settings and check the instance location entry; the defaults below apply unless changed. Each instance folder holds saves, mods, and configs. Check there before assuming, since custom roots are common.
Where are saves inside an instance?
Saves nest inside each instance (saves/ beside mods/ and config/). Copy the instance folder to back it up. Keep loader versions matched; the app resolves those per instance on launch.
Notice an outdated path? Let us know.