Chrome memory limit on macOS: what can be raised

Chrome on a Mac has no setting that raises how much memory it is allowed to use. There is no slider in Settings and no supported switch that hands the browser or a single tab a bigger allowance. The one control with a memory number in its name, the enterprise policy TotalMemoryLimitMb, works in the opposite direction: it tells Chrome at what point to start discarding tabs, not how much more it may take. What actually decides whether a heavy page stays loaded is the RAM in the Mac, how many other tabs compete for it, and how Memory Saver is configured. This guide, checked against Google and Apple documentation on October 18, 2026, covers what each of those controls does and the order in which to try them.

The memory number that does exist, and why it is not a ceiling to raise

Most guides that rank for this search say plainly that Chrome's memory allocation cannot be increased, and then move straight to tips for using less. That is mostly right, but it skips the one setting that people find when they dig into Chrome policies.

The Chrome Enterprise policy list includes a policy called TotalMemoryLimitMb, supported on Windows and on Mac since Chrome 79. Its description is specific. It sets the amount of memory a single Chrome instance can use before Chrome starts discarding tabs to save memory. A discarded tab has its memory released and must reload the next time it is shown. The documentation adds two details that matter:

• Chrome does not guarantee that it will always stay under the value. It is a trigger for discarding, not a hard cap.
• Any value below 1,024 is rounded up to 1,024 MB.

When the policy is not set, Chrome only tries to save memory when it detects that the computer's physical memory is running low.

Read that way, setting a high value does not give Chrome more memory. It simply means Chrome waits until memory is nearly exhausted before discarding tabs, which is already the default behavior when the policy is absent. Setting a low value does the reverse: Chrome discards tabs earlier. Either way, the policy changes when tabs get unloaded. It never adds RAM.

On a Mac, Chrome policies are normally delivered by an administrator through a configuration profile, as Google's Mac policy guide for administrators describes. On a work Mac, a policy like this may already be in place. Typing chrome://policy into the address bar lists the policies Chrome has received, which is the quickest way to rule out an aggressive limit set by IT before changing anything else.

Three different problems arrive with the same search

People who search for a way to raise Chrome's memory limit are usually reacting to one of three symptoms. They look similar, but the fixes are different.

A tab reloads when you come back to it. This is Chrome deactivating an inactive tab, either through Memory Saver or because macOS reported memory pressure. The page was not broken. Chrome released its memory on purpose. The fix is to tell Chrome which sites to keep active.

One page is slow while it is in front of you. A large spreadsheet, a design file, or a long chat history can be slow even when it is the only tab open. Discarding other tabs helps a little, but the limit here is usually the page itself plus the overall memory available on the Mac.

The whole Mac slows down, not just Chrome. Typing lags in other apps, the beach ball appears, and switching apps takes seconds. This points to system-wide memory pressure, and the evidence is in Activity Monitor rather than in Chrome.

Identifying which one applies first avoids changing settings that cannot help. The next section shows where to look.

Measure before changing anything

Two tools answer different questions. Activity Monitor tells you whether the Mac as a whole is short of memory. Chrome's Task Manager tells you which tab or extension is using it.

Activity Monitor: is the Mac short of memory?

Open Activity Monitor and click the Memory tab. Apple's guide to viewing memory usage explains the figures at the bottom of the window. The most useful is the Memory Pressure graph, which Apple says is determined by free memory, swap rate, wired memory, and file cached memory. Swap Used shows how much of the startup disk is standing in for RAM.

Apple's page on checking whether a Mac needs more RAM gives a simple reading of the graph:

Memory Pressure color	What Apple says it means
Green	The computer is using all of its RAM efficiently
Yellow	The computer might eventually need more RAM
Red	The computer needs more RAM

A large "Memory Used" number on its own is not a problem. macOS deliberately fills unused RAM with cached files and compresses inactive memory. The color of the pressure graph is the signal to watch, especially while the slow page is open.

Chrome Task Manager: which tab is heavy?

Google's guide to speeding up Chrome points to Chrome's own Task Manager. Open the More menu at the top right, choose More tools, then Task Manager, and select Memory to sort tasks by memory usage. Each tab, extension, and helper process gets its own row, so a single runaway page or extension stands out at once.

Chrome can also show a tab's memory in the tab hover card. In Settings, under Appearance, the Mac option is called "Show memory usage on tab hover preview card." With it on, hovering over a tab shows how much memory that tab is using, without opening Task Manager.

Keep the tabs that matter from being unloaded

