Export Chirps and import a package

When you're done, you'll have your Chirps in a .zip file, or Chirps from a .zip back in your account.

Who can do this: the account owner, on any plan.

Export

On the Chirps page:

• Export all (1) downloads every Chirp in the workspace you're in, including drafts and archived ones, as "Chirp Builder export (date).zip" (or under the Chirp's name, if there's only one).
• To export one Chirp, click ••• on its card, then Export (2). You get "(name) (Chirp Builder).zip".

Each Chirp in the .zip has its own folder with its settings, instructions, starters, picture, knowledge files and Actions (their OpenAPI schemas). Files you uploaded come out as the originals; files an AI app added come out as text. API keys, access codes and visitor data are never exported.

Import a package

The Import a Chirp package section on the Import page takes:

• a .zip you exported from Chirp Builder, or
• a zipped folder of Custom GPTs: one folder per GPT, each with an instructions.txt, and if you like a starters.txt (one starter per line), a picture named avatar, profile or icon (PNG, JPEG, WebP or GIF), and its knowledge files.

1. In the menu, click Import and scroll to Import a Chirp package.

2. Click Choose a .zip file and pick the file.

   

3. Chirp Builder reads it and says, for example, 2 of 2 Chirps imported as drafts. Each Chirp gets an Open button, and notes for anything it skipped.

Everything arrives as a Draft, so nobody sees it until you publish it. Uploading the same file again never makes duplicates. If a Chirp with the same name is already in your account, Chirp Builder asks first: OK imports it again as a copy, named for example Recipe Coach (copy), and Cancel skips it. Each import is listed under Your imports: see Check an import.

Good to know

• Add Actions' API keys again after importing; they're never part of a package.
• Pictures over 2 MB are left out of an import; add them in the editor.
• A few settings start fresh on import: the web address, letting visitors switch models (and the extra models), the whole-file limit for knowledge, and welcome content.

If it doesn't work

• "That file isn't a zip we can open." Make sure you chose the .zip itself, not a folder.
• "No Chirps found." Each Chirp needs its own folder with an instructions.txt (or an assistant.json from an export).
• "Skipped (file): not a supported knowledge file type." Convert it to PDF, Word or text and add it in the editor.