The Great Suspender Tab Recovery: Free Tool to Get Your Tabs Back

How to Recover Tabs From The Great Suspender

You need one of two things: some text that still contains the suspended links, or a copy of your browser’s History file. The first is quicker; the second works even when every tab is gone.

1. Collect the suspended links

   Copy the address of any tab that still shows a suspended page, or open a OneTab, Session Buddy or bookmarks export that contains chrome-extension:// links. Paste all of it into the Paste text box. Other text in between is ignored.

2. Or drop your History file

   If the tabs have closed, switch to the History file tab. Close the browser, copy the file named History from your profile folder (paths are in the table below), and drop the copy onto the page.

3. Check the recovered list

   Each row shows the original page title, the real URL and the extension that suspended it. Leave “Merge duplicates” on to collapse repeat visits into one row per page.

4. Save the list before anything else

   Download it as a bookmarks file, a CSV or a plain text list. Import the bookmarks file into any browser so the links are safe even if you close this page.

5. Reopen the pages in batches

   Press Open to reopen the pages 10 at a time. Allow pop-ups for belaytab.com the first time, because browsers block a page that opens many tabs.

What Happened to The Great Suspender?

The Great Suspender was a popular open-source Chrome extension that unloaded tabs you weren’t using to save memory. In June 2020 its original developer handed the project to a new, unnamed owner. A few months later that owner shipped version 7.1.8, which loaded code from a remote server. Chrome disabled the extension in February 2021 and flagged it as malware, which closed every suspended tab it held.

The problem was found in the open. Users on the project’s GitHub page noticed that the Chrome Web Store build included a script that the GitHub source didn’t, pointing at a domain registered around the same time as the update. The script could run code chosen by the server, which is enough to track browsing or inject ads. The GitHub issue that collected the evidence is still the best primary account.

The GitHub source code of The Great Suspender was never shown to contain the malicious script. The risk came from the build published to the store by the new owner, which is why installing a fork of the old code doesn’t carry the same risk by itself.

Where the Real URL Hides in a Suspended-Tab Link

A suspender doesn’t really keep your page. It swaps the tab for a small page inside the extension and writes the original address into that page’s own URL. When you click the tab, the extension reads the address back and loads it. If the extension disappears, the page it was drawing goes too, but the address was never stored anywhere else.

That’s good news for recovery: the real URL is sitting in plain sight inside the suspended link. The Great Suspender and its forks put it after uri= at the very end, unencoded, so it can contain its own question marks, ampersands and # fragments. The title is URL-encoded in the ttl parameter and the scroll position is in pos. Other suspenders use a query string with an encoded url parameter instead.

• Very old versions of The Great Suspender wrote an encoded url= parameter instead of uri=. The tool reads both.
• Links that passed through another app are sometimes encoded twice, so https:// shows up as https%253A%252F%252F. The tool decodes up to three layers and stops as soon as it has a working address.
• A suspended page that was suspended again by a second extension carries one link inside another. The tool unwraps it and returns the innermost real address.
• In Edge the address bar shows extension:// rather than chrome-extension://. Both forms are recognised, as is Firefox’s moz-extension://.

How to Recover Suspended Tabs After the Extension Was Removed

When Chrome disables or removes an extension, it closes every tab that was showing one of that extension’s pages. That’s what happened to Great Suspender users in 2021. The tabs are gone from the window, but their suspended links usually survive in at least one of these places.

• Browser history. Every time a suspended page loaded, Chrome recorded its chrome-extension:// link, with the original title, in history. Chrome deletes local history older than 90 days, so this works for recent losses. Search chrome://history for the extension ID, or drop the History file here to get them all at once.
• Recently closed tabs. Ctrl+Shift+T (Cmd+Shift+T on a Mac) reopens closed tabs. A reopened suspended tab shows an error, but its address bar still holds the suspended link, which you can copy and paste here.
• Session manager and OneTab exports. If you ever saved those windows with OneTab, Session Buddy or a similar tool, the export contains the suspended links, not the real ones. Paste the whole export here.
• Bookmarks. “Bookmark all tabs” on suspended windows saved the chrome-extension:// links. Export your bookmarks to HTML and paste the file’s contents.
• Another synced device. If Chrome Sync is on, a second computer may still have the history entries or open tabs. Check chrome://history there too.

