> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-guide/settings/backup.md). # Backup and restore Export the accounts and networks stored in this browser to a JSON file, and import that file on another browser or device. **Where:** **Settings → Backup**
Settings Backup page with Export JSON and the Merge and Replace import options

Export writes your account list to a file. On import, Merge adds to what is already here and Replace discards it, so the choice matters.

## Why back up The page explains: "Your accounts and saved networks live in this browser (IndexedDB). Bloxchain keeps no copy, so an exported file is the only way to move them to another browser or get them back after clearing site data." {% hint style="danger" %} The export is the only copy. Clearing site data, switching browsers or losing the device removes your list. The smart accounts themselves stay on-chain and can be imported again by address, but names, marks and custom networks are gone unless you have a backup. {% endhint %} ## Export 1. Click **Export JSON**. 2. Save the file. It is named `bloxchain-local-workspace-YYYY-MM-DD-HH-MM-SS.json`. The file contains your account list (network, address, display name, mark) and your custom networks. It contains no keys, no signatures and no secrets. It is safe to store in ordinary cloud storage, though it does reveal which accounts you track. ## Import a backup Choose one mode, then click **Choose file and merge** or **Choose file and replace**. | Mode | What it does | Undo | | ----------- | --------------------------------------------------------------------------------------- | -------------------------------- | | **Merge** | "Adds anything in the file that is not already here. Names you set on this device win." | Remove unwanted entries by hand. | | **Replace** | "Discards the list on this device and uses the file instead. Cannot be undone." | None. Export first if in doubt. | ## Limits | Limit | Value | | ----------------- | ----- | | Accounts per file | 200 | | Networks per file | 50 | | File size | 4 MB | ## Error messages | Message | Cause | | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | "That file is not valid JSON." | The file could not be parsed at all. Export a fresh file from the Platform. | | "That file is not a Bloxchain local workspace backup." | It parsed, but it is not a workspace backup: the expected structure is missing. | | "That backup was written by a newer version of Bloxchain (format N). Update this app, then import again." | The file came from a newer build than the one you are running. | | "That backup has no accounts or networks this build can read." | Nothing in the file could be read at all. | | "That file is too large to be a workspace backup." | Over 4 MB. | Going over the limits above is not an error. Entries past the cap are dropped quietly during the import, and so are individual accounts or networks whose address or chain id is malformed. You only see a message when nothing at all in the file can be read. Check the counts the import reports against what you expected. ## Moving to a new browser or device 1. On the old browser, **Export JSON**. 2. Move the file (cloud drive, USB, or send it to yourself). 3. On the new browser, open bloxchain.app → Settings → Backup and import with **Replace** (empty device) or **Merge** (device already has accounts). 4. Connect your wallet. Roles live on-chain, so nothing else needs to move. Organization accounts are not in the file. They live in the Cloud and appear when you sign in. ## Related * [Accounts](/platform-guide/accounts.md) * [Networks](/platform-guide/settings/networks.md) * [Limits and defaults](/resources/limits-and-defaults.md) * [Security best practices](/security/security-best-practices.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bloxchain.app/platform-guide/settings/backup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.