Free & open source  ·  macOS 14+

Set a memory limit
for Chrome.

Memory Saver sleeps idle tabs. RAMcap sets the ceiling Chrome doesn’t have — and stops the heaviest tab before your Mac runs out of memory.

Menu bar app  ·  No extension  ·  No admin rights  ·  Distributed on GitHub

Chrome memory

11.4 GB Under your 14 GB limit
Chrome11.4 of 14 GB

Largest tabs

  • YouTube — Live2.6 GB
  • Figma — RAMcap1.9 GB
  • Gmail — Inbox820 MB
  • Google Docs — Plan610 MB
  • Frame: maps.google.com340 MB
Warn 12 GB · Stop 14 GBSettings…
Stopped “YouTube — Live”Freed 2.6 GB · Reload the tab to bring it back

The problem

No more “Your system has run out of application memory.”

Chrome reached 30.5 GB on a 24 GB Mac, and macOS paused every app to survive. Chrome has no memory limit. RAMcap gives it one, so a single heavy tab stops — not your whole Mac.

Before

Chrome at 30.5 GB. Every app paused.

With RAMcap

Chrome capped at 14 GB. One tab stopped, reload to restore.

Per scan

19ms

A native read of every Chrome process. Same total as Activity Monitor.

Grace period

20s

Before a tab is stopped, you get a notice — and time to save or protect it.

Things to install in Chrome

0

No extension, helper tool or admin rights. RAMcap runs outside Chrome, so it never freezes with it.

How it works

Watch. Warn. Cap.

Pick two numbers once. RAMcap keeps Chrome under them from your menu bar.

01 · Watch

Chrome’s real total, always visible

Your menu bar shows Chrome’s full memory footprint — every tab, extension and helper process — not the misleading RSS number.

02 · Warn

A heads-up before it hurts

Cross your warning level and RAMcap tells you which tabs are heaviest, so you can close one on your terms.

03 · Cap

A hard ceiling that holds

At the limit, the largest tab process is stopped after a 20-second grace period. Protected tabs are never touched. Reload brings it back.

Compare

Memory Saver isn’t a limit.

Chrome’s Memory Saver unloads tabs you haven’t used in a while. It lowers the average — it never sets a ceiling.

Memory SaverRAMcap
Sets a ceiling on Chrome’s total memory
Handles a runaway tab you’re actively using
Shows Chrome’s real footprint in the menu bar
Lets you protect tabs that must never stop
Unloads tabs you haven’t used in a while

Use both: Memory Saver keeps the everyday level low, RAMcap stops the spike.

Open source

Free and open.
Read every line.

RAMcap stops processes on your Mac, so you should be able to see exactly how. The whole app — scanner, policy and enforcer — is on GitHub. No account, no subscription, no App Store.

Built with
Swift 6 · SwiftUI
Runs on
macOS 14 or later
Needs
No root, no helper tool
Footprint
A menu bar icon. No Dock icon.
Tests
Swift Testing

FAQ

Good questions.

Will I lose the tab?

Chrome shows it as a crashed tab and a reload brings the page back. You get a 20-second notice first, and protected tabs are never stopped.

Why not a Chrome extension?

Extensions can’t read memory on stable Chrome, and they freeze along with it. RAMcap lives outside Chrome, so it keeps working when Chrome doesn’t.

What permissions does it need?

None to set a limit. Showing tab names is opt-in and uses Accessibility permission to read Chrome’s own Task Manager.

Which browsers does it support?

Google Chrome on macOS 14 or later. The scanner watches Chrome’s app bundle; other Chromium browsers may come later.