Chrome can restore the tabs you lost: where that list lives

Chrome was holding around thirty tabs. Then it quit, or the Mac restarted for an update, and the window came back with a single New Tab page. The pages are not gone: Chrome keeps several records of what was open, and they sit in different places with different reach. Knowing which one to try first is the difference between recovering a morning's work in four seconds and reconstructing it from memory for twenty minutes.

This covers the recovery routes in the order they should be attempted, why the fastest one sometimes returns nothing, and the one setting that makes the question stop coming up. It also covers the part that no recovery trick fixes, which is why thirty tabs existed in the first place.

Start with the reopen stack

The first attempt costs one keystroke. On macOS, Cmd+Shift+T reopens previously closed tabs in the order they were closed, and Google's shortcut reference describes it exactly that way. Pressing it repeatedly walks backwards through the stack, one tab at a time.

Two properties of that stack are worth knowing before relying on it:

It includes whole windows, not just tabs. If a window with twelve tabs was closed, the first press brings the window back with its tabs, rather than requiring twelve presses.

It is not infinite and it is not durable. The stack is a recent list, and it is tied to the browsing session. After Chrome has been quit and reopened, pressing the shortcut usually restores the last session's window on the first press, then stops being useful for anything older.

If the keystroke produces nothing at all, the usual cause is that the current window belongs to a different profile than the one that lost the tabs. The reopen stack is per profile, not per machine.

There is also a difference between closing a window and quitting the browser, and it changes what the stack holds. Cmd+Shift+W closes one window and pushes it onto the stack as a group, which is the friendliest case. Cmd+Q quits Chrome entirely, and the next launch treats the whole previous session as the thing to restore. A forced quit or a power loss falls into the same category as a quit, because Chrome writes its session state as pages open and close rather than at shutdown.

Then the History page, which reaches much further

Cmd+Y opens the History page in a new tab. The top of that page carries a Recently closed section that lists closed tabs and closed windows as named groups, and a closed window listed there restores all of its tabs at once.

Below that sits the full history, searchable by keyword. This is the route that works when the loss happened days ago, or when the reopen stack has already been exhausted. It is slower because it restores one page at a time and it does not preserve tab order or tab groups, but its reach is measured in weeks rather than minutes.

One caveat applies to both routes. History records pages, not state. A form half filled in, a document scrolled to page forty, a dashboard with filters applied through JavaScript rather than through the address: reopening the URL returns the page, not the position. For anything where the state mattered, the recovery that actually helps is the next section, because it restores the session rather than the addresses.

Pinned tabs and tab groups behave differently

Pinned tabs are the most durable thing in the strip. They come back on their own after a normal quit and relaunch, without any setting and without the reopen shortcut, which makes pinning the cheapest available protection for the handful of pages that should always be open. The limitation is that pinning does nothing about count: a pinned mail tab is still a tab competing for the same row.

Tab groups sit in the middle. A named, collapsed group restores as a group through Recently closed and through the startup restore, so the structure survives the ordinary cases. Full history search, on the other hand, returns bare URLs with no grouping and no order, so a recovery that goes that far means rebuilding the arrangement by hand. That difference is a reason to attempt the routes in order rather than jumping to history search because it feels more thorough.

When the tab appears in no list at all

A few situations leave nothing to recover, and recognizing them quickly saves time.

Incognito windows keep no record. Nothing from an Incognito session appears in history or in Recently closed, and closing the last Incognito window ends it permanently. Guest mode behaves the same way by design.

Browsing data that was deleted is deleted. Clearing browsing history removes the addresses from the History page, which also removes the only route that reaches back more than a session. Extensions that clear history or cookies on a schedule produce the same outcome without anyone choosing it, so a machine where recovery keeps failing is worth checking for one of those.

And a page that lived entirely behind a login with no stable address cannot be restored from history even when the entry exists, because the entry points at a wrapper rather than at the view. This is the case where the startup restore earns its keep, since it resumes the session instead of re-requesting the address.

The setting that removes the problem

