CLI

Format identification

File system identification

To identify files from the command line, run droid with a list of files or folders to process:

droid "C:\Files\A Folder" "C:\Files\A File"

This will output the results of identification as Comma Separated Values (CSV) directly to the console. This is equivalent to using the -a option - add resources for identification. However, you don't need to specify -a unless you want to be explicit.

droid -a "C:\Files\A Folder" "C:\Files\A File"

If you want to output to JSON instead of CSV, set the --json flag on any command.

droid -a "C:\Files\A Folder" "C:\Files\A File" --json

If you want to process sub-folders and the files inside them, specify the -R option to recurse into sub-folders:

droid "C:\Files\A Folder" "C:\Files\A File" -R

S3 identification

DROID will identify files from an AWS S3 bucket.

You will need credentials to the bucket you are trying to access, and you will need a profile set up with a configured region matching the region of your bucket

There is AWS documentation on configuring profiles

Your credentials must have at least the s3:GetObject permission for the bucket you are trying to access. For more information, see the AWS documentation on S3 permissions.

S3 doesn't store folder information. Every object in a bucket has a single path, although the S3 UI will split this into folders if the path contains a /

Given the following objects in S3


          /folder1/object.txt
          /folder1/object.pdf
          /folder11/object.csv
          /folder2/object.docx
          /folder3/object.xlsx

This would be rendered on a traditional file system like this:


          ├── folder1
          │   ├── object.pdf
          │   └── object.txt
          ├── folder11
          │   └── object.csv
          ├── folder2
          │   └── object.docx
          └── folder3
          └── object.xlsx

S3 works on object prefixes. You make a request using an s3 object url which has the form s3://{bucket}/{path} This command:


          droid s3://bucket.name/folder

will return


          /folder1/object.txt
          /folder1/object.pdf
          /folder11/object.csv
          /folder2/object.docx
          /folder3/object.xlsx

Every object has the prefix /folder This command:

droid s3://bucket.name/folder1

will return


          /folder1/object.txt
          /folder1/object.pdf
          /folder11/object.csv

These commands:

droid s3://bucket.name/folder1/ droid s3://bucket.name/folder1/object

will both return


          /folder1/object.txt
          /folder1/object.pdf

All options relating to output format and container expansion will work with the S3 identification

HTTP(S) Identification

HTTP format identification is simpler than S3 identification. It is not possible to generically get a list of files from a URL prefix so HTTP identification only works on individual files.

droid http://example.com/file1

droid https://example.com/file1

All options relating to output format and container expansion will work with the HTTP identification

Writing results

Writing to a file

To output the CSV results to a file rather than the console, you can use the -o option:

droid "C:\Files\A Folder" "C:\Files\A File" -R -o "C:\Results\identifications.csv"

Note: if you specify "stdout" as the filename for the -o option, it will also write to the console. But it's easier to simply not specify the -o option.

To output results as JSON instead of CSV, you can use the --json option:

droid "C:\Files\A Folder" "C:\Files\A File" -R -o "C:\Results\identifications.json" --json

Writing to a database

To output the identification results to a profile database (which can be loaded in the DROID graphical user interface), use the -p option:

droid "C:\Files\A Folder" "C:\Files\A File" -R -p "C:\Results\identifications.droid"

If you don't want to see DROID log messages to the console, you can use quiet mode: -q:

droid "C:\Files\A Folder" "C:\Files\A File" -R -p "C:\Results\identifications.droid" -q

If you want to keep exploring the results of identifying files, saving the results to a database is the most flexible, as you can run different queries on it.

Filtering results

Filtering files to identify

If there are files you don't want to identify, then you can filter them out of identification, based on basic file metadata: file name, file size, file extension or the last modified date. Use the -ff (must meet all criteria) or -FF (must meet any criteria) options. For example:

droid "C:\Files\A Folder" "C:\Files\A File" -R -ff "file_size > 1000" "file_ext any txt pdf"

Note: filtering files does not filter out folders from the output, it only applies filtering criteria to which files to identify. If you want to only include files in the output (after filtering which files to identify), you can also specify a -f results filter as follows:

