memory
Give the session 2, 3 or 4 times your plan's memory; it counts as that many times the threads.
Use it for: Memory-heavy work that would otherwise end with session_memory_limit: many tabs at once, big single-page apps, long infinite scrolls, or large PDFs and screenshots.
Browsers: Google Chrome, Microsoft Edge, Brave, Opera, Naver Whale, Yandex Browser, Chromium, Patchright, Rebrowser, Camoufox, Firefox, WebKit.
Details
- Type:
integer - Default: 1
- Example:
{"memory":2}
A multiplier of your plan's per-session memory (Community 2 GB, shared 4 GB, dedicated 6 GB; headful sessions get 512 MB more for the display). The session's weight is multiplied too: headless with "memory": 2 takes 2 threads, headful 4, and its minutes are used up as fast. The launch response returns the effective weight and memory_mb.
Only 1, 2, 3 or 4 as a JSON number; anything else (e.g. 4096 or "2x") is refused with 400 invalid_memory. A launch that would go over your threads gets 429 threads_exceeded as usual, so a Community headful session can't use it. The tab cap (50) stays the same.
Used in
- Case 80: How many tabs fit in one session, by plan, browser and "memory"
- Case 72: Stay under the tab and memory caps: reuse a few pages, close what you're done with
- More memory for one heavy session
All options: launch options.