How to write a chat recap or transcript today

Years ago, a chat host could paste a hashtag into a transcript service and get every post from the hour in a neat archive. Most of those tools are gone. That's partly good news. A full transcript of 600 posts was rarely read anyway. A short, edited recap that pulls out the best answers is more useful, gets shared more, and brings people back for the next session.

This guide covers collecting the material, quoting fairly, and a structure you can reuse.

Collect while it's fresh

Do the gathering within a day, while you still remember which answers stood out and before the posts drift down in search.

1. Search the hashtag and open the Latest tab. Scroll from the start time to the end. For a big chat, search for the hashtag plus the label, such as #NewsletterChat A3, to see the answers to one question.
2. Bookmark as you go. X's bookmarks let you save candidate posts privately. Bookmark during the chat if a co-host is running the questions.
3. Keep a simple document open. For each question, paste the links of the two to four answers you might use. Links are enough; you'll embed or quote them later.
4. Note the numbers. How many people took part, any guest, anything memorable that happened. Exact totals aren't needed; "about 40 people" is honest and fine.

For a Space, collection is different. If you recorded it, listen back and write timestamps for the strongest moments. Quote speakers only from the recording, and only things they said on the record in a public Space.

Quote fairly

Your recap reuses other people's words, so a few rules keep it fair and keep you on good terms with your participants.

Embed when you can. X provides an embed code for any public post (in the post's share or "more" menu, or through X's publish tool for websites). An embedded post shows the author's name, handle and words exactly as written, links to the original, and stops displaying if the author deletes it. That last part matters: it respects someone's choice to take a post down.

When you quote in text, credit and link. Use the person's handle, quote accurately, and link to the original post. Keep quotes short, a sentence or two. Don't edit wording except to fix an obvious typo, and never change the meaning by cutting.

Don't quote what wasn't public. Answers posted publicly with the chat hashtag were meant for an audience. Posts from protected accounts, messages from direct messages or group chats, and things said in a Space that wasn't recorded or public are different. Ask before using any of them.

Respect opt-outs. Some people say in the chat that they'd rather not be featured. Some ask later. Remove their posts promptly and without fuss.

Screenshots are a last resort. A screenshot doesn't update when someone deletes or corrects a post, and it isn't readable by screen readers. If you must use one, add alt text with the full post text and the author's handle.

A structure that works

Readers skim recaps, so make the structure obvious:

Title: [Topic]: highlights from #YourChat, [date]

Intro (2-3 sentences): what the session covered, who the guest was,
roughly how many joined, and a link to join next time.

Q1: [question text]
  - 1 sentence summing up the general direction of answers
  - 2-3 embedded or quoted answers

Q2: ... (same pattern for each question)

Takeaways: 3-5 short points in your own words

Next session: date, time in 2-3 zones, topic, guest

Summarize in your own words between quotes. "Most people said their first subscribers came from friends and coworkers, but a few had real luck with a single guest post" tells readers more than six embedded posts in a row.

Where to publish it

A recap can live in a few places:

• A blog post or web page is best for anything you want people to find later. It can hold embeds, it's searchable, and it doesn't scroll away. Our recaps page has more on this.
• A thread on X works for short recaps. Post the takeaways first and quote the best answers in replies.
• An article on X, where available to your account, works if you'd rather keep everything on the platform.

Wherever it lives, post a link to it from your account, reply to your wrap-up post with the link, and tag the people you quoted. Being featured is a good reason to share, and most of them will.

Recaps for Spaces

A Space recap tends to be shorter and more narrative: who spoke, the three or four main points, and a link to the recording if you kept one. Add timestamps so people can jump to the part they care about ("12:40: how she found her first sponsor"). If the Space wasn't recorded, say so and stick to summarizing. Don't present your paraphrase as a direct quote. See hosting an X Space for recording settings.

Small things that help

• Write the recap within three days. After a week, it reads as an afterthought.
• Use the same title format every week so regulars recognize it.
• Link to last week's recap at the bottom. Over time, that becomes your chat's archive.
• Fix mistakes when people point them out, and thank them for it.

Common questions

Can I quote people's answers from a public X chat in my recap?

Short quotes with the person's handle and a link to the original post are standard practice for public chats. Embedding the post is the cleanest method because it shows the original in full and disappears if the author deletes it. Ask first before quoting anything from a protected account, a direct message or a group chat.

Is there still a tool that makes automatic Twitter chat transcripts?

Most of the old transcript services shut down or stopped working after changes to X's API. Today a recap is usually written by hand from the hashtag's Latest results, with a few embedded posts.

How long should a chat recap be?

Usually 500 to 1,000 words: a short introduction, a section per question with two or three quoted answers, and a closing note with the next session's date.