> ## Documentation Index
> Fetch the complete documentation index at: https://runpod-b18f5ded-docs-runpod-allow-ip.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If this page is missing information, contains outdated instructions, or doesn't fully answer the user's question, use the feedback tool to report it. In your feedback, be specific about what's missing, what appears out of date, or what needs to be corrected or updated, so the docs team can act on it directly.

# Environment variables

> Configure Pods with environment variables for settings, secrets, and runtime information. See setup and usage details for Runpod Pods.

export const PodsTooltip = () => {
  return <Tooltip headline="Pods" tip="Dedicated GPU or CPU instances for containerized AI/ML workloads." cta="Learn more about Pods" href="/pods/overview">Pods</Tooltip>;
};

Environment variables are key-value pairs accessible within your <PodsTooltip /> container. Use them to pass configuration settings, secrets, and runtime information without hardcoding values into your code or container image.

## Set environment variables

You can configure up to 50 environment variables per Pod.

**During Pod creation:**

1. Click **Edit Template** and expand **Environment Variables**.
2. Click **Add Environment Variable** and enter the key-value pair.

**In Pod templates:**

1. Navigate to [My Templates](https://www.console.runpod.io/user/templates).
2. Create or edit a template and add variables in the **Environment Variables** section.

**Using secrets:**

Reference [Runpod secrets](/pods/templates/secrets) for sensitive data:

```
API_KEY={{ RUNPOD_SECRET_my_api_key }}
DATABASE_PASSWORD={{ RUNPOD_SECRET_db_password }}
```

## Update environment variables

1. Go to [Pods](https://www.console.runpod.io/user/pods) and click the three dots next to your Pod.
2. Select **Edit Pod** and expand **Environment Variables**.
3. Add or update variables and click **Save**.

<Warning>
  Updating environment variables restarts your Pod, clearing all data outside your volume mount path (`/workspace` by default).
</Warning>

## Access environment variables

**In your Pod's terminal:**

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
echo $VARIABLE_NAME     # View specific variable
env | grep RUNPOD       # List Runpod variables
```

**In your code:**

<Tabs>
  <Tab title="Python">
    ```python theme={"theme":{"light":"github-light","dark":"github-dark"}}
    import os

    model_name = os.environ.get('MODEL_NAME', 'default-model')
    api_key = os.environ['API_KEY']  # Raises error if not set
    ```
  </Tab>

  <Tab title="JavaScript">
    ```javascript theme={"theme":{"light":"github-light","dark":"github-dark"}}
    const modelName = process.env.MODEL_NAME || 'default-model';
    const apiKey = process.env.API_KEY;
    ```
  </Tab>

  <Tab title="Bash">
    ```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
    MODEL_NAME=${MODEL_NAME:-"default-model"}
    echo "Using model: $MODEL_NAME"
    ```
  </Tab>
</Tabs>

## Runpod-provided variables

Runpod automatically sets these environment variables:

| Variable              | Description                       |
| --------------------- | --------------------------------- |
| `RUNPOD_POD_ID`       | Unique Pod identifier.            |
| `RUNPOD_DC_ID`        | Data center identifier.           |
| `RUNPOD_POD_HOSTNAME` | Server hostname.                  |
| `RUNPOD_GPU_COUNT`    | Number of GPUs available.         |
| `RUNPOD_CPU_COUNT`    | Number of CPUs available.         |
| `RUNPOD_PUBLIC_IP`    | Public IP address (if available). |
| `RUNPOD_TCP_PORT_22`  | Public port mapped to SSH.        |
| `RUNPOD_VOLUME_ID`    | Attached network volume ID.       |
| `RUNPOD_API_KEY`      | Pod-scoped API key.               |
| `PUBLIC_KEY`          | Authorized SSH public keys.       |
| `CUDA_VERSION`        | Installed CUDA version.           |
| `PYTORCH_VERSION`     | Installed PyTorch version.        |

## Runpod-reserved variables

Runpod reads these variables if you set them. They change how Runpod handles your Pod rather than configuring your application:

| Variable          | Description                                                                                                                                                                                                                                                                                                                             |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `RUNPOD_ALLOW_IP` | Comma-separated list of IP addresses or IP address ranges allowed to reach your Pod's HTTP proxy ports, such as `203.0.113.7,198.51.100.0/24`. Requests from other addresses receive a `400` response. Doesn't apply to TCP ports. See [Restrict access by IP address](/pods/configuration/expose-ports#restrict-access-by-ip-address). |

## Best practices

* **Use secrets for sensitive data**: Never hardcode API keys or passwords. Use [Runpod secrets](/pods/templates/secrets).
* **Validate required variables**: Check that critical variables are set before your application starts.
* **Provide defaults**: Use fallback values for non-critical configuration.
* **Use descriptive names**: Prefer `DATABASE_PASSWORD` over `DB_PASS`.
* **Group related variables**: Use consistent prefixes like `DB_HOST`, `DB_PORT`, `DB_NAME`.