Bundled vs manifest-only
The Bundle Addons toggle is the most consequential choice. Manifest-only exports list the mods by their CurseForge or Modrinth IDs (and versions); whoever installs the pack has the launcher fetch the mods from the CDN. The file stays small (a few MB), the recipient needs internet to install.
Bundled exports include the actual mod JARs in the archive. The file can be installed offline (assuming Minecraft assets are already cached). Trade-off: the archive is much larger (hundreds of MB to a few GB), and you're effectively redistributing the mods themselves, so check the licenses before sharing publicly.
Picking a format
- GDLauncher .gdlpack: best fidelity for recipients who also use GDLauncher. Preserves the full instance shape including everything GDLauncher tracks.
- CurseForge .zip: portable to most launchers (CurseForge App, PrismLauncher, MultiMC, ATLauncher, Technic). Mods are referenced by CurseForge project IDs; mods only on Modrinth need the bundle toggle for inclusion.
- Modrinth .mrpack: portable to Modrinth-supporting launchers. Mods are referenced by direct download URLs and hashes.
What doesn't get exported
Your accounts, your launcher settings, your skin, and anything you didn't tick during the filter step. The export is the instance, not the launcher.
For sharing with another GDLauncher user
If your recipient also uses GDLauncher and you want a one-click flow, the Cloud Instance Sharing code feature is the better fit, see How to Share an Instance. Export is for archiving and for sending to people on other launchers.