Skip to main content

CLI Reference

Quickwit is a single binary that makes it easy to index and search structured or unstructured data from the command line. It consumes datasets consisting of newline-delimited JSON objects with arbitrary keys. It produces indexes that can be stored locally or remotely on an object storage such as Amazon S3 and queried with subsecond latency.

This page documents all the available commands, related options, and environment variables.


Before using Quickwit with an object storage, check out our advice for deploying on AWS S3 to avoid some nasty surprises at the end of the month.


Command-line synopsis syntax


quickwit or quickwit help displays the list of available commands.

quickwit help <command name> displays the documentation for the command and a usage example.

Note on telemetry#

Quickwit collects some anonymous usage data, you can disable it. When it's enabled you will see this output:

quickwit help
Quickwit 0.1.0
Quickwit, Inc. <>
Indexing your large dataset on object storage & making it searchable from the command line.
Telemetry enabled

The line Telemetry enabled disappears when you disable it.


quickwit --version displays the version. It is useful for reporting bugs.



Creates an index at index-uri configured by a json file located at index-config-path. The command fails if an index already exists at index-uri unless overwrite is passed. When overwrite is enabled, the command deletes all the files stored at index-uri before creating a new index. The index config defines how a document and fields it contains, are stored and indexed, see the index config documentation.


quickwit new
--index-uri <uri>
--index-config-path <path>


--index-uri (string) Defines the index location.
--index-config-path (string) Defines the index config path.
--overwrite (boolean) Overwrites existing index.


Creating a new index on local file system

quickwit new --index-uri file:///quickwit-indexes/catalog --index-config-path ~/quickwit-conf/index_config.json

Creating a new index on Amazon S3*

quickwit new --index-uri s3://quickwit-indexes/catalog --index_config-path ~/quickwit-conf/index_config.json

Replacing an existing index

quickwit new --index-uri s3://quickwit-indexes/catalog --index_config-path ~/quickwit-conf/index_config.json --overwrite

When creating an index on a local file system, absolute path is enforce. This implies that index-uri like file:///quickwit-indexes/catalog pertenains you have the required permissions on /quickwit-indexes/catalog.



Indexes a dataset consisting of newline-delimited JSON objects located at input-path or read from stdin. The data is appended to the target index specified by index-uri unless overwrite is passed. input-path can be a file or another command output piped into stdin. Currently, only local datasets are supported. By default, the process uses 4 threads and 1 GiB of memory per thread. The num-threads and heap-size options customize those settings.


quickwit index
--index-uri <uri>
[--input-path <path>]
[--num-thread <num threads>]
[--heap-size <num bytes>]


--index-uri (string) Location of the target index.
--input-path (string) Location of the source dataset.
--overwrite (boolean) Overwrites existing data.
--num-thread (integer) Number of allocated threads for the process.
--heap-size (integer) Amount of allocated memory for the process.
--temp-dir (string) Path of temporary directory for building the index (defaults to /tmp)


Indexing a local dataset

quickwit index --index-uri s3://quickwit-indexes/nginx --input-path nginx.json

Indexing a dataset from stdin

cat nginx.json | quickwit index --index-uri s3://quickwit-indexes/nginx
quickwit index --index-uri s3://quickwit-indexes/nginx < nginx.json

Reindexing a dataset

quickwit index --index-uri s3://quickwit-indexes/nginx --input-path nginx.json --overwrite

Customizing the resources allocated to the program

quickwit index --index-uri s3://quickwit-indexes/nginx --input-path nginx.json --num-threads 8 --heap-size 16GiB



Searches the index stored at index-uri and returns the documents matching the query specified with query. The offset of the first hit returned and the number of hits returned can be set with the start-offset and max-hits options. Given the query doesn't explicitly contains fields, it's possible to restrict the search on specified fields using the search-fields option. Search can also be limited to a time range using the start-timestamp and end-timestamp options. These timestamp options can particularly be useful in boosting query performance when using a time series dataset and only need to query a particular window.


quickwit search
--index-uri <uri>
--query <query>
[--max-hits <n>]
[--start-offset <offset>]
[--search-fields <comma-separated list of fields>]
[--start-timestamp <i64>]
[--end-timestamp <i64>]


--index-uri (string) Location of the target index.
--query (string) Query expressed in Tantivy syntax.
--max-hits (integer) Maximum number of hits returned (defaults to 20).
--start-offset (integer) Skips the first start-offset hits (defaults to 0).
--search-fields (string) Search only on this comma-separated list of field names.
--start-timestamp (string) Inclusive lower bound.
--end-timestamp (string) Exclusive upper bound.


Searching a local index

quickwit search --index-uri file:///path-to-my-indexes/wikipedia --query "Barack Obama"

Searching a remote index

quickwit search --index-uri s3://quickwit-indexes/wikipedia --query "Barack Obama"

Limiting the result set to 50 hits

quickwit search --index-uri s3://quickwit-indexes/wikipedia --query "Barack Obama" --max-hits 50

Skipping the first 20 hits

quickwit search --index-uri s3://quickwit-indexes/wikipedia --query "Barack Obama" --start-offset 20

Looking for matches in the title and url fields only

quickwit search --index-uri s3://quickwit-indexes/wikipedia --query "Barack Obama" --search-fields title,url



Starts a rest server at address host:port and makes searchable indexes located at index-uri and returns the documents matching the query specified with query. Optionally connects to peers listed at peer-seed using SWIM membership protocol to allow search workload distribution.


Behind the scenes, Quickwit need to open the following port for cluster formation and workload distribution:

  • TCP port (default is 8080) for REST API
  • TCP and UDP port + 1 (default is 8081) for cluster membership protocol
  • TCP port + 2 (default is 8082) for gRPC address for the distributed search

In this case, if ports are already taken, the serve command will fail.


quickwit serve
--index-uri <list of uris>
--host <hostname>
--port <port>
--peer-seeds <list of seeds>


--index-uri (string) List of location of target indexes.
--host (string) Hostname the rest server should bind to.
--port (string) Port the REST API server should bind to.
--peer-seeds (string) List of peer socket address (e.g. to connect to form a cluster.


Start a local server and for a local index

quickwit serve --index-uri file:///path-to-my-indexes/wikipedia



Deletes the index at index-uri.


quickwit delete
--index-uri <uri>


--index-uri (string) Location of the target index. --dry-run (boolean) Executes the command in dry run mode and displays the list of files subject to be deleted.


Deleting an index

quickwit delete --index-uri s3://quickwit-indexes/catalog

Executing in dry run mode

quickwit delete --index-uri s3://quickwit-indexes/catalog --dry-run