storage

The following options are related to darktable’s library database and XMP sidecar files.

🔗database

check for database maintenance
Indicates when darktable should check for database fragmentation and perform maintenance. Options are “never”, “on startup”, “on close” and “on both”. Each of these is also available with an additional “(don’t ask)” option to perform the checks automatically without prompting (default “on close”).
database fragmentation ratio threshold
Fragmentation ratio (in per cent) above which database maintenance should be performed (subject to the selection made in the option above) (default 25).
create database snapshot
Specifies how often darktable should create database snapshots. Options are “never”, “once a month”, “once a week”, “once a day” and “on close” (default “once a week”)
how many snapshots to keep
Number of snapshots to keep after creating a new snapshot, not counting database backups taken when moving between darktable versions. Enter “-1” to store an unlimited number of snapshots. (default 10)

🔗xmp

write sidecar file for each image
XMP files provide a redundant method of saving the changes that you have made to an image, in addition to the changes saved to darktable’s database. This option allows you to choose when to write these files. Choose from:
  • never: Don’t write XMP files. This can be useful if you are running multiple version of darktable for development/testing purposes but is not normally recommended
  • on import: An XMP file will be written as soon as you add an image to darktable’s library and will be subsequently updated each time you edit it
  • after edit: An XMP file will be written the first time you perform an edit on an image and will be updated on each subsequent edit. Importing will not generate an XMP file by default.

It’s strongly recommended that you choose either “on import” or “after edit”. XMP files provide a useful fail-safe so that you don’t lose data if your database becomes corrupted. Backing up your raw file plus the accompanying XMP file will allow you to fully restore your work at a later date by re-importing your edit history back into darktable (default “on import”).

store xmp tags in compressed format
Entries in XMP tags can get rather large and may exceed the available space to store the history stack in some output files on export. This option allows binary XMP tags to be compressed in order to save space. Available options are “never”, “always”, and “only large entries” (default).
look for updated xmp files on startup
Scan all XMP files on startup and check if any have been updated in the meantime by some other software. If updated XMP files are found, a menu is opened for the user to choose which of the XMP files to reload (replacing darktable’s database entries by the XMP file contents) and which of the XMP to overwrite from darktable’s database. Activating this option also causes darktable to check for text sidecar files that have been added after import time (default off).