01

Save the message, not a screenshot of it

A Teams message is often where a decision first becomes visible: an owner accepts work, an engineer posts a command, or a meeting ends with a clear next step. A screenshot preserves the appearance but not the text, links or structure someone needs to reuse later. A clean Markdown note can be searched, versioned, compared and opened in a normal editor.

Start with the exact messages worth keeping. Copy the decision and the surrounding context that explains it, then add the channel name, date and source link yourself if those facts matter. Do not assume that a copied message includes thread history, reactions, attachments or permissions. Those belong to Teams and may need a separate, deliberate record.

  • Decision or confirmed fact
  • Owner and due date
  • The minimum context needed to interpret it
  • A source link when the reader can access Teams
  • Attachments and thread replies called out separately

Open Teams to Markdown · Markdown and file exports

02

Copied text can arrive in more than one representation

The same copied selection can offer HTML and plain-text representations. The W3C Clipboard API describes these as alternative formats of one clipboard item. The richer form can retain paragraphs, lists and links, while plain text may lose the relationships that made the message understandable. Neither form should be treated as an unverified export of the whole Teams conversation.

Pasteful compares the useful source representations and converts semantic structure into Markdown. It does not fetch a link, inspect the Team, read nearby messages or invent text that was not in the copy. If a browser exposes only plain text, keep the original message available while you check the result.

W3C: Clipboard API and multiple representations · Open rich text to Markdown · Copy rich text into a Markdown file

03

Make a small, portable Markdown note

Use headings for real sections, ordinary list markers for actions and a code fence only for commands or output that must keep its spacing. Write a message URL as a labelled link when the destination can resolve it, but include enough surrounding words that the note still makes sense to someone without Teams access. A portable note should explain the decision, not merely point back to a private chat.

Keep the Markdown flavour simple. CommonMark covers paragraphs, headings, lists, quotations, code blocks, links and emphasis. Tables, task-list boxes, callouts and embedded files vary between editors. When one of those structures carries meaning, add a plain explanation near it rather than hoping a nonstandard extension will survive every notes app or repository.

  • Use one clear title for the saved decision
  • Keep ordered actions in an ordered list
  • Put commands in fenced code blocks
  • Use descriptive link text
  • Turn a table into labelled rows when portability matters

CommonMark specification · Export text as a Markdown file

04

Separate source cleanup from editorial cleanup

First make the copied structure legible: remove accidental extra blank lines, retain the correct link destinations and preserve code literally. Then make an editorial decision about what belongs in the durable note. A chat reply such as “yes, do that” becomes useful only when the preceding decision is included or named. Do not let a formatter silently choose that context for you.

Pasteful's deterministic cleanup can show changes before you copy, but it should not be used to rewrite a decision. Keep the source message open until the new note has been reviewed. That gives you a clean boundary between a mechanical conversion and the human judgement about what the record ought to say.

Pasteful cleanup rules · Why deterministic cleanup beats another AI formatting prompt

05

Verify the file where it will live

Download the Markdown file or paste the Markdown into the repository, notes app or editor where the record will live. Check the heading hierarchy, one link, the deepest list item and every code block. If the destination renders a line differently from the preview, fix the source Markdown and recheck rather than editing a rendered view with no clear record of what changed.

A local Markdown file is portable, not automatically private. Pasteful formats it in the browser, but the place you save next may sync, publish or index the file. Choose storage deliberately, and do not include access tokens, confidential URLs or private chat material in a note that does not need them.

Open Teams to Markdown · Pasteful privacy model