droid "C:\Files\A Folder" "C:\Files\A File" -R -ff "file_size > 1000" "file_ext any txt pdf" -f "type none folder"

The command above would only identify files whose file size was bigger than 1000 bytes, and whose file extensions are .txt or .pdf. Filtering files before they are identified (rather than afterwards) can speed up the process, particularly when processing inside archive files like zip, as DROID doesn't need to read the data inside the files.

There is another option to only process files with particular extensions, using the -Nx option:

droid "C:\Files\A Folder" "C:\Files\A File" -R -Nx txt pdf

The -Nx option was provided in earlier versions of DROID, before the more flexible file filtering options above were added, but it's still available.

Filtering results once identified

To filter out results from being written to a file or to the console after they have been identified, you can use the -f (must meet all criteria) or -F (must meet any criteria) options. Results can be filtered out on all available metadata, not just basic file metadata:

droid "C:\Files\A Folder" "C:\Files\A File" -R -f "puid any fmt/111 fmt/121 fmt/132 fmt/145" "format_count > 1"

Note: Specifying this option if writing to a database with the -p option will have no effect, as the database requires all identifications made to be written out. This is because the database can be in an inconsistent state otherwise, if folders or archive files are filtered out, but the children in them are still present. You can still filter a database after it has been saved using these options, but not during the file identification process itself. See Filtering Exports for more details.

List filtering options

To obtain a full list of the available filtering fields and operators, use the -k option, or see the Filtering Parameters Table:

droid -d

Configuring DROID

Specifying the signature files to use

DROID will use the default binary and container signature files (normally the last ones downloaded) to identify file formats. If you want to specify a different binary signature file, use the -Ns option, the -Nc option to specify a different container signature file, or both:

droid "C:\Files\A Folder" "C:\Files\A File" -R -Ns "C:\Signatures\binarysig.xml" -Nc "C:\Signatures\containersig.xml"

Specifying which archive types to process

DROID can look inside many different types of archive file to identify their contents. It will use the default settings for which archive types to process. You can override the defaults at the command line using the following options:

-A Open all archive types (zip, gzip, 7zip, bzip2, tar, rar, iso, fat)
-W Open all web archive types (arc, warc)

droid "C:\Files\A Folder" "C:\Files\A File" -R -A -W

You can also specify individual archive types you want to process using -At and -Wt, followed by the types you want to process. Any not specified will not be processed:

droid "C:\Files\A Folder" "C:\Files\A File" -R -At zip 7zip -Wt warc

If you don't want to expand any archive types, then just use the -At or -Wt options with no archive types specified.

Specifying profile properties

For full control over the profile properties used when identifying files, you can use the -Pr option:

droid "C:\Files\A Folder" "C:\Files\A File" -R -Pr "maxBytesToScan=10000" "matchAllExtensions=true"

If you have a common set of properties you want to apply each time, you can place them in a text file, and use the -Pf option to specify the property file to use:

droid "C:\Files\A Folder" "C:\Files\A File" -R -Pf "C:\Config\config.properties"

Note: When specifying properties in a property file, each property must have the prefix "profile.". For example:

profile.maxBytesToScan=10000 profile.matchAllExtensions=true

You can also combine the -Pr and -Pf options on the command line. In this case, properties specified on the command line directly will take precedence over those in the file, if the same property is specified in both.

A complete list of profile properties can be found in the profile property table.

No profile Mode

This version of DROID allows identification results to be written directly to a file or the console, not only a profile database. In prior versions, "No Profile Mode" gave a more limited capability that wrote only the name and PUID of identifications straight to the console. It did not identify files in exactly the same way as the other identification modes and had various other limitations.

This mode is retained in DROID for backwards compatibility, but it is now re-implemented to use standard identification code. The output will not be completely identical to the previous mode, but will be more accurate and in-line with all other identification modes. Differences include:

If a file name contains a comma, it will be quoted with double quotes.
Extension filtering with -Nx will also work inside archive files, not only on files in the file system.
You do not have to specify signature files - it will use the normal defaults if you do not.

