Writing
How to write an X chat recap people want to read
Short answer
Within 24 hours, collect the questions and the four or five best answers to each, credit every quoted person by handle, add one or two sentences of your own on what stood out, and publish it as a thread, a post with a link or a short web page.
Key takeaways
- A recap is a selection, not a transcript: four or five answers per question is plenty.
- Credit by handle every time you quote someone, and only quote public posts.
- Publish within a day, while participants still want to share it.
- End with the next chat's date, topic and time in more than one time zone.
The chat is over, the tab is still open, and there are 140 posts under the hashtag. A recap turns that into something worth sharing: a short record that credits the people who showed up and gives everyone else a reason to come next time.
Why write a recap at all?
Because most people who care about your topic missed the hour, and a recap is the only part of the chat they'll ever see.
A recap also does three quieter jobs. It thanks the participants in public, which they share. It gives you a searchable archive of your own chat. And it forces you to notice which questions worked. Hosts who recap every week tend to write better questions within a month.
What should you collect after the chat?
The questions as posted, every numbered answer, and a note of who was new, all gathered within a few hours while search is fresh.
Search the hashtag on the Latest tab and scroll back to your welcome post. For a past chat, add a date range with since: and until:, or use the date fields in X's Advanced search. Copy the posts, oldest to newest or the other way; order doesn't matter if they're numbered.
Paste everything into the recap formatter. It drops interface text like "Reply" and timestamps, groups each A1, A2 under its question, strips the hashtag from every answer and credits each one by handle. Posts without a number are counted separately so you can decide whether any deserve a place.
How many answers should a recap include?
Four or five per question, chosen for range rather than popularity.
A good selection for each question includes:
- one answer that most people agreed with,
- one that disagreed or added a twist,
- one practical tip or resource,
- one from a first-time participant, if you have it.
Skip near-duplicates. If six people said "a paper notebook", say so in one line ("Paper notebooks were the clear favorite") and quote the best of them. Keep spelling as written unless a typo changes the meaning.
How do you credit people properly?
Name every quoted person by their @handle next to their words, and quote only public posts.
| Do | Don't |
|---|---|
| "@example_ann: Read it every winter" | quote without a handle |
| keep the answer's meaning | edit an answer to say something new |
| say "lightly edited for length" if you trimmed | merge two people's answers into one |
| remove anyone who asks | include protected accounts or DMs |
If you want to be extra careful, mention the recap in your welcome post: "We'll quote some answers in tomorrow's recap. Tell us if you'd rather not be included." It costs one sentence and saves awkward messages.
Which format should the recap take?
Use a thread for reach on X, a web page or newsletter for a permanent archive, and ideally both with a link between them.
A recap thread works natively on X: one opening post, then one post per question with two or three answers. The recap formatter can split it into posts that each fit in 280 characters. A web page has room for more answers, headings and links, and it stays findable long after the hashtag goes quiet. Many hosts post a short thread and link to the full page in the last post.
Whatever you choose, add something of your own. Two sentences at the top ("Tonight's surprise: almost everyone rereads in winter") make the recap feel written, not compiled.
When should you publish it?
Within 24 hours, and ideally the next morning in your main time zone.
Participants share recaps that include them, and they do it while the chat is still fresh. After two or three days, momentum is gone. Tag the guest, thank the regulars and end with the next session: topic, day and time in two or three zones plus UTC. The time-zone slot finder helps if you're still settling that time.
How do you recap an X Space?
Share the recording if there is one, then write a short summary with topic timestamps and speaker credits.
Hosts can choose to record a Space when they create it. Once the Space ends, X's Help Center says the recording is publicly available until the host deletes it. A written summary still matters: most people won't listen to an hour of audio, and text can be searched. List the main points with rough timestamps ("12:30 on pacing a reread") so people can jump to the part they want.
Frequently asked questions
Do I need permission to quote answers in a recap?
Public posts can be embedded and quoted, but asking is good practice. Say in your welcome post that some answers may be quoted in the recap, remove anyone who asks, and never quote protected accounts, private messages or answers that were later deleted.
Should I embed posts or copy the text?
Embedding keeps the author's own version and links back to them, but embeds can break if a post is deleted and they slow a page down. Quoting the text with a handle credit is lighter and lasts longer. Many hosts quote text and link to the hashtag search.
How do I recap an X Space?
If you recorded it, share the recording link and add a written summary with timestamps for each topic. Spaces have automated live captions for listeners, but write the summary yourself and check names. Credit speakers by handle and keep quotes short.
How long should a recap be?
For a one-hour chat with six questions, roughly 400 to 800 words on a web page, or one post per question in a thread. If it takes longer to read than the chat took to run, cut it.
Sources
- X Help Center: How to host a Space (recording)
- X Help Center: How to post
- X Help Center: How to use advanced search
Platform details checked as of November 2026. X changes features often; if something here no longer matches the app, tell us.