The user needs to supply an input filename and an output filename. All other parameters are optional.
<inputfile>
The name of the input file to export.
<xmpfile>
The optional name of an XMP sidecar file containing the history stack data to be applied during
export. If this option is not given darktable will search for an XMP file that belongs to the given
input file.
<outputfile>
The name of the output file. darktable derives the export file format from the file extension. You
can also use all the variables available in darktable's export module in the output filename.
--width<maxwidth>
This optional parameter allows one to limit the width of the exported image to that number of pixels.
--height<maxheight>
This optional parameter allows one to limit the height of the exported image to that number of
pixels.
--bpp<bpp>
An optional parameter to define the bit depth of the exported image; allowed values depend on the
file format. Currently this option is not yet functional. If you need to define the bit depth you
need to use the following workaround:
--core --conf plugins/imageio/format/<FORMAT>/bpp=<VALUE>
where FORMAT is the name of the selected output format, for example png.
--hq<0|1|true|false>
A flag that defines whether to use high quality resampling during export. Defaults to true.
--upscale<0|1|true|false>
A flag that defines whether to allow upscaling during export. Defaults to false.
--export_masks<0|1|true|false>
A flag that defines whether masks used in the image will be stored as layers in the exported image
(provided the format supports it). Defaults to false.
--style<stylename>
Specify the name of a style to be applied during export. If a style is specified, the path to the
darktable configuration directory must also be specified (i.e. --core --configdir
~/.config/darktable). Defaults to no style specified.
--style-overwrite
The specified style overwrites the history stack instead of being appended to it.
--apply-custom-presets
With this option you can decide if darktable loads its set of default parameters from data.db and
applies them. Otherwise the defaults that ship with darktable are used.
Set this flag to false in order to run multiple instances.
--verbose
Enables verbose output.
--core<darktableoptions>
All command line parameters following --core are passed to the darktable core and handled as standard
parameters. See darktable(1) for a detailed description of the options.