Account data export: formats, contents and limits
Export supported Gab AI account records as JSON or ZIP. Understand the included chat history, memories and file metadata, then check the archive for completeness.
Open the account export controls
Sign in and open Settings → General. Use the account data export action for your own records. Export can contain private conversations and account information; inspect it locally rather than posting it in a public chat or report. Authenticated API exports have their own setup.
JSON and ZIP have different packaging
The current account builder supports a JSON bundle and a ZIP package. ZIP includes a README, manifest, record JSON files, readable per-conversation Markdown and memory text. These are supported account records, not a complete machine backup or automatic restore of every setting.
Contents and exclusions
| Topic | What to check |
|---|---|
| Conversation records | Supported account conversations and their included message history. Deleted and temporary records are excluded from the account export. |
| Memory, agents and collections | Supported saved records. Exporting them does not automatically import them into another product’s memory/settings system. |
| Files | File metadata and retrieval URLs are different from including each binary file in the archive. Preserve needed original files separately through the product’s supported controls. |
| Account and operational records | Supported profile, bookmarks, task/voice metadata and transaction-related records can appear. Certain credential and payment-reference fields are excluded; inspect the actual archive. |
| Credentials | Account export excludes password/reset/MFA secret fields and API-key secret values. An export remains private even when those fields are excluded. |
Inspect counts and truncation
Account exports have record limits. Current caps include 5,000 conversations, 5,000 memories, 10,000 file records and 1,000 agents or collections. Other collections have their own bounds. Check the manifest and truncated flags; a large account may need support to obtain additional records. Do not describe a capped archive as literally everything.
Find your records inside the package
The local export example produced conversation records, readable chat files and saved memory text. In your own export, use the manifest and record counts to check what was included; file metadata and retrieval URLs are separate from original file contents.
Export and import are different operations
The chat importer can read supported conversation data, but that does not establish a full restore of every exported collection, credential, setting, binary file or provider state. Check the import guide’s field scope, then set up useful memories and settings separately.
If export is incomplete or fails
Keep the displayed error and check your account state before retrying. Do not assume an interrupted response is a complete archive. Review record counts and truncation after a successful export. Contact support for missing data without sending passwords, full payment information or an entire private archive to an unapproved recipient.
Keep a copy you understand.
Use the account export action in Settings → General. Review the manifest, counts and truncation flags, and keep any original files you also need.
Open account settingsRead the import guide