Frequently asked questions
The practical details behind bookmarks, sessions, workspace switching, and cross-browser continuity.
What problem does TabSpace actually solve? Open
It fixes the gap between bookmarks and browser state. Users can keep bookmarks, sessions, pinned items, and workspace context together so they stop rebuilding the same setup after interruptions, browser changes, or device handoffs.
Is this just another bookmark manager? Open
No. Bookmark tools mostly store links. TabSpace also remembers sessions, window grouping, tab order, recent activity, and the workspace the session belongs to.
What exactly gets saved in a session? Open
A session is modeled as windows containing ordered tabs. Each tab keeps its URL, title, and position so restore can bring back as much of the original browsing state as possible.
Which browsers are supported? Open
The MVP is Chromium-first. Firefox support is planned next. Safari is possible later but more limited because of extension constraints. Mobile is mostly read-only for bookmarks and sessions.
Do I need cloud sync for it to be useful? Open
No. TabSpace is designed to work in a local-first mode so users can save bookmarks and sessions without depending on a backend from day one. Sync can be added later.
Does TabSpace track full browsing history? Open
No. The goal is not history surveillance. The product focuses on active session data the user wants to save, restore, or sync, with user-controlled deletion and sync behavior.
Can I restore only part of a saved session? Open
Yes. Restore is designed to support the whole session, a single window, or a selected subset of tabs depending on what the user needs next.
Still trying to map this to your workflow?
Tell us where browser continuity breaks down for you and we can point you to the right access path.