LinuxWindows

Where Does Scid vs PC Store Config and Databases?

Where Scid vs PC keeps options, engines and database files.

Last updated

Scid vs PC keeps config in .scidvspc/config on Linux and Mac with options.dat and engines.dat as the headline files. Windows installs instead use bin\config inside the program folder, mirrored through VirtualStore under Program Files.

Databases themselves are triplets (.si4 index, .sn4 names, .sg4 games) wherever you saved them. Options save on exit or via Options menu, so close cleanly before copying config between machines.

Where Scid vs PC stores this, by platform

Linux
~/.scidvspc/config/

Holds options.dat, engines.dat and books. Windows uses the install bin config path with VirtualStore mirroring instead. Copy the folder for upgrades. Databases (.si4/.sn4/.sg4) live wherever you saved them.

Windows
<Scid vs PC install>\bin\config\

Same config role inside the install tree. Expect UAC virtualization under Program Files. Prefer a user writable install path to dodge mirror confusion.

Frequently asked questions

Engines broke after upgrading Scid vs PC. How do I fix it?

Delete or edit engines.dat in the config folder. Upgrades often leave stale engine entries behind, and a clean engines file plus fresh setup beats debugging each line.

How do I migrate Scid vs PC settings?

Copy the whole config directory from the old install. The README blesses exactly this for upgrades: options.dat, engines.dat and opening books travel together.

Notice an outdated path? Let us know.