Mixboard offline on 28.09: exporting prompts and assets before Bubble bulk catalogs via BIAIG

Why this matters now

According to digest signals and secondary coverage (e.g. Jetstream’s reproduction of the shutdown notice), users were told that after 28 September 2026 the Mixboard site goes offline and stored data—boards, generated images, and prompts—will no longer be accessible. Scout did not find a matching indexed shutdown post on blog.google; details rely partly on reproduced email/in-app text, so verification risk remains. Time zone and exact cutoff time are not stated in the packet. On 28 Sep 2026, automated fetches of mixboard.google.com/projects sometimes returned sign-in, sometimes 403—do not infer user-visible outage from bots alone.

Mixboard’s launch post (23 Sep 2025) positions it as a Labs experiment for prompt-driven boards and edits. Community write-ups frame multi-image canvas workflows as “bulk” generation (example third-party note)—that is not the same as durable catalog export. If your prompt library lived only in Mixboard, continuity risk is already real.

What export actually covers

The documented path is manual, per board:

1. Open mixboard.google.com/projects (sign-in required).
2. Expand the project, board ⋮ menu → “Download as PNG”.
3. You get a ZIP of that board’s images; repeat for every board/project.

There is no cited account-wide bulk export. Aggregators such as ScriptByAI align with the notice: post-shutdown, prompts in Mixboard are gone, while official save steps emphasize image ZIPs, not prompt/metadata export. Inference (not confirmed by Google): treat prompt text as high loss risk—copy prompts externally; do not assume ZIP files are your prompt source of truth.

Scout open questions: whether PNG/ZIP embed retrievable prompt metadata; whether export includes text blocks, uploads, and share state—unanswered in this packet.

Pre-shutdown operational checklist

Images

• Inventory every project/board (names, dates) to reduce missed-board risk.
• Run “Download as PNG” per board; store ZIPs in a consistent folder or push extracted files to durable storage.
• Large catalogs mean manual toil—assign an owner and finish before 28.09, not at the last hour.

Prompts and catalog rows

• For each asset entering a Bubble bulk catalog, record prompt text, any UI-captured settings, legacy board reference, and a version field.
• If rows already live in a spreadsheet, use that as a bridge; aim for Bubble DB as canonical after migration. Worth reading next: Fragmented bulk-tools niche: Apify spreadsheet. Same topic: Magnific One (Brand Kit +. Worth reading next: After 8 Oct: FLUX 3.

Avoid

• Treating any experimental Labs UI as the sole system of record (launch ~Sep 2025, shutdown ~Sep 2026 per secondary timelines).
• Confusing canvas “bulk generation” with portable bulk export.

Mirroring in Bubble: database + files

Public Bubble patterns (not Mixboard-specific):

• Files: The Bubble API—pass file/image parameters as a hosted URL or base64 for server-side storage after you unpack ZIPs or upload to your CDN.
• Bulk runs: Schedule API workflow on a list for per-row backend processing; mind intervals, overlap, and HTTP 429 when calling external APIs (scheduling guidance). Worth reading next: gpt-image-1 sunsets 23 Oct 2026:. Worth reading next: OpenAI Decisions API (preview): classification. Worth reading next: gpt-image-1 sunsets 23 Oct 2026:.

Minimal data model (editorial suggestion)

• CatalogRow: slug, prompt_text, status, mixboard_board_ref (legacy), external_job_id, version.
• Asset: Bubble file field, filename/checksum, parent row.
• RunLog: run_id, timestamp, row_id, outcome—so reruns do not depend on Mixboard session state.

BIAIG: orchestration after spreadsheet/UI prep

Important: public search found no documentation for “BIAIG” as a Bubble bulk-catalog layer; unrelated entities use the same acronym. The following is an editorial playbook from the approved brief: BIAIG sits after row prep (sheet/editor), not as a substitute for Mixboard export.

1. Input contract: jobs consume only Bubble/API rows in ready state; prompts and file URLs are already in your app.
2. Idempotent reruns: key on row id + version or prompt hash; avoid duplicate assets unless force_regenerate is set.
3. No external UI dependency: pipeline steps must not require a logged-in Mixboard; images come from Bubble storage or your image API.
4. Rate limits: stagger scheduled workflows—Bubble supports large lists in docs, but concurrency and third-party API limits cap real throughput.

This article deliberately does not restate separate pieces on ~500-row chunking or OpenArt-vs-BIAIG placement; it focuses on continuity when Mixboard disappears.

Summary

Item	Action
Images	Per-board “Download as PNG” ZIP; mirror into Bubble/storage
Prompts	Copy manually into canonical DB/sheet before shutdown; ZIP is not proven prompt backup
Catalog reruns	Bubble scheduled API workflows + internal BIAIG from row state, not Mixboard
Trust	Shutdown details mostly secondary sources; no indexed primary Google shutdown page found

If you still have access, run one documented export pass and migrate prompts in parallel. After 28 Sep 2026, public sources do not describe a way to recover data left only in Mixboard.