---
title: Configure Kibana memory
description: Kibana has a default memory limit that scales based on total memory available. The default limit is sufficient for core Kibana functionality. In some...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/6201/deploy-manage/production-guidance/kibana-configure-memory
products:
  - Kibana
applies_to:
  - Self-managed Elastic deployments: Generally available
---

# Configure Kibana memory
Kibana has a default memory limit that scales based on total memory available.
The default limit is sufficient for core Kibana functionality. In some scenarios, such as large reporting jobs, detection rules, managing alerting workflows, or working with SLOs, we recommend increasing memory limits to at least 2 GB to meet more specific performance requirements.
For Platinum and Enterprise users, we recommend at least 2 GB of memory for each Kibana instance to avoid service interruptions when using advanced features.

## Limit memory usage

A limit can be defined by setting `--max-old-space-size` in the `node.options` config file found inside the `kibana/config` folder or any other folder configured with the environment variable `KBN_PATH_CONF`. For example, in the Debian-based system, the folder is `/etc/kibana`.
The option accepts a limit in MB:
```js
--max-old-space-size=2048
```

<note>
  In orchestrated environments like Elastic Cloud Hosted, Elastic Cloud Enterprise, or Elastic Cloud on Kubernetes, you should not override Kibana’s default memory limit using `--max-old-space-size`. Instead, set the desired Kibana memory size at the deployment level. This automatically adjusts the container’s memory allocation and ensures more consistent and predictable performance.
</note>