Exporting a transcript here means finding the file, not unlocking a feature.

Most notetakers make you ask permission to leave. The transcript lives in their account, behind their login, and "export" is a button that generates a copy of something that was theirs to hold in the first place. That's not how it works when the transcript was never uploaded anywhere to begin with — it exists as a plain text file on the Mac from the moment it's written, which changes what "exporting" it actually means.

What's different about exporting something that was never uploaded

That exchange is close to the literal truth of it. Because the transcript is a text file the moment the recording finishes, "exporting" it isn't a distinct step the app has to perform on request — it's the ordinary business of opening, copying or attaching a file, the same as any document already sitting in Finder. There's no format lock-in to work around and no button to hunt for in a settings menu, because there was never a proprietary container the text was trapped inside.

Step 1 — find the transcript in the app's archive

Each recording in the archive keeps its transcript alongside the audio and the generated minutes, listed as one entry rather than three things to track down separately. Opening that entry shows the transcript as readable text on screen, which is also the first and often only "export" step most people need — reading it directly, without moving the file anywhere at all.

Step 2 — copy the text straight out

Transcript text behaves like any other text on the Mac: selectable, copyable, and pasteable into an email, a document, a chat message, or a project management tool without any conversion. For a quick "here's roughly what was said" share, this is usually faster than a formal export — select the relevant lines, copy, paste into whatever the recipient actually reads.

Step 3 — hand over the whole file when the format matters

For a full, timestamped, speaker-labeled record rather than a pasted excerpt, the transcript exists as a file that can be attached to an email or dropped into a shared folder exactly the way any document would be. There's no account the recipient needs and no link that expires — a transcript sent this way is just a file someone opens, the same as a PDF or a Word document, because structurally that's what it is.

Step 4 — export the minutes instead, when the full transcript is too much

Not every recipient wants forty minutes of back-and-forth. The generated minutes — decisions, actions and open questions distilled from the same call — are their own separate file, short enough to paste directly into an email or a status update. What actually separates a transcript from a set of minutes matters here: picking the wrong one means either overwhelming someone with the full conversation or leaving out the specific line they actually needed.

Step 5 — convert to PDF, if a formal record is what's needed

For situations where a formal, non-editable document matters more than a plain text file — a record handed to a client, or attached to a file that needs to look finished — macOS's own print-to-PDF, available from any app that can open a text file, turns the transcript into a PDF without needing a dedicated export button built into the app itself. It's one extra step rather than zero, and it uses a tool that's already part of the Mac rather than a feature that has to exist inside this one.

Why there's no dedicated "Export" button to look for

It's worth being direct about this rather than implying a feature that isn't there: Coii AudioNotes doesn't have a single button labeled "Export" that converts a transcript into some other format. What it has instead is a transcript that was already a plain, readable file the moment it finished being written — which means there was never a locked format to build an unlock mechanism for. The absence of an export feature and the presence of an already-exportable file are, in practice, the same thing described two different ways.

How this compares to exporting from a cloud notetaker

A cloud tool's transcript starts out living on the vendor's servers, tied to an account, which means getting a usable copy onto your own machine is a real step — a download, sometimes gated behind a plan tier, sometimes limited in format or retention window. Coii AudioNotes against Otter covers that difference directly: one of the two starts the transcript on a server and the other starts it on the Mac doing the recording, and that starting point is what determines whether "export" is a meaningful step or a formality.

Sharing a transcript with someone who doesn't have the app

Because the file is plain text rather than a proprietary format, whoever receives it doesn't need Coii AudioNotes installed, an account created, or a link followed to read it — a text file opens in whatever's already on their machine, from Mail's own preview to Notes to a plain text editor. That matters more than it sounds: sharing something with a client, a colleague on a different tool, or a lawyer who has no reason to install new software works the same way it would for any document, because that's structurally what a transcript here is.

What doesn't come along with the export

A cloud notetaker's export sometimes carries metadata a plain text file doesn't — a link back to a shared workspace, a comment thread attached to specific lines, collaborative editing history. None of that exists here, because none of it was ever built on top of an account-based system in the first place. What's exported is exactly the transcript: the words, the speaker labels, the timestamps, and nothing tied to an online presence that stops working once a subscription lapses.

Turning a transcript into something more structured

