Updates / product

50 tabs per session, memory as the ceiling, and the memory option

Every plan now allows 50 tabs in one session; what actually limits a session is its memory — 2, 4 or 6 GB by plan — and the new "memory" launch option buys 2–4 times that.

2026-11-03

A session used to stop at 5, 10 or 20 open tabs depending on the plan, even when the pages were light. From 2026-10-29 the tab cap is 50 on every plan and the real limit is memory, which is what heavy pages exhaust first anyway. And when a job needs more memory than your plan gives one session, a launch option now buys it.

What changed

• Tabs: 50 open pages per session on every plan — Community, shared and dedicated — counting every tab, popup and context (was 5 / 10 / 20).
• Memory per session: 2 GB on Community (was 3 GB), 4 GB on shared, 6 GB on dedicated (was 8 GB, with the new dedicated price). Headful sessions get 512 MB more for the display.
• A session that goes over its memory is ended with session_memory_limit; your other sessions aren't affected. A tab over the 50 cap is closed at once on Chromium-based browsers (the session goes on); on the others the session ends with page_limit.

The memory option

• Launch with "memory": 2, 3 or 4 and the session gets that many times your plan's memory — a dedicated thread with "memory": 4 has 24 GB.
• It counts as that many times the threads: a headless session with "memory": 2 takes 2 threads, a headful one 4, and uses minutes as fast. The launch response returns the effective weight and memory_mb.
• Only the JSON numbers 1–4: "memory": 4096 or "2x" gets 400 invalid_memory. A launch that would go over your threads gets 429 threads_exceeded, so a Community headful session can't use it.
• The tab cap stays 50 — the option is for heavy pages, not more of them than that.

When to use it

• Big single-page apps, long infinite scrolls, many heavy tabs at once, large full-page screenshots or PDFs — anything that ends with session_memory_limit at your plan's default.
• Light pages don't need it: a mid-weight article page fits dozens of times into one session. The case below measures how many on each plan and browser family, and what a client sees when memory runs out.

Get started

• The option: memory — also in the code builder and the dashboard's generator.
• Limits on every plan: Community vs paid and errors & limits.
• Measured: How many tabs fit, by plan and memory.