kill-tabs
A CLI tool and Node.js API to kill Chrome tab processes to free up system resources while keeping tabs in the browser.
What is kill-tabs?
kill-tabs is a Node.js-based tool that kills Chrome tab processes to improve system performance, decrease battery usage, and save memory. It targets users who keep numerous tabs open, allowing them to suspend tabs without closing them, so they can be reloaded later. The tool works across multiple Chromium-based browsers and offers both CLI and API interfaces for flexibility.
Developers and power users who frequently have many Chrome tabs open and experience system slowdowns or high resource consumption, particularly on laptops or lower-spec machines.
It provides a simple, automated way to free up system resources without losing tab state, unlike manual tab closing or browser extensions that may not fully kill processes. Its cross-platform support and dual CLI/API options make it versatile for different workflows.
Overview
Kill all Chrome tabs to improve performance, decrease battery usage, and save memory
Use Cases
Best For
- Freeing up memory on systems with many open Chrome tabs
- Reducing battery drain on laptops during intensive browsing sessions
- Automating browser resource management in development workflows
- Temporarily suspending tabs without losing browsing history or state
- Improving system performance when Chrome is consuming excessive CPU
- Managing tabs across multiple Chromium-based browsers like Brave or Edge
Not Ideal For
- Users who need to preserve unsaved form data or active sessions in tabs, as killing processes will lose any temporary state
- Projects requiring selective tab suspension (e.g., keeping specific tabs alive), since kill-tabs operates indiscriminately on all tabs per browser
- Environments where browser stability is critical, as crashed tabs may confuse users or require manual reloading efforts
- Systems without Node.js installed, as it's a prerequisite for both CLI and API usage
Pros & Cons
Pros
Kills Chrome tab processes to instantly free up memory and CPU, directly addressing system slowdowns from tab overload as described in the README for users like the author who are 'tab-abusers'.
Works with Chrome, Chromium, Chrome Canary, Brave, and Edge, with CLI options to exclude specific browsers, making it versatile for users of various Chromium-based browsers.
Offers both a global CLI for quick use and a Node.js module for programmatic access, allowing automation in development workflows or scripts.
Runs on macOS, Linux, and Windows, ensuring broad usability across different operating systems without platform-specific tweaks.
Cons
Lacks granular control to target specific tabs or preserve important ones, which can disrupt unsaved work or active processes, a limitation not addressed in the README beyond basic browser exclusions.
Requires Node.js installation for both CLI and API usage, adding an extra step for users not in the Node ecosystem or on minimal systems.
Leaves tabs in a crashed state without auto-reload; users must manually reload each tab or rely on external extensions like 'Reload All Tabs', as suggested in the README tip.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.