A little troubleshooting
Troubleshoot Tabplate startup, missing favicons, disabled Lucky, Chrome permissions and local data recovery without losing boards.
The usual questions
Lucky is missing or disabled.
It is intended for an empty board and needs enough eligible sites. If history permission is missing, Chrome must grant it first. A sparse history may not meet the six-site threshold. Try Magic with saved links or open tabs instead.
A favicon is still just a letter.
Check the favicon guide. Chrome’s local store may not have it, direct fetching may be off or the site may block icon discovery. A letter is a safe fallback.
The tab rail is empty.
It mirrors web tabs from the same Chrome window and needs optional tab permission. Browser-internal pages are not normal web tabs. This feature cannot access real tabs from a website preview.
Where did another workspace’s Favorites go?
Favorites are global. A missing item may no longer be starred, may be filtered by your search, or may have been deleted at its original location.
A new tab briefly shows an older board.
A bounded local display snapshot can appear before the verified repository finishes loading. Other open tabs or changed data can make it briefly stale. It is a display cache, not the source used to recover data.
My other computer has different boards.
There is no account-based cloud sync in this version. Use export/import to move data between Chrome profiles.
I cannot delete the last workspace.
Tabplate keeps at least one workspace. Create another one before removing the current last workspace.
A safe order for investigating
- Export what you can
Keep a current file and an earlier known-good backup.
- Try a normal refresh
For a local unpacked update, reload the extension card and then the open Tabplate page. Keep the same installation folder and profile.
- Check permissions and settings
A disabled optional permission affects that feature, not all saved content.
- Use recovery before resetting
Inspect local snapshots or a backup import. Avoid uninstalling as the first troubleshooting step.