Import Gemini Chats: Supported Files and Limits

A Gemini export can mean several different things: a web conversation, an AI Studio session, account activity, or a Gem's configuration. Files with the same .json or .zip extension are not necessarily interchangeable.

Cakumi currently supports recognizable Gemini web conversation JSON, AI Studio JSON, and compatible ZIP packages containing those files. Google Takeout activity archives are not currently supported for direct chat import.

Start by identifying the source. That prevents a valid backup from being mistaken for a compatible migration file.

Identify what the file contains

Support for a format means there is a corresponding parser. It does not guarantee compatibility with every exporter. Third-party tools may produce their own structures; stop if the preview does not match the original.

Save Gemini Apps data through Google's official route

To obtain a Gemini Apps backup, open Takeout with the same account, deselect the default products, and choose My Activity → All activity data included → Gemini Apps. Continue to select delivery and archive options. The separate Gemini item concerns Gem data. Follow Google's download instructions for the current flow.

Check that the resulting archive contains the material you need. This official backup route is not the same as Cakumi's compatible import route. If Takeout is all you have, retain it. Successfully extracting a ZIP does not establish that another app can rebuild its conversations.

This guide does not present a browser extension's output as an official Google export. You should not need to give passwords, verification codes, or login sessions to an unfamiliar migration tool.

If you already have web conversation or AI Studio JSON

Keep the original and inspect a copy. Establish:

• Which conversation the file represents.
• Whether both speakers and a sensible message sequence are present.
• Whether attachments exist as actual files or only references.
• Whether character instructions need to be saved separately.

In AI Studio, Get code is for using a prompt in an API application. Google's AI Studio quickstart distinguishes obtaining code from saving a prompt. A generated program should not be treated as a complete, reimportable conversation backup.

If you cannot establish how your current interface provides a conversation file, preserve readable content and important instructions first. Do not assume a control shown in an older tutorial is available in your account.

Without a compatible file, the new-chat handoff method can help you prepare selected background. Describe that honestly as a manual continuation, rather than a complete migration.

Preview and select the import in Cakumi

1. Open the memory import area and choose Import chat history.
2. Select Gemini and read the supported-format guidance.
3. Choose the JSON or ZIP whose source you have identified.
4. Review the conversation list, message counts, and attachment warnings.
5. Select an existing Being or create a new one, choose the conversations, and confirm.

If asked to identify your speaker, compare the samples with the original. An unfamiliar structure may trigger model-based field identification with usage charges shown in the interface. Repeatedly submitting uncertain files is not a useful compatibility test.

If the result identifies only character information, decide whether to use Import a persona instead. That organizes a character document; it does not recreate a transcript. Review the core instructions using the character consistency guide.

Previewing uploads the file for processing. The absence of a newly created Being before confirmation does not mean that the file stays entirely on your device.

Understand attachments, long histories, and retries

An attachment has only a remote reference: that reference is not the image or document itself. When the preview reports missing resources, use a complete archive if you have one. If you explicitly accept partial recovery, record which files are absent. A message containing only a missing attachment may have no recoverable text.

The history is long: storing the transcript does not mean the model reads all of it on every turn. Background memory processing also need not finish immediately. Check the record first, then continue one specific topic.

You want to retry after a connection problem: inspect the destination first. Imports append new chats rather than automatically merging repeated copies of the same conversation.

The character feels different: compare model choice, instructions, and recent context. Records can transfer while response style changes. A ZIP cannot guarantee identical character behavior.

Finish with a clear result

Source: Gemini web / AI Studio / Takeout / other
Actual file type:
Where the original is kept:
Conversation preview matches:
Speakers are correct:
Beginning, middle, and recent text checked:
Attachments recovered and missing:
Character instructions saved separately:
Destination Being and import date:
Checks still outstanding:

If you only have Takeout data, “backed up, not imported” is a valid result. If a compatible conversation file imports correctly, record what you checked before continuing.

Use the AI chat backup checklist to organize originals and attachments. For ChatGPT records, follow the separate ChatGPT import steps rather than mixing the two sources' structures.