It can be run using the -Nr option:

droid -Nr "C:\Files\A Folder" "C:\Files\A File" -R -Ns "C:\Signatures\binarysig.xml" -Nc "C:\Signatures\containersig.xml"

In general, there is little reason to use this mode unless it is required for backwards compatibility with existing scripts. The standard identification mode writing to the console or file gives much greater control over the output and configuration.

Configuring output

You can configure how DROID will output Comma Separated Values (CSV) or JSON to either the console or a file. These options will work either when outputting during format identification, or when exporting a saved profile.

Writing a row per file or per identification

By default, DROID will write out a single row for each file identified. If there is more than one identification, then additional columns will be added to the row for each identification. You can write out a row for each identification instead, using the -ri option. Where more than one identification for a file exists, there will be multiple rows for the same file, with a different identification:

droid "C:\Files\A Folder" "C:\Files\A File" -ri

To output as JSON, use the --json flag.

droid "C:\Files\A Folder" "C:\Files\A File" -ri --json

Quoting CSV fields

By default, all fields written will be quoted inside double quotes. If you only want quotes when a field value contains a comma, use the -qc option:

droid "C:\Files\A Folder" "C:\Files\A File" -qc

Choosing which columns to write

You can configure which columns are written out using the -co option. For example:

droid "C:\Files\A Folder" "C:\Files\A File" -co FILE_PATH NAME METHOD PUID

A list of all valid column headers can be found in the Column Name table

Working with saved profiles

If you have a database profile created using the -p option on the command line, or created with the GUI interface of DROID you can export the information in the database as CSV, or create reports on it from the command line. By convention, DROID database profiles have the file extension ".droid".

To work with previously saved profiles, we again use the -p option to specify where the profile files are to be loaded from. You can specify more than one profile when working with saved profiles.

Exporting profiles

To export one or more profiles to a file, use the -e or -E options. To write out one row for each file, use the -e option. If a file has multiple identifications, they will be added as additional entries in the file. To write out one row per format identification, use the -E option. If a file has multiple identifications, then there will be more than one row for that file, with different format identifications. For example:

droid -p "C:\Results\myprofile1.droid" "C:\Results\myprofile2.droid" -e "C:\Exports\myprofiles.csv"

If you want to output as JSON, pass the --json flag.

droid -p "C:\Results\myprofile1.droid" "C:\Results\myprofile2.droid" -e "C:\Exports\myprofiles.json" --json

If you want to export directly to the console, not to a file, simply don't specify a file name after the -e or -E options:

droid -p "C:\Results\myprofile1.droid" "C:\Results\myprofile2.droid" -e

If you want to export a subset of columns, simply specify a space separated list of those columns after the -co option:

droid -p "C:\Results\myprofile1.droid" -e "C:\Exports\myprofiles.csv" -co FILE_PATH STATUS HASH PUID

If you have defined an export template, simply specify the absolute path to the export template after the -et option:

droid -p "C:\Results\myprofile1.droid" -e "C:\Exports\myprofiles.csv" -et "C:\Templates\MyExport.template"

A final option for export is to control whether a Byte Order Mark (BOM) is written at the beginning of the file. To write a BOM, use the -B option:

droid -p "C:\Results\myprofile1.droid" "C:\Results\myprofile2.droid" -e "C:\Exports\myprofiles.csv" -B

Filtering exports

If you want to filter what is exported from saved profiles to the CSV file, use the -f option to specify a filter in which all filter criteria must be met, or -F to specify a filter where any of the filter criteria must be met. For example:

droid -p "C:\Results\myprofile1.droid" "C:\Results\myprofile2.droid" -E "C:\Exports\myprofiles.csv" -F "file_size > 100000" "puid any fmt/110 fmt/111 fmt/112"

To obtain a full list of the available filtering fields and operators, use the -k option, or see the Filtering Parameters Table

Reporting on saved profiles

To generate a report on one or more saved profiles, use the -n option to select the report to run, and the -r option to specify the filename to write the report to:

