Document 2GiB and 4GiB headless memory options

browsers/concurrency-and-limits.mdx

@@ -53,7 +53,7 @@ If you're hitting the ceiling in normal operation, [contact us](https://calendly
 | --- | --- | --- |
 | Default memory | 8 GB | 1 GB |
 
-Memory is the practical ceiling on how many tabs and how heavy a page one browser handles. A [headless](/browsers/headless) browser at 1 GB is sized for short-lived, single-page, high-concurrency automation; open a dozen heavy tabs in one and Chromium starts killing renderers. If your workload needs many concurrent pages, spread it across more browsers rather than more tabs in one. Headful browsers support up to 16 GB: set `memory` on a [browser pool](/browsers/pools) when a workload needs more than the default.
+Memory is the practical ceiling on how many tabs and how heavy a page one browser handles. A [headless](/browsers/headless) browser at 1 GB is sized for short-lived, single-page, high-concurrency automation; open a dozen heavy tabs in one and Chromium starts killing renderers. If your workload needs many concurrent pages, spread it across more browsers rather than more tabs in one. non-gpu browsers support `2GiB` or `4GiB` headless, or `16GiB` headful: set `memory` when you [create a browser](https://www.kernel.sh/docs/api-reference/browsers/create-a-browser-session) or [browser pool](/browsers/pools) for workloads that need more than the default.
 
 [GPU acceleration](/browsers/gpu-acceleration) is a separate browser type with its own [usage rate](/info/pricing#usage-rates), available on Start-Up and Enterprise.
 

browsers/headless.mdx

@@ -4,9 +4,11 @@ title: "Headless Mode"
 
 Kernel browsers ship in `headful` mode by default. In headful mode, the launched browser has a corresponding GUI. This enables features like [live view](/browsers/live-view) and [replays](/browsers/replays).
 
-`headless` mode runs without a visual interface. They generally run faster and have a lighter footprint (1 GB rather than headful's 8 GB), resulting in significant cost savings. This is useful for short-lived or highly concurrent browser automations.
+`headless` mode runs without a visual interface. They generally run faster and have a lighter footprint (1 GB by default rather than headful's 8 GB), resulting in significant cost savings. This is useful for short-lived or highly concurrent browser automations.
 Some bot detectors may detect headless mode.
 
+for more memory on a non-gpu browser, set `memory` to `2GiB` or `4GiB` when you [create a headless browser](https://www.kernel.sh/docs/api-reference/browsers/create-a-browser-session) or [headless browser pool](/browsers/pools). the default remains `1GiB`.
+
 To launch a Kernel browser in `headless` mode, set its config:
 
 <CodeGroup>

browsers/process-execution.mdx

@@ -240,7 +240,7 @@ Kernel doesn't expose a per-session memory metric in the API, CLI, or dashboard
 
 ### Read whole-session memory
 
-`free` reports the memory allocated to your browser. A headless browser gets 1 GiB; a headful, non-GPU browser gets 8 GiB by default and 16 GiB when you set `memory` on [create](/api-reference/browsers/create-a-browser-session).
+`free` reports the memory allocated to your browser. non-gpu headless browsers use `1GiB` by default and support `2GiB` or `4GiB`; non-gpu headful browsers use `8GiB` by default and support `16GiB`. set `memory` when you [create a browser](https://www.kernel.sh/docs/api-reference/browsers/create-a-browser-session) to select the larger allocation.
 
 <CodeGroup>
 ```typescript Typescript/Javascript