- Supported games
- FIFA 11–23
- Platform
- Windows x64
- Input formats
- Text folder or t3db + XML
- Output format
- DB Master text folder
01 · Import
Make a managed source snapshot
Choose one or more DB Master-compatible text folders, or pair a PC format-8 t3db database with its matching metadata XML. QDB Converter inspects the schema and identifies compatible FIFA editions before any managed copy is created.
Every selected source must pass structural and data validation. Imported snapshots live in application-owned storage; the source folder, database, and XML remain untouched.
02 · Manage
Keep source and converted datasets separate
Browse, search, filter, sort, inspect, rename, validate, and remove imported and converted datasets from their separate libraries. Saved column visibility and ordering keep both tables focused on the information you use.
03 · Convert
Build against the target schema
Select an imported dataset and a FIFA 11–23 target. The conversion engine includes every source table supported by the target, orders fields by the target schema, substitutes target defaults for unusable values, and creates an independent managed result.
04 · Dataset tools
Validate, optimize player names, and export
Run validation on either library at any time. Inspect player-name ID ranges, close holes, repair out-of-range integer IDs, remove unused names, or combine both operations, then overwrite the selected managed snapshot or create a new Converted result. Export remains the path to an external folder.
Security
Filesystem access stays in Electron
The Angular renderer has no Node.js or direct filesystem access. A typed preload bridge exposes only dataset operations, while Electron validates requests and runs inspection, import, validation, conversion, and Playernames work outside the renderer.