droid –p "C:\Results\result1.droid" –n "File count and sizes" –r "C:\Reports\result1Report.pdf"

This command would load the profile from the "C:\Results\result1.droid" file, run the "File count and sizes" report, and save the results to a PDF file:" C:\Reports\result1Report.pdf

To obtain a list of available reports on the command line, use the -l option, or see Available reports.

droid -l

By default, reports are saved as PDF files. You can change the type of the report written using the -t option:

droid –p "C:\Results\result1.droid" –n "Comprehensive breakdown" -t "Planets XML" –r "C:\Reports\result1Report.xml"

See output file formats for a list of report output formats.

Note: The "Comprehensive Breakdown" report has a special output type: "Planets XML" which writes out the results of identification in the Planets XML format.

Filtering reports

To generate a filtered report on one or more saved profiles, use the -f option to filter on all criteria, or the -F option to filter on any criteria:

droid –p  C:\Results\result1.droid
          –n  File count and sizes  -t "DROID Report XML" –r  C:\Reports\result1Report.xml  -F "format_count > 2" "file_ext any pdf txt doc"

To obtain a full list of the available filtering fields and operators, use the -k option, or see the Filtering Parameters Table

Signature management

Check for signature updates

To check for any signature updates, without downloading them, use the -c option:

droid -c

Download the latest signatures

To download any available signature updates, use the -d option:

droid -d

List available signatures

To list all the signatures registered with DROID, use the -X option:

droid -X

To list the default signatures a profile will use, unless overridden, use the -x option:

droid -x

Configure the default signatures

Sets the current default signature file version. For example:

droid -s 120

This would set the DROID signature file version 120 - a binary signature - as the default. If we instead specified the version number of a container signature, then the container signature default would be set instead. The version numbers of all installed signatures can be obtained using the list signature command.

Reference tables

Field fields and operators

The fields which can be filtered on, and the operators that can be applied to them, are:

Field	Description	Operators	Examples
file_name	The filename of the file. The value to compare with must be surrounded with single quotes.	=>, starts, ends, contains, not starts, not ends, not contains	file_name starts 'Invoice' file_name = 'xxx' file_name not contains 'temp'
file_size	The size of a file in bytes.	<, <=, =, <>, >, >=	file_size > 100000 file_size <= 99999
file_ext	The file extension of the file name	=, <>, any, none	file_ext = bmp file_ext none tmp temp ignore
last_modified	The date/time on which the file was last modified ( yyyy-MM-dd )	<, <=, =, <>, >, >=	last_modified < 2020-01-31 last_modified >= 2000-01-01
format_count	The number of format identifications made	<, <=, =, <>, >, >=	format_count > 2 format_count = 1
type	The type of resource ( file \| folder \| container )	any, none	type none folder type any file container
status	The identification job status ( not_done \| done \| access_denied \| not_found \| error )	any, none	status none done status any access_denied not_found error
method	How the file was identified ( extension \| signature \| container )	any, none	method none extension method any signature container
format_name	The file format description (text)	=, <>, starts, ends, contains, not starts, not ends, not contains	format_name contains Microsoft format_name not starts Adobe
puid	The PUID identified (e.g. x-fmt/101)	any, none	puid any fmt/111 fmt/112 fmt/113 fmt/114 fmt/115 puid none fmt/245 fmt/235 fmt/222
mime_type	The mime-type of the identification	any, none	mime_type any text/plain text/html mime_type none image/tiff image/jpeg image/gif
extension_mismatch	Whether or not there is a mismatch between the PRONOM Unique Identifier and the file extension	=, <>	extension_mismatch=true extension_mismatch=false

Note: If you want to filter on a list of values using any or none, and a value contains a space, then you can quote the value using single quotes.

Profile properties table

This table describes the properties which can be set using the -Pr options. If these properties are recorded in a file to use with the -Pf option, each property must be prefixed by "profile.". For example, "profile.maxBytesToScan=4096". If specifying directly on the command line with the -Pr option, you don't have to specify .profile in front of each (although you can if you wish).