Profiles other than the first live in folders named Profile 1, Profile 2 and so on instead of Default. Open chrome://version (or edge://version, brave://version) and look at “Profile Path” to see which folder is yours.

How the Great Suspender Recovery Tool Works

Everything happens in this tab. Pasted text is scanned with a pattern that matches chrome-extension://, extension:// and moz-extension:// links, and each match is taken apart to find the url or uri parameter and the title. HTML escaping from bookmark files (&) and JSON escaping from exports (\/ and \u0026) is undone first, so links inside those files are read correctly.

A History file is opened with sql.js, which is SQLite compiled to WebAssembly and loaded only when you drop a file. The tool asks the database for rows in the urls table whose address starts with an extension scheme, reads each one’s title, visit count and last visit time (Chrome counts in microseconds since 1 January 1601), and throws the rest away. It never reads your ordinary browsing history into the page.

Nothing is uploaded, stored or logged. There’s no server involved and no analytics on what you paste. When you close the tab, the file and the list are gone, which is why saving an export is step four above.

Examples: Suspended Links and What Comes Back

These are the kinds of input people bring to this page, with the address the tool returns for each one.

Is The Marvellous Suspender Safe?

The Marvellous Suspender is the best-known fork of The Great Suspender, started in 2021 from the old open-source code without the tracking script. As of September 2026 its Chrome Web Store listing shows version 9.0.3, about 100,000 users, a 4.2 rating and an update dated 17 September 2026. The source code is public on GitHub under the GPLv2 licence, and it has moved to Manifest V3, Chrome’s current extension format.

Nothing public shows it doing anything harmful, and its code can be checked by anyone. That’s real evidence, but it isn’t a guarantee. It asks for access to every http and https site plus your browsing history, which is the same kind of access that made The Great Suspender dangerous once it changed hands. The Great Suspender was also open source, and the problem was in the store build, not the code on GitHub.

If you keep using a suspender, pick one whose source is public, check who publishes it, and read the changelog when its permissions change. Keep a copy of your open tabs somewhere that doesn’t depend on the suspender, because the next removal will close its tabs the same way.

Do You Still Need a Tab Suspender?

For most people, no. Every major browser now puts idle tabs to sleep by itself, and a sleeping tab keeps its real URL. If the browser feature is ever turned off, your tabs stay exactly where they were, which is the main reason to prefer it over an extension.

Chrome, Edge and Brave let you list sites that should never sleep. Add anything that must keep running in the background, such as a web mail tab or a music player.

Ways to Recover Great Suspender Tabs Compared

Limits and Troubleshooting

• “No suspended links found”: the text has no chrome-extension:// links with a url or uri parameter. Check you copied the full address, not just the title.
• “This isn’t a SQLite database file”: you picked the wrong file. The History file has no extension; don’t pick History-journal or a folder.
• The History file won’t copy, or the tool says the database is locked: close the browser completely first. On Windows, check it isn’t still running in the system tray.
• Some rows are missing: Chrome deletes history older than 90 days, and clearing browsing data removes it sooner. Check a second synced computer.
• A title is empty: some suspenders didn’t store one. In History file mode the tool falls back to the title Chrome saved.
• Only one tab opened: your browser blocked the rest as pop-ups. Allow pop-ups for belaytab.com and press Open again.

The tool can recover an address only if a suspended link still exists somewhere. If the history was cleared and there’s no export, bookmark or synced device, the links are gone. Suspenders kept their own list inside the extension’s storage, and that storage is deleted with the extension.

How to Avoid Losing Tabs This Way Again

The Great Suspender story is a clear case of a single point of failure: the only record of hundreds of tabs lived inside one extension. A few habits remove that risk.

• Use the browser’s own tab sleeping instead of an extension, so tabs never depend on anyone’s store listing.
• If you keep a suspender, export your open tabs as bookmarks now and then, from the bookmarks manager or with “Bookmark all tabs”.
• Keep Chrome Sync or an equivalent on, so history exists on more than one device.
• Use a session manager that saves windows automatically and keeps versions, and export its data to a file you control.
• Be wary when an extension you rely on changes owner, adds permissions, or its changelog stops matching its public code.