DEV Community: Anton P

TabVitals 0.4.20 is live: Auto-suspend Chrome tabs and reclaim RAM on a schedule

Anton P — Sun, 27 Sep 2026 05:48:23 +0000

The Auto-suspend update I previewed is now live in the Chrome Web Store. I built TabVitals for the moment when Chrome has dozens of useful tabs open, but too many of them are still consuming resources in the background.

What changed in 0.4.20

Turn Auto-suspend ON and TabVitals runs a scan-and-sleep cycle immediately. It then repeats every 30 minutes, 1 hour, or 2 hours, putting eligible background tabs to sleep without closing them. You can keep working while the cycle runs.

Active tabs, pinned tabs, audio-playing tabs, recently used tabs, and sites you mark Always Awake are protected. Sleeping tabs stay in the tab bar and reload when you return. Save unfinished work on a tab before putting it to sleep.

After each cycle, the popup shows how many tabs were slept and the change in available system memory. That result is an observed system-wide change, not a claim that every byte came from a particular tab or that everyone will free the same number of GB.

The manual tools are still here

You can still run the X-Ray scanner to inspect loaded tabs and decide what to sleep manually. TabVitals also keeps its tools for the current website: clear that site's cache, perform a full site reset, open it in Incognito, or remove only that site from Chrome history. Auto-suspend does not clear cookies or history.

TabVitals runs locally in Chrome on Mac and Windows. Auto-suspend starts OFF, so you decide when to turn it on.

Install or update TabVitals 0.4.20 in the Chrome Web Store.

I'm the developer, and I'd appreciate feedback: which interval fits your workflow, and which tabs should always stay awake?

Coming soon: Auto-suspend for TabVitals — Chrome RAM cleanup on a schedule

Anton P — Thu, 24 Sep 2026 05:56:20 +0000

I’m building Auto-suspend for TabVitals: an upcoming way to free up Chrome RAM on a schedule, alongside the existing manual X-Ray scanner and tab-sleep controls.

If you work with dozens of tabs, the repetitive part is remembering to revisit them and put the ones you no longer need to sleep. This update is about making that routine automatic, so you can stay focused on your work.

The upcoming workflow

Choose a repeat interval: 30 minutes, 1 hour or 2 hours.
Switch Auto-suspend ON. The first scan-and-sleep cycle starts immediately.
TabVitals scans loaded tabs, sleeps eligible background tabs, and repeats on your schedule.
A prominent result card shows the measured change in available system memory after the cycle, plus the number of tabs put to sleep.

Tabs stay in the tab bar and reload when you return to them. The manual scanner remains available whenever you want to inspect your session yourself.

Automation needs boundaries

Active tabs, pinned tabs, audio-playing tabs and sites marked Always Awake stay protected. The auto-sleep path also rechecks each candidate before sleeping it, including whether you recently used the tab or its URL changed.

An important implementation detail: reopening the popup must not trigger another cleanup, changing the interval must not cancel an in-progress scan, and OFF must prevent further automatic sleep actions. Those cases are part of our tests.

Save unfinished work and mark sites that need to keep running as Always Awake. The memory card reports the system’s available-memory change after the cycle, rather than presenting it as an exact per-tab measurement.

Manual and one-site tools are staying

TabVitals continues to offer its manual X-Ray scanner, background-tab sleep controls, targeted cache/cookie tools for one website, one-click Incognito, and removal of only one site’s browsing history. Diagnostics run locally. This is for Chrome on both Mac and Windows.

Coming soon: Auto-suspend is in testing, not in the Chrome Web Store release yet. The current manual version is available here:

TabVitals on the Chrome Web Store

Which repeat interval would you choose for a busy browser session — 30 minutes, 1 hour or 2 hours?

How to Remove One Website from Chrome History, Clear Its Cache, and Free RAM

Anton P — Fri, 11 Sep 2026 14:19:32 +0000

Chrome makes three seemingly simple tasks surprisingly inconvenient:

removing one website from browsing history without clearing everything;
testing or resetting only the current website;
finding which actual tabs are consuming memory when the system only shows multiple Chrome or Chrome Helper processes.

These are different problems, but they often appear during the same troubleshooting session. Here is how to handle each one manually—and how to reduce the repeated steps.

Remove one website from Chrome history

Deleting all browsing history is easy. Removing only one website takes more work.

The manual route is:

Open Chrome History with Ctrl + H on Windows/Linux or Cmd + Y on macOS.
Search for the website’s domain.
Review the results carefully, including relevant subdomains.
Select every visit you want to remove.
Delete the selected entries.

