Do my notes need a particular format?
No. Headings and bullets help, but plain lines work too. Explicit markers such as Action:, Decision:, and Q: always win when the wording is ambiguous.
Raw notes in, action items out.
Paste the notes you typed during a meeting, in whatever shape they are in. Meeting notes pulls out the decisions, the action items, and the open questions, gives each one an owner from the attendee list, and writes it all back as clean Markdown, JSON, or CSV.
Loading the toolbox.
You do not have to take our word that your meeting notes stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your meeting notes. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your meeting notes elsewhere.
Most meeting notes are written fast: a few bullets, half sentences, names in shorthand, and the important parts buried between status updates. The converter reads those notes the way a careful colleague would and sorts every line into one of four kinds:
The result is a structured summary you can paste into a ticket, a wiki page, a chat thread, or an email, with every action item showing who owns it.
Three kinds of signal are read, from strongest to weakest.
Action:, TODO:, AI:, Follow-up:, Decision:, Agreed:, Resolved:, Q:, Question:, and TBD:, plus Markdown checkboxes, where [ ] is an open action and [x] is a done one.Headings can be Markdown (# Decisions), bold text, a line ending in a colon, a line in capitals, or a short line sitting directly above a bulleted list. Wrapped lines that are indented under a bullet are joined to that bullet, so a long action item stays one item.
The converter looks for a line such as Attendees:, Present:, Participants:, or In attendance:, either followed by a list on the same line or by bullets underneath. Each person can be written in several ways, and all of them are understood:
Ana Ruiz (PM): a name with a role in parentheses.Priya Natarajan (PN): a name with initials, so a later line starting PN: is assigned to Priya.Ben Ode <ben@example.com>: a name with an email address.@dana: a chat handle.Chen Li - eng lead: a name and role separated by a dash.A line starting Absent:, Regrets:, or Apologies: lists the people who were not there. Facilitator, chair, and note-taker lines add that person with the role filled in. People are de-duplicated, and anyone listed as absent is removed from the present list.
Owners are matched against the attendee list by full name, by a unique first name, by initials, by handle, or by email, so "Ana to write the announcement" belongs to Ana Ruiz. The forms recognized are:
Owner: Eli Park, assigned to Ana, or a trailing (Chen) or [Chen].@dana.The findings list warns about every open action that has no owner, notes owners who are not on the attendee list, and flags items owned by someone who was absent, so nothing is quietly dropped. Due dates are kept exactly as written, such as "by Friday", "EOD", or "11/20", and are never converted into a calendar date that could be wrong.
Markdown gives a ready-to-paste summary: the title, date, attendees, and absent list, then Decisions, Action items as checkboxes with the owner in bold and the due date, Open questions, and the remaining notes under their original headings. Tick "Group actions by owner" to get one heading per person instead, which is handy when each person copies their own list.
JSON holds the same content as data, with every item carrying its owner, its due text, its done flag, and the line it came from, ready for a script or an automation. CSV writes one row per item with type, text, owner, due, status, and line, and opens directly in a spreadsheet or imports into most task trackers. Any cell that starts with an equals, plus, minus, or at sign gets a leading apostrophe so a spreadsheet never runs it as a formula.
No. The converter is a transform, not a notes app. Your notes are read in this browser tab, kept in memory only while the page is open, and never saved to storage, never put in the address bar, and never sent to a server or an AI service. The only way they leave the page is when you copy or download the result yourself. Meeting notes often contain names, plans, and numbers that are not public yet, which is exactly why it works this way.
Elsewhere in the toolbox: Hash, Base, TOTP, XML, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.
No. Headings and bullets help, but plain lines work too. Explicit markers such as Action:, Decision:, and Q: always win when the wording is ambiguous.
It matches names, first names, initials, handles, and emails against the attendee list, and reads forms such as "Ana to ...", "Ben:", "Owner: Eli", "(Chen)", and "@dana".
No. Due text such as "by Friday", "EOD", or "11/20" is kept exactly as written, so it never shifts to the wrong day.
No. They stay in this tab, are never saved or sent, and leave the page only when you copy or download the export.