cdb-converter

cdb-converter

Convert Pro Cycling Manager CDB database files to and from SQLite, straight from the command line or your own code. Lightweight, isomorphic (Node.js and the browser), and zero-configuration.

The conversion is lossless: a full cdb → sqlite → cdb round-trip preserves every table, column, data type, and flag — so you can edit a save in any SQLite tool and load it back into the game.

Based on agfor/pcmdbedit — many thanks to agfor for the foundational work.

Contents

• Features
• Getting started
• Command line
• Library usage
  • CDB to SQLite
  • SQLite to CDB
  • Compression
  • Browser
• API reference
• Supported data types
• How metadata is preserved
• Compatibility
• Performance & size
• Samples

Features

• CDB SQLite — convert between the binary CDB format and standard SQLite databases.
• CLI included — convert files without writing any code; direction is auto-detected.
• Lossless round-trip — table flags, column order, and data types survive an export/reopen cycle.
• Isomorphic — runs in Node.js and in the browser via sql.js.
• Lightweight — the library's own code is ~28 kB, with only pako and sql.js as dependencies.
• TypeScript-first — native type definitions and full IDE support.
• Tree-shakeable — pure functions, no side effects, ESM + CommonJS builds.

Getting started

npm install cdb-converter

Requires Node.js 22 or newer. In the browser, sql.js loads its WebAssembly runtime on demand.

The fastest way to try it is the CLI:

npx cdb-converter save.cdb

Command line

The package ships a cdb-converter command. The conversion direction is auto-detected from the input file extension.

# CDB → SQLite (default output: save.sqlite)
npx cdb-converter save.cdb

# SQLite → CDB (default output: save.cdb)
npx cdb-converter save.sqlite

# Provide an explicit output path (directories are created as needed)
npx cdb-converter save.cdb data/save.sqlite

# Help / version
npx cdb-converter --help
npx cdb-converter --version

Input extension	Direction	Default output
.cdb	CDB → SQLite	<input>.sqlite
.sqlite / .db	SQLite → CDB	<input>.cdb

Library usage

CDB to SQLite

import fs from "node:fs";
import initSqlJs from "sql.js";
import { cdbToSql } from "cdb-converter";

const SQL = await initSqlJs();

// Read and convert a CDB file
const cdbBuffer = fs.readFileSync("save.cdb");
const db = cdbToSql(cdbBuffer, SQL);

// Query it like any SQLite database
const result = db.exec("SELECT * FROM Teams LIMIT 5");
console.log(result[0].values);

// Export to a .sqlite file
fs.writeFileSync("save.sqlite", db.export());

You must pass the initialized sql.js module returned by initSqlJs(). This library does not initialize sql.js for you: that setup is asynchronous and environment-specific (the caller decides how the wasm file is loaded in Node.js or the browser).

SQLite to CDB

import fs from "node:fs";
import initSqlJs from "sql.js";
import { sqlToCdb } from "cdb-converter";

const SQL = await initSqlJs();

// Load a SQLite database and convert back to CDB
const sqliteBuffer = fs.readFileSync("save.sqlite");
const db = new SQL.Database(sqliteBuffer);

const cdbBuffer = sqlToCdb(db); // automatically compressed
fs.writeFileSync("save.cdb", Buffer.from(cdbBuffer));

Compression

The library handles CDB compression (zlib deflate) transparently, but the helpers are exposed if you need them directly:

import { compressCdb, decompressCdb } from "cdb-converter";

const compressed = compressCdb(cdbData);
const decompressed = decompressCdb(compressed); // accepts compressed or raw input

Browser

<script src="https://cdn.jsdelivr.net/npm/sql.js@1.14.1/dist/sql-wasm.js"></script>
<script type="module">
  import { cdbToSql } from "https://cdn.jsdelivr.net/npm/cdb-converter/+esm";

  const SQL = await initSqlJs({
    locateFile: (file) =>
      `https://cdn.jsdelivr.net/npm/sql.js@1.14.1/dist/${file}`,
  });

  // Read a CDB from a file input
  const file = document.getElementById("cdb-input").files[0];
  const cdbBuffer = await file.arrayBuffer();

  const db = cdbToSql(cdbBuffer, SQL);
  console.log(db.exec("SELECT * FROM sqlite_master WHERE type='table'"));
</script>

API reference

cdbToSql(cdbBuffer, SQL): Database

Convert CDB binary data into a SQLite database instance.

• cdbBuffer — ArrayBuffer | Uint8Array, raw CDB data (compressed or uncompressed).
• SQL — SqlJsStatic, the module returned by initSqlJs().
• returns — a sql.js Database with the CDB tables loaded.

sqlToCdb(db): ArrayBuffer

Convert a SQLite database back to CDB binary format (automatically compressed).

• db — a sql.js Database instance.
• returns — compressed CDB binary data as an ArrayBuffer.

compressCdb(data): ArrayBuffer

Compress CDB data using zlib deflate. Accepts ArrayBuffer | Uint8Array.

decompressCdb(data): ArrayBuffer

Decompress CDB data, transparently handling both compressed and already-uncompressed input.

Lower-level building blocks (CDBReader, CDBWriter), enums (ChunkType, DataType, Magic), and all TypeScript types are also exported from the package root.

Supported data types

Every CDB data type is preserved during conversion:

Type	Description	Example
INTEGER	32-bit signed	42
FLOAT	IEEE 754 float32	3.14
STRING	UTF-8 text	"cyclist"
BOOLEAN	Bit-packed	true / false
INTEGER_BYTE	8-bit signed	-128 to 127
INTEGER_SHORT	16-bit unsigned	0 to 65535
FLOAT_LIST	Array of floats	(1.5,2.3,3.7)
INTEGER_LIST	Array of integers	(10,20,30)

How metadata is preserved

The library uses a special DB_STRUCTURE table to round-trip CDB metadata that has no native SQLite equivalent:

CREATE TABLE DB_STRUCTURE (
  TableName TEXT '274',
  ID INTEGER,
  Flags INTEGER
)

Each table's flags (their exact meaning is unknown but must be preserved) are stored in the Flags column, so they are written into the .sqlite file itself and survive an export()/reopen cycle. Column indices and data types are encoded into each column's declared type annotation. Together this makes cdb → sqlite → cdb lossless even when the SQLite database is saved to disk and reopened in a separate process.

Compatibility

The CDB parser is format-driven, not version-specific, so it is not tied to a single Pro Cycling Manager release. Lossless round-trip conversion (cdb → sqlite → cdb) is tested against the official databases of:

Version	Status
Pro Cycling Manager 2014	tested
Pro Cycling Manager 2018	tested
Pro Cycling Manager 2019	tested
Pro Cycling Manager 2021	tested
Pro Cycling Manager 2025	tested

Performance & size

A full cdb → sqlite → cdb round-trip on a real ~60k-row database stays well under half a second, and the library's own code adds only ~28 kB — the SQLite WASM runtime is the real weight, and you would pay for it with any SQLite-in-JS approach.

See bench/README.md for the full per-fixture numbers, the bundle breakdown, and how to reproduce them (npm run bench).

Samples

Runnable examples live in the samples folder:

• Browser — convert a .cdb file to SQLite directly in the browser.
• Node.js — CDB to SQLite — convert a .cdb file into a .sqlite file.
• Node.js — SQLite to CDB — convert a .sqlite or .db file back into a .cdb file.

License

MIT — see LICENSE for details.