Property	Value	Description	Notes
maxBytesToScan	Number	The maximum number of bytes DROID scans at the start and end of each file it attempts to identify.	Set to 65536 by default. If it is set to a negative number, DROID will scan the entire file.
matchAllExtensions	true/false	Whether to match extensions even if a better signature-based identification exists.	If matches are made on extensions when there are better options, there may be more erroneous identifications.
defaultBinarySigFileVersion	Filename	The filename of a binary signature to use to identify formats.	The binary signature file already exist in the standard path where binary signatures are stored by DROID.
defaultContainerSigFileVersion	Filename	The filename of a container signature to use to identify formats.	The container signature file already exist in the standard path where binary signatures are stored by DROID.
processTar	true/false	Whether to identify files inside tar files.	This is similar to the -At tar option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processZip	true/false	Whether to identify files inside zip files.	This is similar to the -At zip option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processGzip	true/false	Whether to identify files inside gzip files.	This is similar to the -At gzip option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processRar	true/false	Whether to identify files inside rar files.	This is similar to the -At rar option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
process7zip	true/false	Whether to identify files inside tar files.	This is similar to the -At tar option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processIso	true/false	Whether to identify files inside iso files.	This is similar to the -At iso option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processBzip2	true/false	Whether to identify files inside bzip2 files.	This is similar to the -At bzip2 option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processArc	true/false	Whether to identify files inside arc files.	This is similar to the -Wt arc option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
processWarc	true/false	Whether to identify files inside warc files.	This is similar to the -Wt warc option, but this will only turn on or off processing for this type; not turn off other types of archive processing.
generateHash	true/false	Whether to generate a hash for each file processed.	Generating hashes forces another scan of each file, so it affects performance. Only turn this on if you need hash values.
hashAlgorithm	String	The hash algorithm to use if generating hashes.	Values can be md5, sha1 or sha256
defaultThrottle	Number	A delay in milliseconds between processing each file.	This can help to minimise the impact of DROID scanning a large volume of files, although it will make the results take longer to obtain.

Column names

This table describes the columns which can be written out, configurable using the -co option:

Column	Description
ID	A unique id for each resource identified.
PARENT_ID	The id of the parent resource
URI	A URI for the resource, including locations inside archive files.
FILE_PATH	The path to the resource in the file system
NAME	The name of the resource
METHOD	The method used to identify the resource.
STATUS	The identification status of the resource.
SIZE	The size in bytes of the resource.
TYPE	The type of the resource
EXT	The file extension of the resource
LAST_MODIFIED	The last modified date/time of the resource.
EXTENSION_MISMATCH	Whether there is a mismatch between the extension of the resource and its identification by signature
HASH	The hash value of the resource.
FORMAT_COUNT	The number of identifications made to the resource.
PUID	The PRONOM Unique Identifier of the resource, which identifies the format
MIME_TYPE	The mime type of the resource where known.
FORMAT_NAME	The name of the format the resource was identified as
FORMAT_VERSION	The version of the format the resource was identified as

Command options

This table lists all the command line options available:

