Troubleshooting

Work through whichever of these matches what you're seeing. Each one links out to the detailed guide instead of repeating it here.

TabSlate doesn't open on a new tab

TabSlate replaces the browser's new-tab page (see Getting Started). If a new tab shows something else, confirm the extension is still enabled in your browser's extension manager, and that no other extension is also overriding the new-tab page — only one can win at a time. Reinstalling from an official store resets things if toggling it back on doesn't help.

A permission-gated feature isn't working

Most of TabSlate's permissions are requested once at install and don't need separate attention. The one exception is the optional overlay permission behind the global search shortcut — if it isn't granted for the site you're on, the shortcut does nothing there, silently. See Browser Permissions for what's required versus optional, and where to turn the optional one on.

The global search shortcut isn't opening anything

Ctrl+Shift+K (Command+Shift+K on macOS) only responds where TabSlate can run a script: it does nothing on internal browser pages (chrome://...), and on any other site until you've granted the optional overlay permission there. On the TabSlate new-tab page itself, it focuses the dashboard's own search box rather than opening an overlay — that's expected, not a failure. See Keyboard Shortcuts and Browser Permissions.

A tab or bookmark isn't showing up in search

Search needs at least two characters typed before it matches anything, and bookmark results are scoped to your active workspace — a bookmark saved in a different workspace won't appear until you switch to it. Trashed bookmarks are excluded from search entirely; archived ones still appear, marked Archived. See Search and Workspaces & Collections.

The sync status shows Offline

This means TabSlate currently has no reachable connection — changes you make keep saving locally and will push once a connection returns. Seeing it while your network is actually down is expected; if it persists once you're clearly back online, try Sync now from the sidebar. See Offline Behavior.

The sync status shows an error

Hover the status indicator for the specific error message. Common causes are a plan limit reached, or — if you're on a self-hosted server — the server being unreachable or misconfigured; see the next item for that case. See Cloud Sync.

The extension can't connect to a self-hosted server

Confirm the server URL field has your instance's exact HTTPS origin — not http://, and not still pointing at the default TabSlate Cloud address — then work through the server-side checks in Self-hosting → Troubleshooting: a TLS error and a CORS error point to different fixes there. See also Connect the Extension.

Still stuck

Open an issue describing what you tried and what you saw: TabSlate for the extension, TabSlate Server for a self-hosted instance.