Paste your notes or pick a meeting from your app. Choose a style. Get a clean, shareable summary instantly.
Want real-time summaries inside meetings? Use the full app.
Open Meetings Brief — free →Bullet summary is the default and the right choice when you are writing for people who were in the room. Decisions, actions, open questions, next steps — nothing that recaps discussion they already sat through.
Follow-up email is for people who were not there, or who were and need it in writing. It comes back with a subject line and a sign-off, ready to paste into Gmail or Outlook. This is the one most people should use most often, because a summary that stays in your notes app changes nothing.
Quick recap is three to five sentences for a Slack message or a status update. Action items only strips everything except who owes what by when — the right format for a standup or a project tracker. Full minutes is the formal record with attendees and agenda, for board meetings, committees and anything that might be referred back to. Founder mode reframes the same notes as risks, opportunities and the one thing to watch.
You can run the same notes through several styles. The input is not consumed and nothing is stored, so generating an email and then an action list from one paste costs nothing.
Messy notes work. Fragments, half-sentences, arrows and shorthand are all fine — that is the normal input, not a degraded one. A full transcript works too, and so do the two combined.
The one thing worth adding before you press Generate is who was there. Action items need owners, and a model cannot assign a task to a name it has never seen. A single line at the top — the date, and the first names of the people in the meeting — is the highest-value thirty seconds you can spend on this page. Without it, the action list comes back with tasks and no one attached to them, which is the most common complaint about every AI summary tool and is almost always an input problem.
Deadlines behave the same way. “Priya to send scope Friday” produces a usable action item; “send scope soon” produces one nobody can check.
Three causes, in order of how often they are the real one. The notes recorded what was discussed rather than what was decided, so there is nothing definite to extract. The notes are very short, and a model asked to summarise four lines will pad. Or several meetings were pasted in at once, and the output is an average of all of them — run them separately.
Always read the action items before sending. An extraction can attach a task to the wrong person when two names appear near each other, and that specific error is expensive to discover a week later. Everything else in a summary is recoverable; a misassigned owner is not.
The notes are sent to the model to generate the summary and are not saved to an account, because this page does not have one. Nothing appears in a history you can return to — if you want to keep the result, copy or download it before you leave.
If the notes are sensitive enough that they should not go to a model at all, do not paste them here. The transcription tool runs entirely on your own device and never sends anything, but summarising is a different operation and it does need a model to do it.
Turn it into text first at the transcription page — free, no account, and the audio never leaves your machine — then paste the transcript here. For the steps on getting a recording out of your meeting tool, there are guides for Google Meet, Zoom and Teams. If you would rather improve the notes themselves, how to record meeting notes covers the four things worth writing down.
Yes, with no account and no limit on how many summaries you generate. You can run the same notes through several styles without re-pasting them.
Either works, and so do both together. Fragments, shorthand and half-sentences are the normal input rather than a degraded one. The one thing worth adding is a line naming who was in the meeting: action items need owners, and a model cannot assign a task to a name it has never seen.
Almost always because the notes never named anyone. Add a line at the top with the date and the first names of the people present, and the extraction has something to attach tasks to. The same applies to deadlines — "Priya to send scope Friday" produces a checkable item, "send scope soon" does not.
Bullet summary for people who were in the room. Follow-up email for anyone who was not, or who needs it in writing — this is the one most people should use most, because a summary that stays in your notes app changes nothing. Quick recap for Slack, action items only for standups, full minutes for a formal record, founder mode to reframe the same notes as risks and opportunities.
The notes are sent to the model to produce the summary and are not saved to an account, because this page does not have one. Nothing appears in a history you can return to, so copy or download the result before you leave. If the notes are too sensitive to send to a model at all, do not paste them here — transcription runs on your own device, but summarising needs a model.
Usually one of three things: the notes recorded what was discussed rather than what was decided, so there is nothing definite to extract; the notes are very short and a model asked to summarise four lines will pad; or several meetings were pasted at once and the output is an average of all of them. Run them separately.
Transcribe it first — free, in your browser, with the audio never leaving your device — then paste the transcript here.
Yes. Copy it as Markdown to paste into Notion or Google Docs with formatting intact, download it as a text file, or generate a clean public link the recipient can open without signing in.