> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/expression-engine.md).

# Expression engine

{% hint style="info" %}
**File-based configuration**

You can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](/deploy/host-n8n/configure-n8n/basic-configuration.md#keeping-sensitive-data-in-separate-files) for more details.
{% endhint %}

[Expressions](/build/work-with-data/expressions-versus-data-nodes.md) are the JavaScript snippets n8n evaluates at runtime to set node parameters dynamically. The expression engine is the component that runs that evaluation. This page lists environment variables for configuring it.

{% hint style="info" %}
**Experimental**

The `vm` engine is experimental. n8n runs the `legacy` engine by default. The variables below other than `N8N_EXPRESSION_ENGINE` only take effect when you set `N8N_EXPRESSION_ENGINE` to `vm`.
{% endhint %}

| Variable                                    | Type                        | Default  | Description                                                                                                                                                                |
| ------------------------------------------- | --------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `N8N_EXPRESSION_ENGINE`                     | Enum string: `legacy`, `vm` | `legacy` | Which expression engine to use. `legacy` runs expressions without isolation. `vm` runs them in a sandboxed V8 isolate. `vm` is experimental; `legacy` remains the default. |
| `N8N_EXPRESSION_ENGINE_POOL_SIZE`           | Number                      | `1`      | Number of V8 isolates kept warm in the pool.                                                                                                                               |
| `N8N_EXPRESSION_ENGINE_MAX_CODE_CACHE_SIZE` | Number                      | `1024`   | Maximum number of compiled expressions to cache.                                                                                                                           |
| `N8N_EXPRESSION_ENGINE_TIMEOUT`             | Number                      | `5000`   | Execution timeout in milliseconds for each expression evaluation.                                                                                                          |
| `N8N_EXPRESSION_ENGINE_MEMORY_LIMIT`        | Number                      | `128`    | Memory limit in MiB for each V8 isolate.                                                                                                                                   |
| `N8N_EXPRESSION_ENGINE_IDLE_TIMEOUT`        | Number                      | -        | If set, scales the isolate pool to zero warm isolates after this many seconds with no activity.                                                                            |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/expression-engine.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.