Sync, backup, and account — Tomebound help

Data on this device

Your signed-in collection is stored in the cloud; this browser keeps a read copy to speed up repeat visits. Startup confirms your account and sync connection before enabling edits. Chat and some dialogs prepare when you first open them after loading the page, so opening them may take a moment on a slow connection. If startup fails, for example because part of the app didn't download, Tomebound says so and offers Reload; if startup takes more than 20 seconds, it offers Reload while it keeps trying. When a newer version of Tomebound is published while a tab is open, a banner offers to reload. The previous four releases' app files stay available, and if a feature still can't load, the same banner asks you to reload.
If the browser closes its local cache while you switch apps, Tomebound reopens it automatically. If the cache remains unavailable, or doesn't respond within a few seconds, the page uses a temporary copy in memory; cloud saves still work while you are signed in and online, but that temporary copy is lost when you reload or close the page. If the browser blocks site data for Tomebound, the app still opens, but settings aren't kept after a reload and sign-in may not work; a message says to allow site data.
Editing requires sign-in and a connection. An open tab can show its cached copy offline; editing and reloading need a connection. If a save's answer is lost, Tomebound checks it and may resend the same change without applying it twice. It then makes up to three automatic confirmation checks, pausing between checks. Failed cloud reads do not use up those checks. Retry sync can check again. Later edits may wait. After these checks, if the cloud has moved on, independent edits can save; edits that depend on a rejected or changed value need review. Rejected changes are undone on screen and are not automatically resubmitted. If a save remains uncertain, check your collection before making it again.
Unconfirmed edits can stay visible, but this browser's read copy contains only confirmed changes. Edits that have not been sent are kept only in this open tab and are lost if it closes or reloads. A warning distinguishes a rejected save from an uncertain one. Dismissing an uncertainty warning does not establish whether the change saved.
Signing out clears the read copy from this browser, and opening Tomebound while signed out shows the signed-out demo instead of your last collection. If the sign-in service can't be reached, or answers without confirming your session, the read copy stays in place until it can. Loading sign-in stops waiting after about 15 seconds per step. On a browser that was signed in, the account chip then reads "can't reach sign-in" and the collection is not treated as signed out; selecting the chip, Try again in an empty collection, coming back online, or returning to the tab tries again. Signing in with a different account on the same browser first clears the previous account's read copy and history; nothing from it is shown to, or saved into, the new account. Nothing is lost - your collection lives in your account, and signing back in restores it from the cloud.
Use export data before signing out or clearing browser data if you want a portable copy on hand.
Signed out, the account chip reads "sign in / sign up" and opens sign-in with one click. Its tooltip says "demo only — not kept after sign-in" while the welcome demo is loaded, or that a signed-out collection is read-only. Signing in replaces the demo with your account collection and turns the chip into the account menu; nothing from the demo carries over, including its cards, imported decks, and history. When you edit or import in the demo, Tomebound says at that moment that the change is demo only and not kept after sign-in. Empty signed-in collections show a zero state, with add and import available from the normal app controls, only once the cloud confirms the collection is empty. While a signed-in collection is still loading, it reads "still loading your collection…" instead.

Account sync

The sidebar account menu stays compact: it shows your full account name, then Account, settings, export data, and Sign out. Routine sync status is kept out of this menu.
When you are signed in, Tomebound keeps changes in sync across your signed-in browsers. Everyday edits sync incrementally - only the change itself travels, not your whole collection. An open tab gets changes from your other devices as they happen; when its live connection drops or goes quiet, it reconnects, and on reconnecting, returning to the tab, or coming back online it loads anything it missed. Closing or leaving the page while a change is still saving asks you to confirm first.
Card art, prices, and printing details are not carried in the cloud copy. Tomebound refreshes that metadata silently from Scryfall after you sign in; known printings can display artwork directly while the refresh is still running. Background lookups that return no artwork or price, or fail after their normal retry, are not repeated on every sync. Reloading the page or changing the card’s printing allows a new lookup. These background refreshes preserve edits and deletions received from your other devices and connected tools.
Signed-in users manage personal access tokens from the account section in settings, keeping this less-common tool out of the main account menu (see Automation and integrations).
Changes from browsers and connected tools are saved one at a time. You can keep editing while a save finishes. If another edit changes a value your change needs, Tomebound asks you to check the collection and make that change again; it does not automatically resubmit it. Independent later edits can still save. Removing a card row that changed elsewhere also needs review. Removing more than 25 rows in one change requires confirmation; undoing or redoing a confirmed bulk delete is not limited. A failed sign-in check says Tomebound couldn't verify your sign-in at the time. If your session ends unexpectedly, a rejected or uncertain save stays reported when the same account reconnects.
During temporary connection problems, Add and row-selection controls stay in place but are disabled until editing is available. Connection problems wait about eight seconds before showing a banner. Rejected changes appear immediately and stay reported until you dismiss them or a change made after the rejection saves. A save already waiting when the rejection happened does not clear the warning. Uncertain saves need confirmation or dismissal, even if another edit saves. Shared views omit editing controls; the signed-out demo allows unsaved additions through Add, Import, and Scan.
Background prices, Scryfall metadata, set icons, search indexing, and remote revisions never reorder or rebuild the screen you are currently using. On a fresh device, initially missing prices, rarity, and preview artwork fill into the existing collection rows or visual cards as they load; row order, selection, and focus stay in place. Later changes to already displayed metadata stay silent and apply at your next explicit route, view, filter, sort, reload, or mutation boundary. Automatic card-detail backfills do not flash a separate progress message. Updates that only fill in prices, artwork, or rules text do not start a cloud save. If another device changes your collection while details are loading, those edits are kept and the details fill in on the current cards; removed cards stay removed.
If a card changes or disappears while its row, menu, tag editor, or deck preview is open, Tomebound checks the current collection before acting. If that copy is no longer there, the action stops and a short message says the list was refreshed. A pending move to a new container stops before creating the container when its card is gone.
Failed changes and uncertain saves appear in the banner. Later edits may wait while Tomebound checks an uncertain save; routine successful syncing stays out of the way.
If sync looks stuck, copy the support details from settings and include them with a bug report.
Connection and save failures appear in the banner; routine successful syncing stays out of the way.

