One link for a whole group of tabs.

Try it right here

This page has no backend. The link below is built entirely in your browser, using the real Tab Share codec, and points at the live viewer.

How it works

No servers, shown not just said.

1. The extension takes your tabs and compresses the list (titles, URLs, order) into a short token.
2. The token goes in the URL fragment — the part after #, which browsers never send to a server.
3. You paste the link into chat, email, a doc, anywhere. It is just text.
4. The recipient opens it. A static viewer page reads the fragment, decodes it locally, and renders a slideshow / grid / list. The viewer host receives a page load and nothing else.

Tracking parameters (utm_*, fbclid, …) are stripped from every URL before it goes in the link. Add a password to a link and the token is encrypted in your browser (PBKDF2 → AES-GCM) before it ever reaches the URL.

Why it is different

Other tools upload your list to a server and share that page. Tab Share puts the list in the link.

• The shared thing is a link, not a page on someone's server. Nothing to leak, index, or lose.
• No vendor lock-in. The viewer is open source and static. Your links keep working even if this site does not.
• Works where the recipient cannot install anything. Locked-down laptop, library PC, a phone, a non-technical relative.
• Optional end-to-end password. Encrypted in the browser; the password travels out of band.
• Auditable privacy. The viewer makes zero third-party requests — offline favicons, system fonts, no analytics.
• Cross-browser both ends. Chrome and Firefox to create; any browser, including mobile, to open.
• A walkthrough surface. Ordered slideshow, grid, numbered list, preview grid — not just a pile of links.
• Free, no account, no pro tier. AGPL-3.0.

Not what Tab Share is for: freeing memory (that is OneTab), syncing tabs across devices (that is browser sync / Toby), or a long-term reading library (that is Raindrop). Tab Share does one job — hand someone a set of pages, with nothing stored.

Privacy

• Tab Share itself has no backend, no database, no account, and no analytics.
• The viewer makes zero requests to third parties. Favicons are drawn locally from the hostname; fonts are your system fonts.
• The fragment that holds your tabs is never transmitted to the viewer's host.
• The shortener is a separate, optional service. If you turn it on, it stores the long link plus aggregate hit counts and referrer host by day — no IP, no full referrer, no cookies. It is host-allowlisted, so it cannot be used as an open redirector. You can self-host it.

Long link? There is a shortener.

For big collections, the companion Tab Share shortener turns the link into something like s.kaikay.de/swift-amber-otter. Off by default -- opt in when a link gets long.

• Zero dependencies. Node's standard library only, or a Cloudflare Worker.
• Self-hostable in one command. systemd installer, JSON or SQLite storage.
• Host-allowlisted. Can only ever point at a Tab Share viewer -- never an open redirector.
• No tracking. No IP, no full referrer, no cookies -- aggregate stats only.