Chrome can be told to reopen the same pages it was showing when it quit. The control is in Settings, under On startup, and the option is called Continue where you left off. Google's help page notes that cookies and site data are preserved with it, so sites that were signed in open signed in.

That behavior is the point, and it is also the reason to think before enabling it on a shared or portable machine. A laptop that opens twenty signed-in dashboards the moment Chrome launches is convenient at a desk and less so in a meeting room with a projector attached. Two ways to soften that:

Keep the startup set deliberately small. On startup can also be set to open a specific set of pages, which turns launch into a known state rather than whatever was open at 2am.

Pair it with the profile startup picker. In Manage Chrome profiles there is a Show on startup option that displays every profile when a new browser session opens, so the restore happens after a deliberate choice of which identity to resume.

Route	Reach	Restores tab order	Restores signed-in state	Cost
Cmd+Shift+T	The current and immediately previous session	Yes, one step at a time	Usually yes	One keystroke
Recently closed on the History page	Recent closed tabs and windows	Per window group	Usually yes	A few clicks
Full history search	Weeks	No	No	One page at a time
Continue where you left off	The last quit, automatically	Yes	Yes	A setting, enabled in advance

Session data lives inside the profile

Everything above is stored per profile, in the profile's own folder under ~/Library/Application Support/Google/Chrome. That single fact explains most of the confusing cases.

A second profile cannot restore the first profile's tabs. Switching profiles to look for a lost window is not just unhelpful, it hides the recovery route, because the reopen stack and the Recently closed list both belong to the profile that is in front.

Reinstalling Chrome while leaving the profile folder in place keeps the session records. Migrating to a new Mac by signing into a Google account does not, because sync carries bookmarks, passwords and settings rather than open tabs. Anyone who cares about the open set surviving a machine change should either copy the whole profile folder or, more reliably, stop treating open tabs as storage.

The files that hold this state are internal to Chrome and are not a documented, editable format. Guides that suggest opening them in a text editor are describing an older layout, and editing them by hand is not a repeatable recovery method. The supported levers are the three routes above plus the startup setting.

One more consequence is worth stating for anyone running several profiles. Each profile keeps its own set of open tabs, so the startup setting has to be enabled in each one separately, and a restart brings back as many windows as there were profiles running. On a machine with four profiles that can mean four windows and a long wait while every signed-in page loads at once. Setting On startup to a small fixed list on the profiles used least, and Continue where you left off only on the main one, keeps the launch predictable.

The reason thirty tabs existed

Recovery techniques treat the symptom. The tab count is the condition, and it has a specific cause: tabs get used as three things at once.

Some tabs are applications that should never close, such as mail, chat, a calendar and a project tool. Some are a reading list, opened with the intention of getting to them later. Some are a working set for the task actually in progress. All three live in the same strip, look identical, and compete for the same twenty or so pixels of label, which is why finding a tab takes longer than finding a file.

Once those categories are separated, tab loss stops being expensive. The applications no longer need restoring, because they are not tabs. The reading list belongs in a bookmark folder or a read-later tool, where a browser quit cannot touch it. What remains in the strip is the working set for the current task, which is usually three to eight pages and is quick to rebuild even in the worst case.

That is the model behind a browser that keeps each web app in its own window: mail is an app in a list with its own cookie container and its own notification badge, not tab seven of twenty-nine. The container model is described on the Workspaces page, and the services that can be added this way are listed under Supported apps. The practical effect on recovery is that a crash costs a working set, not a workday.

Sorting the strip once takes about ten minutes and holds for months. Pin the permanent residents, move everything that is really a reading list into a bookmark folder named for the week, and close the rest. Whatever is left is the working set, and it is small enough that losing it costs a few seconds rather than a search through history.

What to change first

Turn on Continue where you left off today, since it costs nothing and covers the ordinary case of a quit or a restart. Then look at the tab strip and move the permanent residents out of it, either into pinned tabs as a first step or into a tool like SpaceDeck that gives each app its own window, so the next unexpected quit takes a handful of pages with it instead of a morning.