Short name	Long name	Parameters	Description	Example
-h	--help	{none}	Prints the command line option help to the console.	droid -h
-v	--version	{none}	Prints the version of DROID to the console.	droid -v
-a	--profile-resources	One or more quoted paths to files and folders	Adds the resources listed to a profile for identification and runs identification. If not specified, DROID assumes any unbound parameters are -a options, so writing -a is optional.	droid -a "C:\Files\" "C:\More\spreadsheet.xls"
-R	--recurse	{none}	Processes all sub-folders and the files and folders within them, recursively.	droid "C:\Files\" "C:\More\spreadsheet.xls" -R
-q	--quiet	{none}	Suppresses log messages and other metadata sent to the console.	droid "C:\Files\" "C:\More\spreadsheet.xls" -q
-o	--output-file	Quoted path to the CSV file to write to.	Writes identification results out to a CSV file, instead of to the console	droid "C:\Files\" "C:\More\spreadsheet.xls" -o "C:\Results\myresults.csv"
-p	--profile(s)	One or more quoted paths to database files (.droid)	When used with the -a option, this specifies a single profile .droid file to write to. When used with exporting and reporting options, it specifies one or more profiles to load.	droid "C:\Files\" "C:\More\spreadsheet.xls" -p "C:\Results\myresults.droid" droid -p "C:\Results\myresults.droid" "C:\Results\myresults2.droid" -E "C:\Exports\export.csv"
-ff	--filter-all-file	One or more quoted filter criteria.	Filters out files before any identification is made. Only file name, file size, file extensions or last modified date can be filtered with this option. All filter criteria specified must be fulfilled to pass the filter. This can increase performance, as opposed to filtering results after identification is made (see -f option). It can be used when writing to CSV or to a profile database.	droid "C:\Files\" "C:\More\spreadsheet.xls" -ff "file_size > 1000" "file_ext any jpg bmp txt"
-FF	--filter-any-file	One or more quoted filter criteria.	Filters out files before any identification is made. Only file name, file size, file extensions or last modified date can be filtered with this option. At least one filter criteria specified must be fulfilled to pass the filter. This can increase performance, as opposed to filtering results after identification is made (see -F option). It can be used when writing to CSV or to a profile database.	droid "C:\Files\" "C:\More\spreadsheet.xls" -FF "file_size > 1000" "file_ext any jpg bmp txt"
-Nx	--extension-list	One or more file extensions.	Filters out files to identify based on a list of file extensions. This is equivalent to using the -ff or -FF options above, which are more flexible. It is now provided only for backwards compatibility.	droid "C:\Files\" "C:\More\spreadsheet.xls" -Nx jpg bmp txt
-f	--filter-all	One or more quoted filter criteria.	Filters out files from the results when exporting or reporting on previously saved profiles, or outputting to CSV. All filter criteria must be met to pass the filter. Note: it cannot filter out results while writing to a database (-a with -p option) as the database could end up in an inconsistent state.	droid -p "C:\Results\myresults.droid" "C:\Results\myresults2.droid" -E "C:\Exports\export.csv" -f "file_size > 1000" "file_ext any jpg bmp txt" droid "C:\Files\" "C:\More\spreadsheet.xls" -f "file_size > 1000" "file_ext any jpg bmp txt"
-F	--filter-any	One or more quoted filter criteria.	Filters out files from the results when exporting or reporting on previously saved profiles, or outputting to CSV. At least one filter criteria must be met to pass the filter. Note: it cannot filter out results while writing to a database (-a with -p option) as the database could end up in an inconsistent state.	droid -p "C:\Results\myresults.droid" "C:\Results\myresults2.droid" -E "C:\Exports\export.csv" -F "file_size > 1000" "file_ext any jpg bmp txt" droid "C:\Files\" "C:\More\spreadsheet.xls" -F "file_size > 1000" "file_ext any jpg bmp txt"
-Nr	--no-profile-resource	A quoted path to file or folder to scan.	Runs a simple profile outputting only the name and PUID to the console. Older versions of DROID also require the signature and container files to be specified using the -Ns and -Nc options.	droid -Nr “C:\Files\A Folder” -R
-Ns	--signature-file	A quoted path to a binary signature file.	Sets the binary signature file to use when identifying files for this profile run only.	droid “C:\Files\A Folder” "C:\Files\A File” -Ns "C:\Signatures\binarysig.xml"
-Nc	--container-file	A quoted path to a container signature file.	Sets the container signature file to use when identifying files for this profile run only.	droid “C:\Files\A Folder” "C:\Files\A File” -Nc "C:\Signatures\containersig.xml"
-A	--open-all-archives	{none}	Instructs DROID to open all archive types (zip, tar, gzip, rar, 7zip, bzip2, fat and iso)	droid “C:\Files\A Folder” "C:\Files\A File” -A
-W	--open-all-webarchives	{none}	Instructs DROID to open all web archive types (arc, warc)	droid “C:\Files\A Folder” "C:\Files\A File” -W
-At	--open-archive-types	One or more archive types	Instructs DROID to open only the archive types specified (zip, tar, gzip, rar, 7zip, bzip2, fat and iso)	droid “C:\Files\A Folder” "C:\Files\A File” -At zip gzip 7zip bzip2
-Wt	--open-webarchive-types	One or more web archive types	Instructs DROID to open only the web archive types specified (arc, warc) (	droid “C:\Files\A Folder” "C:\Files\A File” -Wt warc
-Pr	--profile-property	One or more profile properties.	Sets the properties that a profile is run with. These will override the default properties for a profile or those specified with the -Pf option.	droid “C:\Files\A Folder” "C:\Files\A File” -Pr "maxBytesToScan=100000" "matchAllExtensions=true"
-Pf	--property-file	A quoted path to a file containing properties.	Sets the properties contained in the property file specified for a profile run. Properties recorded in a file must have the prefix .profile before each property. These will override the default properties for a profile. If properties are also specified using the -Pr option, they will override any specified in the file.	droid “C:\Files\A Folder” "C:\Files\A File” -Pf "C:\Properties\config.properties"
-ri	--row-per-id	{none}	Specifies that CSV output should write a row for each identification made. If a file has more than one identification, then more than one row will be output for that file. The default for CSV output is to write a row for each file, with multiple identifications being written as additional columns.	droid “C:\Files\A Folder” "C:\Files\A File” -ri
-qc	--quote-commas	{none}	Specifies that CSV output should only quote fields that contain a comma. The default is for all fields to be quoted.	droid “C:\Files\A Folder” "C:\Files\A File” -qc
-co	--columns	One or more column names to output	Specifies that CSV output should only write the columns specified.	droid “C:\Files\A Folder” "C:\Files\A File” -co FILE_PATH STATUS HASH PUID
-et	--export-template	Absolute path to the export template	Specifies that CSV output should be written using the customisations defined in the Export Template.	droid “C:\Files\A Folder” "C:\Files\A File” -et "C:\Templates\MyExport.template"
-e	--export-file	A quoted file path to the CSV file to write.	Exports one or more profiles (specified with the -p option) to a CSV file, writing one row per file.	droid -p "C:\Results\profile1.droid" "C:\Results\profile2.droid" -e "C:\Exports\export.csv"
-E	--export-format	A quoted file path to the CSV file to write.	Exports one or more profiles (specified with the -p option) to a CSV file, writing one row per format identification.	droid -p "C:\Results\profile1.droid" "C:\Results\profile2.droid" -E "C:\Exports\export.csv"
-n	--report-name	A quoted report name	Specifies what report to run on profiles selected with the -p option, written to a file specified with the -r option.	droid –p “C:\Results\result1.droid” –n “File count and sizes” –r “C:\Reports\result1Report.pdf”
-r	--report	A quoted path to a file to write a report to.	Specifies the file that a report is written to.	droid –p “C:\Results\result1.droid” –n “File count and sizes” –r “C:\Reports\result1Report.pdf”
-l	--list-reports	{none}	Lists the available report names and the output formats which are supported for them.	droid -l
-t	--report-type	A quoted report type	Sets the type of report format to generate. By default, reports will be written as a PDF file. You can select either "PDF", "Text", "Web page", or "DROID Report XML". Some reports can have additional export options - the Comprehensive Breakdown report also supports the "Planets XML" format.	droid –p “C:\Results\result1.droid” –n “File count and sizes” –r “C:\Reports\result1Report.xml” -t "DROID Report XML"
-c	--check-signature-update	{none}	Checks for signature updates, without downloading them.	droid -c
-d	--download-signature-update	{none}	Downloads available signature updates.	droid -d
-X	--list-signature-files	{none}	Lists all locally available signature files.	droid -X
-x	--display-signature-file	{none}	Lists the current default signature files to use for identification.	droid -x
-s	--set-signature-file	A version number	Sets either a binary or container signature to be the default for its type from the locally available signatures, using its version number to identify it.	droid -s 97 droid
-json	--json-output	{none}	Sets the output to JSON. This will work for any command which outputs to console or to a file	droid C:\More\spreadsheet.xls --json