malahov.io

Back up and move: your whole database in one file

How to export every transcript, recording and preset into a single ZIP, move it to another computer and restore it — and what this export cannot do yet.

Requires version 1.4.40 or newer · Updated 2026-09-10

Call Copilot transcripts live only in your browser, in its local database. They are not on a server: the audio stream goes out for recognition and is not stored there. That is good for privacy and awkward in exactly one place — the database belongs to one profile of one browser. Reinstall the system, switch laptops, clear site data, and the conversations are gone.

Exporting the database closes that gap. You need it in three situations:

  • moving your data to another device — a new computer, a second browser, a work machine and a home one;
  • keeping a complete copy just in case — the file is yours, independent of the browser and of the extension;
  • restoring at any point — the database unfolds back out of that file in full, audio included.

What goes into the file

Everything the extension keeps locally: transcripts with their speakers, notes, summaries and the chat you had about the conversation, audio recordings, screenshots, prompt presets, tags and timeline markers.

What does not: the extension's own settings (site reminders, AI choice, interface language) and your account with its credits — credits belong to the account on the server rather than to the database, so on a new device it is enough to sign in with the same account.

Step 1. Open Settings → the "Backup" tab

Settings open from the gear icon in the extension's side panel, or from a link in the dashboard. The tab you want is the last one, Backup.

Step 2. See how much has piled up

The first block of the tab shows two numbers: how many sessions the database holds and roughly how much space they take. Expect the file to be about that size — almost all of it is audio, which is already compressed and barely shrinks inside a ZIP.

Step 3. Press "Download Backup"

The extension assembles a single ZIP and hands it to the browser as an ordinary download. Inside there is a database.json with the text and the database's own settings, and a blobs/ folder holding audio and images as separate files — that is how binary data survives the round trip intact.

The filename says it all: call-copilot-backup-v1.10.0-db13-2026-09-10.zip — extension version, database schema version, date. Later it tells you at a glance which file is the fresher one.

A large database takes a noticeable while to pack, and the extension holds the whole archive in memory while it does. Wait for the bar to reach the end and for the browser to offer you the file.

Step 4. Restoring on another device

Install the extension, sign in with the same account, open that same Backup tab and press Choose Backup File.

The extension asks again — and it asks for a reason: restoring does not merge the file into what is already there, it replaces the database entirely.

After Restore Backup the unpacking runs, and at the end you get a confirmation and a link to the dashboard, where the moved conversations are already waiting.

If the file is damaged or was repacked from an unzipped folder, the import breaks off after the old database has already been cleared. So on a device that has something to lose, make a fresh export first and restore only then.

What this export cannot do yet

  • The whole database, in one go, and nothing less. There is no way to pick a single conversation, a date range or particular tags — the file always holds everything. For one conversation, each entry in the dashboard has its own download buttons: the transcript as .txt, the audio, the screenshots.
  • Restoring replaces, it does not merge. You cannot fold two devices' databases into one: the one you restore into gets overwritten.
  • Manual only. No schedule, no automatic copies, no cloud sync — every export is one you start yourself.
  • Restore into the same or a newer version of the extension. A file from an older version is migrated up to the current schema on import; a backup from a newer version should not be carried back into an older build.
  • The file is not encrypted. It holds your recordings and transcripts as they are — treat it as carefully as you treat the recordings themselves.

If something does not work

What you seeWhat it means
"database.json not found in backup file"The wrong ZIP, or an archive repacked by hand. It has to be the file exactly as the browser downloaded it.
"Blob file not found: blobs/blob_0.bin"The archive is incomplete: the download broke off, or the files were unpacked and zipped again.
"Failed to export database"The export could not be assembled — usually the browser ran out of memory on a very large database. Close spare tabs and try again.
An empty dashboard right after a restoreOpen it again with "Open Dashboard" from the dialog, or reload the tab, and the list appears.
No credits on the new deviceCredits live in the account, not in the database. Sign in with the account you bought them on.