Documentation

influxdb3 create database

The influxdb3 create database command creates a new database in your InfluxDB 3 Core instance.

Provide a database name and, optionally, specify connection settings and authentication credentials using flags or environment variables.

Usage

influxdb3 create database [OPTIONS] <DATABASE_NAME>

Arguments

  • DATABASE_NAME: The name of the database to create. Valid database names are alphanumeric and start with a letter or number. Dashes (-) and underscores (_) are allowed.

You can also set the database name using the INFLUXDB3_DATABASE_NAME environment variable.

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Core server (default is http://127.0.0.1:8181)
--retention-periodDatabase retention period (duration value, for example: 30d, 24h, 1h)
--tokenAuthentication token
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables instead of providing CLI options directly:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_AUTH_TOKEN--token

Examples

The following examples show how to create a database.

In your commands replace the following:

  • DATABASE_NAME: Database name
  • AUTH_TOKEN: Authentication token

Create a database (default)

Creates a database using settings from environment variables and defaults.

influxdb3 create database 
DATABASE_NAME

Create a database with an authentication token

Creates a database using the specified arguments. Flags override their associated environment variables.

influxdb3 create database --token 
AUTH_TOKEN
DATABASE_NAME

Create a database with a retention period

Creates a database with a 30-day retention period. Data older than 30 days will not be queryable.

influxdb3 create database --retention-period 30d 
DATABASE_NAME

Create a database with infinite retention

Creates a database with no retention period (data never expires).

influxdb3 create database --retention-period none 
DATABASE_NAME

Create a database with a 90-day retention period

Creates a database with a 90-day retention period using an authentication token.

influxdb3 create database \
  --retention-period 90d \
  --token 
AUTH_TOKEN
\
DATABASE_NAME

Create a database with a 1-year retention period

Creates a database with a 1-year retention period.

influxdb3 create database --retention-period 1y 
DATABASE_NAME

Create a database with a combined duration

Creates a database with a retention period of 30 days and 12 hours.

influxdb3 create database --retention-period 30d12h 
DATABASE_NAME

Retention period duration formats

Retention periods are specified as duration values using a numeric value plus a duration unit.

Valid duration units

UnitDescription
hhour
dday
wweek
momonth (30 days)
yyear (365 days)

Minute (m) and second (s) units are not supported for retention periods.

Retention period constraints

  • Minimum for data retention: The practical minimum retention period is 1 hour (1h).
  • Zero-duration periods: Setting a retention period to 0<unit> (for example, 0d or 0h) is allowed but marks all data for immediate deletion at query time. This differs from InfluxDB 1.x and 2.x where 0d meant infinite retention.
  • Infinite retention: Use none to set an infinite retention period.

Example duration values

  • 1h - 1 hour
  • 24h - 24 hours
  • 7d - 7 days
  • 4w - 4 weeks
  • 30d - 30 days
  • 1mo - 1 month (30 days)
  • 90d - 90 days
  • 1y - 1 year (365 days)
  • none - infinite (data never expires)

You can combine units: 30d12h (30.5 days), 1y6mo (545 days)

For complete details about retention periods, see Data retention in InfluxDB 3 Core.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2