A raw transcript, timestamped and speaker-labeled, is sometimes more detail than a reader wants but exactly the right detail for a specific purpose — quoting someone precisely, checking the order events were described in, or settling a dispute about who said what. Because it's plain text, it's also editable in the ordinary sense: opened in a word processor, headers can be added, irrelevant small talk trimmed, and the result saved as a cleaner document without needing a feature built into the app to do any of that reformatting. The transcript the app produces is a starting point, not a finished, locked artifact.

Exporting to share with a non-Mac user

Because nothing here depends on a proprietary app or account, a transcript exported as a text file or a PDF opens identically on Windows, on a phone, or in a browser — there's no Mac-specific format involved once the text has been copied out or saved as a document. A colleague on a different operating system entirely can read a shared transcript the same way anyone else does, which is one advantage of the format being ordinary text rather than something tied to the app that produced it.

What happens if the original recording is later deleted

Deleting a recording from the app's archive removes that entry — the audio, and whatever transcript or minutes were generated from it — but has no effect on a copy that was already exported somewhere else beforehand. An emailed transcript, a PDF saved to a case file, a pasted excerpt in a project doc: none of those reach back into the archive, and none of them get deleted along with the original. That independence is worth knowing both ways — a useful safety net if the archive entry is removed by mistake, and a reason to be intentional about where exported copies end up, since deleting the original afterward doesn't retract anything already sent.

Keeping an exported copy separate from the archive

Once a transcript has been copied out — pasted into an email, saved as a PDF, or moved into a shared drive — that copy is independent of the app's own archive from that point forward. Editing or deleting the original recording later doesn't reach back and change a copy that's already been sent, which is worth knowing before treating an exported transcript as a live, synced document rather than a snapshot taken at the moment it was copied.

Doing this for a batch of transcripts, not just one

There's no bulk export tool built into the app for pulling a month's worth of transcripts out at once — each one is opened, copied or attached individually, the same as reading through a month's worth of any other kind of file would be. For someone with an archive of local transcripts that's grown past a handful of meetings, that's a real limitation worth naming rather than glossing over: this is built around one recording at a time, not a bulk-export workflow for an entire quarter.

Before sending a transcript outside the Mac it was made on

Once a copy is emailed, uploaded to a shared drive, or handed off on a USB stick, it's left the environment where nothing gets uploaded by default — the transcript itself doesn't stop being useful, but the property that made it worth trusting in the first place (that it never had to leave the Mac to exist) no longer applies to that particular copy. That's not a reason to avoid sharing a transcript when sharing it is the point; it's a reason to think about where a copy is headed before sending it, the same care worth applying to backing up the archive it came from.

Renaming a file before sending it anywhere

The app's own archive organizes recordings by date, which is efficient for browsing internally but often not the most useful name once a transcript leaves the archive and gets attached to an email or dropped into a shared folder. Renaming an exported file to something a recipient will recognize at a glance — the client's name, the project, the date written in full — takes a few seconds and saves the person on the other end from opening three similarly-dated files before finding the right one. It's a small habit, but it's the difference between an export that's genuinely useful to someone else and one that's only meaningful to whoever made it.

Exporting from more than one Mac on the same licence

Each of the up to three Macs covered by a single licence keeps its own separate archive, which means a transcript made on a laptop has to be exported from that laptop specifically — there's no shared account where a recording made on one machine becomes reachable from another. For someone who records on a laptop but does most of their writing on a desktop, that's worth planning around: getting a transcript from one Mac to the other is the same file-transfer step as getting it to anyone else, since there's no sync tying the two together automatically.

A quick reference for which file to send

When it's not obvious which of the three files a recipient actually wants, the shortest rule is this: send the minutes to someone who needs the outcome, send the full transcript to someone who needs the exact wording, and keep the recording itself for your own records unless someone specifically asks for the audio. Most requests for "the notes from that call" are really asking for the minutes; most requests for "exactly what was said" mean the transcript. Getting that distinction right the first time saves a second follow-up asking which one was actually wanted.

What it costs, what it runs on

None of the above requires anything beyond the app itself: $19 once, a 30-day trial with no card and no account, running on macOS 13 Ventura or later on Apple Silicon or Intel. There's no API key to configure before transcription works in the first place — what that means in practice covers the setup side of the same story this page has been about getting text back out of.