Web Console

The Web Console allows you to interact with QuestDB. It provides you with tools to query data and visualize it in a table or using graphs.

Screenshot of the Web Console

Accessing the Web Console#

The Web Console will be available at http://[server-address]:9000. When running locally, this will be http://localhost:9000.


Preview of the different sections in the Web Console

Code editor#

By default, the Web Console opens on the code editor.


Run queryf9 or ctrl/cmd + enter
Locate cursorf2, use this to focus the SQL editor on your cursor in order to locate it


As you can write numerous SQL commands separated by semicolon, the Web Console uses the following logic to decide what command to execute:

  • Check if you highlighted a query or part of it, if yes then it will be executed, otherwise:
  • Verify if the cursor is within a SQL statement, if yes, the wrapping statement will be executed, otherwise:
  • Find out if the cursor is on the same line as a SQL statement and after the semicolon, if yes, this statement will be executed, finally:
  • If the cursor is on a line that does not contain a SQL statement, the next encountered statement will be executed. If there is no statement following the cursor, the previous statement will be used.

Visualising results#

You can run a query and click on the Chart button. This will display the chart editor. You can then choose chart type, for example line and then press Draw.

Downloading results#

You can download the query result by clicking the CSV button. This file will be useful to test the import functionality below.


The import tab can be accessed by clicking this icon on the left-side navigation menu:

Screenshot of the Web Console showing the location of the Import tab

Import details#

Description of the fields in the import details table

File nameName of the file imported. If imported from copy & paste, an automatically-generated file name
SizeSize of the imported file
Total rowsNumber of rows successfully imported
Failed rowsNumber of rows that failed to import
Header rowWhether the dataset has been recognised to have a header row or not
StatusStatus of the import. See below

Import statuses#

Description of the import statuses

importingData is currently being imported
failedImport failed, nothing was imported
imported in [time]Import is finished. The completion time will be displayed next to the status
existsYou are trying to import a file that already exists. To import it regardless, you can either append or override. See importing again for a more exhaustive description

Amending the schema#

Although the schema is automatically detected, you can amend the type for any column using the following steps:

  • Click on the file you want to amend in the Import screen. The schema will be displayed.
  • Find and click on the column which type you want to change.
  • You will then need to re-trigger the import.
 Change the schema in the Web Console when importing data

Custom import#

You can amend the import behaviour with the following options. This will trigger to import the data again.

AAppendUploaded data will be appended at the end of the table
OOverrideUploaded data will override existing data in the table
LEVSkip lines with extra valuesSkips rows that contains dangling values that don't fit the schema
HHeader rowFlag whether the first row should be considered header

To start the import, click the following button:

Upload button from the Web Console