How to Build a Personal Knowledge Wiki (2026 Guide)
How to build a personal knowledge wiki — practical setups using Obsidian, Notion, and other tools to create a searchable, linked knowledge base that grows more useful over time.
How-To Guides
How to stop losing tabs when your browser crashes — the best settings and tools to recover lost tabs, save tab sessions, and prevent losing your work when Chrome, Firefox, or Edge crashes.
Browser crashes are one of those computing frustrations that feel entirely unfair. You've spent 40 minutes opening the right tabs — research articles, a documentation page, a thread, a tool — and then Chrome crashes or your laptop restarts and all of it is gone. The work to reconstruct those tabs from browser history, if you can reconstruct it at all, is painful.
Stopping this problem requires both recovery settings (for after a crash) and prevention habits (so crashes don't lose anything important). This guide covers both.
Browsers buffer tab state to disk periodically, not continuously. Chrome saves session state every few seconds, but during a hard crash (power loss, kernel panic, force-quit), the last few seconds of state may not be written.
"Restore previous session" doesn't always appear. Chrome should offer to restore previous session after a crash. But if Chrome didn't detect the crash as abnormal, or if you dismissed the "Restore pages?" prompt without reading it, the offer disappears.
Crash doesn't always mean recovery. If the browser was running slowly before the crash (too many tabs, memory pressure), the session state file may be corrupted, making automatic recovery impossible.
Browser history isn't the same as tab restoration. History shows every page you visited; it doesn't show which specific tabs you had open at once, or which tab groups you'd organized.
Chrome can automatically reopen all tabs from the previous session after any close — including crashes.
How to enable:
After a crash:
If the banner doesn't appear:
Keyboard shortcut: Ctrl+Shift+T reopens the last closed tab. Pressing it repeatedly reopens previously closed tabs in reverse order. After a crash and restart, this often restores recently closed tabs.
Extensions that save tab sessions automatically, providing a snapshot you can restore even if Chrome's built-in session recovery fails.
Session Buddy is a free Chrome extension that saves all open tabs as named sessions.
How Session Buddy prevents tab loss:
Manual saves: Before closing Chrome intentionally, save the session with a name: "Research session 2026-08-10 — Stripe integration." Saved sessions persist indefinitely and can be restored any time.
Advantage: More reliable than Chrome's built-in session recovery. Named sessions mean intentional tab sets are always restorable.
Similar to Session Buddy, Tab Session Manager auto-saves all tabs periodically with configurable interval (default: 15 minutes).
After a crash: Open Tab Session Manager → find the most recent auto-save → restore all tabs.
For work sessions where you expect to close the browser intentionally and want a reliable backup:
Bookmark all open tabs:
Advantage: Reliable. Doesn't depend on Chrome's session recovery mechanism. Bookmarks persist across browser reinstalls. Limitation: Manual step required. Bookmarks accumulate and need periodic cleanup.
Chrome's Tab Groups (available since Chrome 89) can be saved and synced across devices.
How to save a Tab Group:
Saved tab groups persist across browser restarts and crashes. They sync across devices when Chrome Sync is enabled.
Best use: For persistent "working sets" you return to regularly — a project research tab group, a development reference tab group — rather than one-time sessions.
For tabs that represent important research rather than just active browsing — articles you're reading for a project, documentation you reference regularly, sources you're synthesizing — saving the content to WebSnips is more durable than any tab management approach.
The fundamental issue with tabs: Tabs are a working memory metaphor. "I need to come back to this" is the mental model. But tabs aren't a storage system — they're an active state that crashes, closes, and gets lost. Content that matters needs to be in a storage system.
How to use WebSnips for important tab content:
Result: Crashes don't matter for your important research — because important research isn't living in tabs.
Scenario: Your laptop runs out of battery mid-session. Chrome had 15 tabs open — research for two projects, documentation, a Gmail thread, and a YouTube video you were watching.
Step 1 — After restart, check Chrome's session recovery: Open Chrome. If "Chrome didn't shut down correctly" banner appears → click Restore.
Step 2 — If no banner: Press Ctrl+Shift+T repeatedly — Chrome reopens recently closed tabs in reverse order.
Step 3 — Check Session Buddy or Tab Session Manager: If you had a session manager installed: open it → find the last auto-save (likely 15 minutes before the crash or less) → restore.
Step 4 — Check Chrome history: Go to chrome://history. Look for entries from the past hour before the crash. Manually reopen the critical tabs.
Step 5 — Check browser sync: If Chrome Sync is enabled: Chrome history is synced. The tabs may appear in your "Tabs from other devices" section on a new tab.
Prevention for next time: Enable "Continue where you left off" in Chrome settings. Install Session Buddy. For critical research tabs, save to WebSnips.
Enable Chrome's "Continue where you left off" — the single highest-leverage setting.
Install a session manager (Session Buddy or Tab Session Manager) — auto-saves every 15 minutes without any conscious action.
Use Tab Groups for named working sets — and save them.
Reduce tab count — most tab crashes are preceded by running 50+ tabs simultaneously, which exhausts memory and increases crash risk. WebSnips, Pocket, or bookmark saves reduce the need to keep tabs open "to come back to later."
Enable Chrome Sync — your history and saved tab groups sync across devices, providing another recovery path.
Don't ignore the "Restore pages?" prompt. After a crash, Chrome shows a restoration banner. Read it and click Restore before opening any new pages — once you navigate away, the offer disappears.
Don't rely on browser history for tab restoration. History shows what you visited, not which tabs were open simultaneously. Session recovery (via "Continue where you left off" or a session manager) is the right tool for tab restoration.
Don't keep important research only in tabs. Tabs are working memory, not storage. If a tab represents something you'll need tomorrow or next week, save it to a system that persists — bookmarks, a notes app, or a web capture tool.
Don't wait for a crash to set up recovery. The settings (Continue where you left off, session manager) take 5 minutes to configure. Set them up before you need them.
Can I recover tabs from a Chrome crash if I didn't have a session manager? Yes — try Ctrl+Shift+T immediately after reopening Chrome (reopens recently closed tabs). Check Chrome history (Ctrl+H) for the pages open at the time of the crash. If Chrome Sync is enabled, check "Tabs from other devices" on a new tab — your pre-crash session may appear there.
Does the "Continue where you left off" setting affect Chrome startup time? Yes, slightly — Chrome has to reload all previous tabs on startup. You can mitigate this by using tab groups (which collapse) or by closing tabs you don't need before shutting down Chrome intentionally.
Do pinned tabs survive a crash? Pinned tabs are restored by Chrome's session recovery along with regular tabs, but they must be pinned before the crash to be recognized as pinned during restoration.
Stopping tab loss when your browser crashes requires both recovery tools (session managers, Chrome's restore setting) and a better relationship with tabs themselves — important research shouldn't live only in tabs. The combination of "Continue where you left off," a session manager extension, and the habit of saving important tabs to a more permanent home makes browser crashes a minor inconvenience rather than a data loss event.
More WebSnips articles that pair well with this topic.
How to build a personal knowledge wiki — practical setups using Obsidian, Notion, and other tools to create a searchable, linked knowledge base that grows more useful over time.
How to build a second brain in 30 minutes — a practical quick-start for knowledge workers who want a working personal knowledge management system without spending days on setup.
How to capture ideas before you forget them — the fastest tools and habits for getting ideas out of your head and into a retrievable system the moment they occur to you.