ContextSnap

Save and restore your entire browser state — tabs, scroll positions, form inputs, and text selections — in one click.

Never lose your browser context again. ContextSnap saves your entire browser state and restores it exactly where you left off. Not just tabs — your scroll positions, filled-in forms, selected text, and even pinned tabs are all preserved. WHAT GETS SAVED ━━━━━━━━━━━━━━━ • All open tabs (URLs, titles, pinned state) • Scroll positions on every page • Form inputs — text fields, dropdowns, checkboxes, radio buttons • Text selections and highlighted text • Active tab state WHAT MAKES IT DIFFERENT ━━━━━━━━━━━━━━━ Most session managers only save your tabs. ContextSnap goes further — it captures the full state of every page and restores it faithfully. Progressive Scroll — Infinite-scroll pages like YouTube, Twitter, and Reddit don't load all their content at once. ContextSnap automatically scrolls down to trigger lazy loading before restoring your exact position. No more landing at the top of a feed you scrolled through for 20 minutes. Smart Form Restore — Works with modern web apps built with React, Vue, and Angular. Handles dynamic form IDs that change on every page load (common on job application platforms like Greenhouse, Ashby, and Lever). Uses a 10-strategy selector system to find the right field even when the page structure changes. Open in New Window — Restored tabs open in a fresh window by default, so your current tabs stay untouched. No more accidentally overwriting what you're working on. WHO IT'S FOR ━━━━━━━━━━━━━━━ Researchers — Save your research session with dozens of tabs, each scrolled to the relevant section, with key passages highlighted. Come back to it tomorrow or next week. Job seekers — Halfway through a long application on Greenhouse or Lever? Save your progress and come back later without re-filling every field. Developers — Debugging across multiple docs, Stack Overflow pages, and GitHub PRs? Save the whole context and restore it when you switch back from another task. Students — Working on a paper with multiple sources open? Save your reading context with scroll positions and text selections intact. Anyone with too many tabs — If you've ever had 30+ tabs open and wished you could just freeze everything and come back later, this is for you. FULL CONTROL WITH SETTINGS ━━━━━━━━━━━━━━━ • Restore scroll position — on/off (disable to always start at the top) • Progressive scroll — on/off (auto-scroll on infinite-scroll pages) • Restore form data — on/off • Restore text selections — on/off • Open in new window — on/off (restore in a new window or replace current tabs) • Max saved contexts — set a limit (oldest removed automatically), or unlimited • Auto-delete after X days — automatically clean up old saves • Show notifications — on/off KEYBOARD SHORTCUTS ━━━━━━━━━━━━━━━ • Ctrl+Shift+S (Cmd+Shift+S on Mac) — quick save your current context • Ctrl+Shift+A (Cmd+Shift+A on Mac) — open your saved context list PRIVACY FIRST ━━━━━━━━━━━━━━━ • All data stays on your device using chrome.storage.local • No accounts, no servers, no analytics, no tracking • No data ever leaves your browser • Password fields, hidden fields, and file uploads are never captured • Uninstalling removes all stored data We believe your browsing data is yours. Period. PERMISSIONS EXPLAINED ━━━━━━━━━━━━━━━ We know broad permissions can be concerning. Here's exactly why each one is needed: • tabs — Read open tab URLs and titles so we can save and restore them • storage — Save your contexts and settings locally on your device • scripting — Inject the content script that captures scroll positions, form data, and text selections • activeTab — Interact with the currently active tab • host_permissions (all URLs) — Capture and restore page state on any website you visit None of these permissions are used to collect or transmit data. They exist solely for the save/restore functionality. KNOWN LIMITATIONS ━━━━━━━━━━━━━━━ • File upload fields can't be restored (browser security restriction) • Google Docs text selections use a custom renderer and can't be captured • Banking/auth sites may redirect to login (sessions expire server-side) • PDF scroll positions can't be restored (Chrome PDF viewer is sandboxed) • Content on infinite-scroll pages may differ on reload (new posts, algorithm changes)