Choose the scope
First choose Source data or Combined data. Then select one or more leagues and optionally include teams that are not assigned to a league. Teams belonging to the selected leagues and all players belonging to the included teams are added automatically.
Choose the columns
Select at least one field for leagues, teams, and players, then choose the identifier written to JSON and CSV. Exported names use letters, numbers, and underscores, start with a letter or underscore, and stay unique within each entity.
Choose visibility separately with the built-in Default or Full preset. Choose names with the built-in Camel case or Snake case preset; for example, countryCode2 becomes country_code_2 in Snake case. Global settings → Export lets you clone and save custom presets in either family.
A field-name preset defines every exportable field, including fields hidden by the current visibility preset. Names must be unique case-insensitively within each entity and cannot use players, sources, sourceNames, or sourceIds because export formats reserve those keys.
While editing, the visibility and field-name choices remain independent. Each selector independently shows Custom (modified), and returns to a saved preset name whenever its complete configuration matches again. A successful export remembers the exact configuration even when it is not saved as a named preset.
Choose one of three layouts
JSON writes normalized league, team, and player arrays to three files. Single JSON writes snapshot.json with portable project metadata, selected leagues at the root, and players nested under their teams. CSV writes three UTF-8 tables with stable headers, CRLF rows, and RFC 4180 escaping.
Combined data JSON records include a sources collection. Combined data CSV exports flatten aligned provider names and source IDs into provenance columns.
Reuse the last successful setup
The destination folder is remembered when you choose it. After files are exported successfully, QDB Downloader also stores the selected Source or Combined dataset, output format, visible columns, and output field names. These application-wide choices are restored when Export is opened from any project.
League selections and the Include teams without a league choice are rebuilt from the active project and are not remembered. A failed export does not replace the last successful configuration. If restored columns or field names no longer match a named preset, the corresponding selector shows Custom (modified).
Create and open the export
Review the destination, format, scope, and columns. QDB Downloader creates a collision-safe folder from the project name, reference date, and timestamp, then offers to open it when writing succeeds.
An entity with no matching records produces an empty JSON array or a header-only CSV; Single JSON always keeps its project, leagues, and teams structure.