This works, but it is awkward when you need to remove a website quickly. A domain may appear dozens of times, and Chrome does not provide a convenient “remove the current website from history” button beside the address bar.

Clearing history is also separate from clearing cookies or cached files. Removing visits does not reset the website or meaningfully reduce Chrome’s RAM usage.

Clear the cache and cookies for only one website

When one website displays outdated content, fails to load correctly, or behaves differently from another browser session, you usually do not need to clear data for all of Chrome.

Start with a hard reload:

Windows/Linux: Ctrl + Shift + R
macOS: Cmd + Shift + R

If that does not work:

Open the affected website.
Select the site-controls icon beside the address bar.
Open the site settings or on-device site-data controls.
Find the current domain.
Remove its data and reload the page.

Chrome changes the names and positions of these controls occasionally, but the important part is selecting the affected domain instead of using the browser-wide Delete browsing data command.

A deeper site reset can remove:

cached resources;
cookies and login sessions;
local storage and IndexedDB;
service-worker data;
saved permissions.

The selected website may sign you out. Unrelated websites should remain untouched when the operation is correctly limited to one domain.

Test the current page in Incognito

If a website works in Incognito but not in your normal Chrome profile, that is useful diagnostic evidence.

Incognito starts with a cleaner session and may use a different set of enabled extensions. The difference can point toward:

corrupted cookies or local storage;
stale cached resources;
a service worker;
an extension conflict;
a stored site permission.

The usual process is to copy the URL, open a new Incognito window, paste the URL, and load it again. It is not difficult, but it is another repetitive sequence when troubleshooting websites regularly.

Remember that Incognito is a diagnostic step, not proof that cached data is definitely the cause.

Finding the tab behind Chrome’s memory usage

RAM is a different problem.

Windows Task Manager and macOS Activity Monitor often show many Chrome or Google Chrome Helper (Renderer) processes. Those process names do not always tell you which loaded tab deserves attention.

Chrome’s own Task Manager can provide more detail, but shared renderers, utility processes, background activity, and dozens of open tabs can still make the result difficult to act on.

What users usually need is simpler:

Show me the actual website or tab using memory, then let me pause it without closing it.

Sleeping a background tab releases resources while leaving the tab in the tab bar. When you return, Chrome reloads it.

Depending on the number and type of loaded tabs, sleeping unnecessary background tabs may release hundreds of megabytes or several gigabytes of RAM. Results vary by session, website, browser state, and computer.

Reducing unnecessary background activity can also reduce processor work, heat, fan noise, and battery use—but it is not a system-wide performance guarantee.

One workflow for all three problems

I created TabVitals to place these actions in one current-site and tab-management workflow.

Its X-Ray scan shows the actual loaded tab beside the clearest memory reading Chrome exposes. When full renderer data is unavailable, it still shows JavaScript memory, activity, and graphics-related signals instead of presenting a process number without context.

From the results, you can:

identify memory-heavy tabs by website and tab title;
sleep unnecessary background tabs without closing them;
keep the current tab, pinned tabs, audio tabs, and selected websites awake;
scan again after cleanup.

For the current website, TabVitals also provides:

Open in Incognito — open the same page in a private session without copying its URL;
Fix this site — clear the current site’s cache and service-worker data, then reload it;
Full Reset — perform a deeper reset that can also remove cookies and session data;
Remove from history — remove visits for the current website without clearing the rest of Chrome’s history.

These actions solve different problems. Removing history does not free RAM, and clearing cached files is not the same as sleeping a memory-heavy tab. The advantage is having the appropriate controls together when you are diagnosing one website or a heavy Chrome session.

TabVitals performs its analysis locally and does not upload page content. History access is optional and is used only when you choose the history-removal action.

Disclosure: TabVitals is my product. It is available through the official Chrome Web Store.

Quick troubleshooting sequence

Need to hide visits to one website? Search and select them in Chrome History, or use a current-site removal action.
One website looks outdated? Try a hard reload.
The website is still broken? Clear data only for that domain.
It works in Incognito? Investigate local site data, permissions, and extensions.
Chrome is consuming too much RAM? Identify the actual heavy tabs and sleep the unnecessary background ones.
The same failure appears on multiple devices? Check the website, network, DNS, or server/CDN instead of repeatedly clearing local data.

The safest troubleshooting process starts with the smallest targeted action and expands only when necessary.