If the problem is the first one, tabs that reload when you return, the fix is in Chrome's Performance settings. Google's page on Chrome performance settings explains that Memory Saver deactivates tabs you are not currently using, and that an inactive tab reloads automatically when you open it.

Memory Saver has three levels:

• Moderate: tabs become inactive after a longer period of time.
• Balanced (recommended): tabs become inactive after an optimal period of time.
• Maximum: tabs become inactive after a shorter period of time.

The setting that behaves most like extra headroom for one important app is the exclusion list. In Settings, Performance, next to "Always keep these sites active," select Add. Sites can be picked from the tabs currently open, or typed in. The rules for typed entries are precise:

• An entry without a scheme, such as google.com, also matches subdomains like drive.google.com and calendar.google.com.
• A leading dot, as in .google.com, matches that host but not its subdomains.
• A path, such as www.google.com/finance, covers only that section of a site.
• Wildcards work for the host and query parts, such as https://*, but not as a prefix or suffix of a host name.

Some tabs are already protected without any list. Google notes that tab deactivation may not happen for pages with active audio or video, screen sharing, page notifications, active downloads, partially filled forms, pinned tabs, or connected USB or Bluetooth devices. Pinning the two or three web apps used all day is therefore another way to keep them loaded. Turning on "Inactive tabs appearance" marks deactivated tabs with a ring around the icon, so it is clear which ones will reload.

When one tab alone is too heavy

If Task Manager shows a single tab using far more memory than everything else, the browser settings above will not help much. Memory Saver protects that tab from being unloaded, but it cannot give the tab more memory than the Mac has free.

A few steps make a measurable difference:

• Close or disable unused extensions. Google's speed guide lists turning off or removing extensions under More, Extensions, Manage Extensions. Extensions show up as their own rows in Task Manager, which makes it easy to see which ones cost the most.
• Reload the heavy page after long sessions. Web apps that run all day can grow over time. A reload at a natural break returns that memory without restarting Chrome.
• Keep Chrome up to date. Google lists updating as the first step in its speed guide.

Adding memory is a purchase, not a setting

When Activity Monitor shows yellow or red pressure with only a modest number of tabs open, the remaining lever is hardware. Apple's RAM guide explains how to find out whether a particular Mac can take more: hold the Option key, choose Apple menu, then System Information, and under Hardware click Memory. If the Memory Slots pane includes Upgradeable Memory, memory can be installed or replaced. If that pane does not appear, Apple says upgradeable memory is not available for that Mac, and the amount chosen when the Mac was bought is the amount it will always have.

Turning Memory Saver off is a trade, not an upgrade

A common reaction to tabs reloading is to switch Memory Saver off entirely. That stops Chrome from deactivating tabs on a timer, but it does not create memory. When the Mac runs low, macOS still compresses memory and starts swapping to disk, and Chrome still discards tabs when it detects low physical memory. The difference is who decides which tabs suffer and when.

For most setups, a better trade is to leave Memory Saver on at Balanced, add the handful of always-open web apps to "Always keep these sites active," and let everything else be unloaded. That keeps the important tabs warm while research tabs give their memory back.

A Mac that shows red memory pressure with Memory Saver off and only a few tabs open has a simpler answer: it needs either fewer things running at once or more RAM.

Decide what stays resident, and give it its own place

The deeper pattern behind this search is that a browser tab is being used as a desktop app. Mail, chat, calendar, and project tools stay open all day, often in several accounts, and they compete for memory with dozens of short-lived research tabs in the same window. Memory Saver cannot tell the difference unless it is told through the exclusion list.

One way to make the split explicit is to separate the two kinds of pages. Research and reading stay in Chrome, where Memory Saver can unload them freely. The handful of web apps that must stay signed in and responsive move into an app aggregation browser for macOS, where each app sits in the sidebar with its own isolated sign-in. One such browser keeps a separate cookie container per app, so several Gmail or Slack accounts can stay signed in side by side, and its workspaces group apps by context such as work and personal. Its features page lists the rest, including per-app zoom and mute.

That product offers every feature free for 14 days, then a free plan with 1 workspace and up to 3 apps. Running several accounts of the same service is part of the paid Pro plan, which the pricing page lists at $7 a month, $60 a year, or $129 one-time. Whether it is worth adding depends on how many always-open apps there are. With two or three, an exclusion list in Chrome is usually enough.

What to change first

Open Activity Monitor with the slow page loaded and read the Memory Pressure color. If it is green, add the sites that keep reloading to "Always keep these sites active" and stop there. If it is yellow or red, sort Chrome's Task Manager by memory, remove what does not need to run, and only then consider moving always-open apps elsewhere, for example into SpaceDeck, or adding RAM.