Pro feature · v3.0
Export to Apple Files.
Your whole project, as a real folder tree, in the Files app.
Save an entire project — and every sub-project nested under it — to Apple Files in one pass. Each story becomes a folder containing its AI summary, a consent-redacted transcript, a metadata file, and the story's photos and files. The exported tree mirrors your project hierarchy exactly. iPhone, iPad, and Mac.
Sometimes the inbox isn't the destination.
Email a summary and the recipient reads it. But a client engagement, a research study, a legal matter — those want to live somewhere durable. A case folder. A project share. A backup drive you control. Not buried inside an app, and not one summary at a time.
Until now, getting a whole project out of Bonfiyah meant exporting each story by hand and reassembling the structure yourself. The hierarchy you'd carefully built — projects, sub-projects, the stories under each — didn't come with it.
Export to Apple Files takes the whole tree at once. Pick a project, choose a destination in the Files app, and Bonfiyah writes the entire folder structure — every sub-project as a sub-folder, every story as a folder of its own — straight to disk, iCloud Drive, or any cloud you've connected.
Sample export
What lands in the Files app.
A project with two sub-projects and four stories, exported as a folder tree. Sub-projects become sub-folders; each story is a folder of its own.
📁 Acme Q3 Migration/
├── 📂 Kickoff/
│ └── 📁 Sponsorship review — Mar 18/
│ ├── AI Summary.md · Pro AI
│ ├── Transcript.txt · consent-redacted
│ ├── Metadata.json
│ └── 📷 Photos & Files/
├── 📂 Vendor selection/
│ ├── 📁 DPA redlines — Apr 1/
│ │ ├── AI Summary.md
│ │ ├── Transcript.txt
│ │ ├── Metadata.json
│ │ └── 📷 Photos & Files/
│ └── 📁 Budget revision — Apr 22/
│ └── …
└── 📁 Cutover plan — Apr 22/
└── …
Identical structure on iPhone, iPad, and Mac. Drop it in iCloud Drive, On My iPhone, an external drive, or any cloud you've connected to Files.
How the export works.
- 1
Pick a project. The whole tree comes with it.
Choose any project and tap Export to Files. Bonfiyah walks the project and every sub-project nested beneath it, top to bottom, and assembles the matching folder hierarchy in memory. You don't select stories one at a time — the structure you already built is the structure you export.
- 2
Each story becomes a folder.
Inside every story folder: the AI summary (for Pro AI subscribers), a consent-redacted transcript, a metadata file with the date, duration, participants, tags, and consent/privilege markings, and a Photos & Files folder holding everything you attached to that story. Transcripts, metadata, photos, and files are always included; the AI summary is the one Pro-AI-gated piece.
- 3
Consent redaction runs before anything is written.
The transcript in each folder is filtered through the same consent and redaction logic as the Send flow — the Attorney-Client Privileged, Internal-Use-Only, Unknown-Consent, and Revoked toggles. Non-consenting speakers are redacted per your toggle choices before the file is created. There is no path that writes a more-exposed transcript to disk than you'd send by email.
- 4
The system Save-to-Files picker takes it from there.
Bonfiyah hands the finished tree to the standard "Save to Files" surface — the Files picker on iPhone and iPad, the Finder-backed save panel on Mac. You choose the destination: On My iPhone / iPad, iCloud Drive, an external USB-C drive, a network share, or any cloud provider you've connected to Files. Bonfiyah never sees where it lands.
Why a folder tree, not a zip.
A single archive file is a dead end — you have to unpack it before it's useful, and most people never do. A real folder tree in the Files app is alive the moment it lands. You can open the AI summary on your iPad, drop the whole project into a shared iCloud folder for a colleague, hand the case folder to a client's Box, or keep a controlled copy on an external drive.
The structure carries meaning. Because sub-projects become sub-folders and stories become folders, the export reads the way your library reads. Six months from now, the folder named after the engagement still has the kickoff under Kickoff/ and the contract work under Vendor selection/ — without you having reconstructed any of it.
And because it honors the same consent model as everything else Bonfiyah lets out, the folder you hand someone is already as redacted as the email you'd have sent them. The destination changed. The privacy rules didn't.
Privacy & consent
The same consent rules as a send — applied to disk.
Export to Files is governed by the identical consent and redaction model as Bonfiyah's Send flow. The four toggles you already know — Attorney-Client Privileged, Internal-Use-Only, Unknown-Consent, and Revoked — control exactly what appears in the exported transcripts the same way they control what goes into an email or a PDF.
As of the latest release, Internal-Use-Only speakers are included by default when you send or export to internal recipients; switch the toggle off before sharing externally. A privileged story carries its banner and markings into the exported metadata, and the most-restrictive marking always wins — exactly as it does on every other surface.
The tree is assembled on-device and written straight to the Files destination you choose. The AI summaries were generated earlier; export simply writes the text you already have. Read the full consent + privilege reference →
FAQ
Does this require Pro AI?
Export to Apple Files is a Pro feature — it's included in Pro and Pro AI. The transcripts, metadata, photos, and files export on Pro. The one Pro-AI-only piece is the AI summary file inside each story folder: if you're on Pro without AI, the folder still exports with everything else, just without the AI summary document.
Where do the files actually go?
Anywhere the system Files app can write: On My iPhone / On My iPad, iCloud Drive, or any Files location you've connected — Dropbox, Google Drive, Box, a Working Copy repo, an external USB-C drive on iPad, a network share on Mac. Bonfiyah hands the folder tree to the standard "Save to Files" picker and you choose the destination. We never see where it lands.
What's in each story folder?
One folder per story, named after the story. Inside: the AI summary (Pro AI), a consent-redacted transcript, a metadata file (date, duration, participants, tags, consent and privilege markings), and the story's photos and attached files. Sub-projects become sub-folders, so the exported tree mirrors exactly how your library is organized.
Are non-consenting speakers redacted?
Yes. The export honors the exact same consent and redaction model as the Send flow — the Attorney-Client Privileged, Internal-Use-Only, Unknown-Consent, and Revoked toggles. Whatever a speaker's state would redact in an email or PDF export, it redacts the same way in the exported transcript. There is no looser path to disk than there is to email.
Does it work on Mac as well as iPhone and iPad?
Yes — iPhone, iPad, and Mac. It uses the system "Save to Files" surface on each platform, so on Mac the destination picker is the familiar Finder-backed save panel and on iPhone and iPad it's the Files picker. Same folder tree, same consent rules, every device.
Is anything sent to a server during export?
The folder tree is assembled on-device and written straight to the Files location you pick. The AI summary text was generated earlier when you ran the summary; export just writes the text you already have. If you choose an iCloud Drive or third-party-cloud destination, that provider syncs the folder the same way it syncs anything else you save there — that's your storage, not ours.
Used in these workflows
Where exporting the whole project earns its weight.
See the full eighteen-workflow catalog →
See a sample export
We'll send you a sample project folder tree — the exact structure Export to Apple Files writes, summary, consent-redacted transcript, metadata, and photos in place — so you can see what lands in Files before you upgrade.
No spam. We use ConvertKit. See our privacy policy.