Collection size limits

The first sync on a new device downloads the whole collection. After that, everyday edits transfer the changes, and reopening Tomebound on that device loads only what changed since the last visit. If the saved copy can't be verified or too much has changed, it downloads the whole collection again.
Cloud sync supports collections of up to 50,000 card rows and 20 MB of collection data. A change that would grow a collection past either limit is not saved, and the sync status explains which limit was reached; edits and removals still save, so a collection over the limit can always be brought back under it.
Large collections can take longer to load, search, import, or edit. Performance and local cache capacity depend on your browser and device. Comfortable use at 10,000 or 50,000 cards has not yet been established.

Backups and recovery

Tomebound runs daily cloud backups for recovery. Older snapshots are kept for 90 days, and the latest verified backup is kept even if your collection has not changed for longer. If you need help recovering a collection, email [email protected].
Export data asks for a scope every time - entire collection, only the cards matching your current filters, or just the cards you have selected - so a stale filter can never quietly produce a partial file you mistake for a full backup. It also remembers the format you last used and shows a receipt with the count, format, and filename after the download.
Tomebound JSON, the full portable backup with containers, decks, tags, and saved history, is only offered for the entire-collection scope; the CSV formats support all three scopes.
To restore a Tomebound JSON backup, sign in, open add cards, choose import, then upload a file. The preview compares your current collection with the backup - cards, entries, decks and containers, history, and the date of each - and warns when the backup is older than your latest change or has fewer cards. It also offers a download of your current collection first. Check the replacement box and choose restore backup. This replaces your account collection across devices; cancel leaves it unchanged. Before replacing anything, Tomebound saves your current collection as a recovery point; right after the restore you can choose undo restore to put it back. The saved point also stays available as a recovery point for agents connected through MCP.
JSON backups keep your cards, containers, decks, tags, and history, and leave out card details Tomebound looks up again after a restore, such as images, prices, and rules text. A backup must be smaller than 8 MB to restore and must fit your account storage limit; if an export is larger, its receipt says so. Stay online during restoration. If your account or collection changes while the preview is open, close it and open the file again to review the current state.
History and recovery points can help undo big changes, like deleting cards or replacing your collection.
Use History to undo changes, or use tomebound recover from the CLI to review saved recovery points.
CSV exports keep Scryfall card names such as +2 Mace unchanged. User free-text fields such as tags, notes, locations, container and deck names, and purchase notes are protected when beginning with =, +, -, @, a tab, or a carriage return by adding an apostrophe. Literal leading apostrophes in those fields are escaped too, and Tomebound removes this protection on re-import. Exporting never changes the collection. TCGplayer product-detail enrichment requires sign-in. TCGplayer export skips non-English rows and reports the skipped count because its SKU index only supports English; choose Tomebound CSV to preserve languages. Moxfield, ManaBox, and Deckbox purchase-price columns are left blank because Tomebound tracks market value, not purchase cost.

Delete your account

Signed in, open Settings and choose Delete account. Export your collection first if you want a copy, then type delete my account and confirm. This permanently deletes your Tomebound account, whole collection, decks, containers, share links, history and connected apps. A single pre-deletion safety backup is kept for 7 days and then deleted automatically. It cannot be undone. You are signed out and this browser’s local collection and pending changes are cleared.
If a connection error leaves the deletion result unknown, try again; retrying is safe. You can also email [email protected] with your account email to request deletion. If Tomebound deletes your data but cannot remove your sign-in, you are still signed out; email [email protected] to remove the sign-in.