3.8 out of 5
Google doesn't verify reviews. Learn more about results and reviews.
- All reviews
- Recent
- Helpful
- Highest to lowest rating
- Lowest to highest rating
- English
- All languages
Ibrahim AbdullahiNov 12, 2024
No longer working for me, but I liked it when it did
Fernando de FrançaNov 3, 2024
Why is chromewebstore showing "This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions"?
Maksym MorozOct 24, 2024
Legion, dude just go to settings.
LegionOct 21, 2024
Suspends tabs in whitelist. Does not 'ignore' pinned tabs. Does not display round icon, only semi-transparent bar at top of page. In short, broke.
Blade. RyOct 12, 2024
Works, but after checking whats eating my free space on drive i found that TabSuspender folder is 3 gigs in size. Some folders are months old. I guess TS is making snapshot of sites it suspends but never deletes that data from the drive.
Patrick LauserSep 25, 2024
Hit some keyboard shortcut while typing a letter with a diacritic, which suspended a bunch of tabs - didn't find any way to turn off that keyboard shortcut, so I switched off the extension - upon which it closed all the suspended tabs, and they did not go into closed tab history where they could have been reopened. Completely unacceptable.
Dani GiglioSep 12, 2024
Please, give us a quickly update. Tab Suspendere is not working on last Chrome Linux relaise!
mortty 92Aug 28, 2024
great and fast
Craig DeskinsJul 10, 2024
A lot of great options. Side Note: Chrome's built-in Memory Saver doesn't suspend youtube tabs, this will. I turned off Chrome's Memory Saver, now I use Tab Suspender instead.
Samy DULORJul 3, 2024
I've been using it for few years and it's been very great; not denying it happened, but I never had any issue like extension crashing and loosing all my tabs. However I recently started using tab groups, and it seems that randomly some groupped tabs become "new tab". It still is the actual same tab since I can "rewind history"; once to get to the suspended tab, twice to get to the actual loaded webpage; it really looks like something asked those tabs to load "chrome://newtab"...