A review thread on X is a short chain of connected posts, each one up to 280 characters on a standard account. Done well, it's the best format the site has for talking about a book: long enough to make an argument, short enough to read on a bus. Done badly, it's a wall of plot summary that people abandon after the second post. The difference is mostly structure.
The first post does most of the work
Most people will only ever see your first post. It appears in timelines and in search, and it decides whether anyone taps "show more." So it has to stand on its own, and it has to say what you think.
A strong opening post has three parts: the book and author, your verdict in plain words, and a reason to keep reading. For example:
Just finished Lincoln in the Bardo by George Saunders. The first 50 pages nearly lost me. By the end I was crying on a train. Here's why the weird bits are the point (no spoilers) 🧵
Notice what's missing: no plot summary, no "so I finally read," no link. The thread emoji at the end is a common signal that more posts follow, and readers on X recognize it.
Name the author in plain text rather than tagging them in the first post, unless your review is glowing and you're sure they'd want to see it. More on tagging below.
A structure that works for almost any book
You don't need to reinvent the shape for every book. This layout works for literary fiction, genre fiction and most nonfiction:
- The hook: book, author, verdict and a reason to read on.
- The setup: who, where, when, in two sentences. Only the premise, the stuff on the back cover.
- What works: the single best thing about the book, with one concrete example (a scene, a character, a sentence you won't quote in full).
- What doesn't: one honest weakness. This is what makes the rest believable.
- Who it's for: "Read it if" and "skip it if." Readers love this, and it's the post most often shared.
- Comparisons: one or two books it reminds you of. This helps people place it instantly.
- The close: your rating if you use one, a question to invite replies, and, if you have one, the link to your longer review.
Seven posts. Each one makes one point. If a post is trying to make two points, split it or cut one.
An example thread layout
Here's how that structure looks for a real book. Each box is one post, comfortably under 280 characters.
- Finished The Vanishing Half by Brit Bennett this weekend. It's a page-turner that's secretly a novel about how much of yourself you can hide. Strong recommend. No spoilers below 🧵
- The setup: identical twins grow up in a tiny Louisiana town obsessed with light skin. At 16 they run away together. Years later, one lives as Black, one passes as white, and nobody in her new life knows.
- Best thing: Stella, the twin who passes. Bennett never judges her and never lets her off the hook. Her scenes in an all-white LA neighborhood are uncomfortable in exactly the right way.
- Weak spot: the plot leans on one big coincidence to bring the families together. It works because the momentum carries you, but you'll notice it.
- Read it if you love family sagas across decades, or your book club needs something everyone finishes. Skip it if you want deep focus on just one or two characters.
- If you liked The Nickel Boys or Homegoing, this sits right next to them on the shelf.
- 4.5/5. Book club folks: was Stella's choice understandable or unforgivable? Full review on our site, link below.
The last post asks a question with no right answer, which is the single best way to get replies. A reply thread full of people arguing about Stella is worth more than a hundred likes.
Spoilers, warnings and tagging
X has no built-in spoiler tag, so you have to manage spoilers yourself. Keep the first three or four posts spoiler-free, always. If you want to discuss the ending, put a clear warning post first ("Spoilers for the ending in the next post") and keep the spoiler in a single post that people can skip. Never put a twist in the opening post or the alt text of an image.
Add content notes if a book covers heavy material, such as abuse, self-harm or graphic violence. A short line in the setup post is enough, and many readers will thank you for it.
On tagging authors: if the review is warm, a tag in the final post is usually welcome, and many authors repost kind reviews. If the review is critical, don't tag the author. They don't need to see it, and it looks like you're picking a fight. Tagging publishers or booksellers is fine either way.
Making the posts readable
Write in short sentences. A post that's one long sentence with three clauses is hard to read on a phone.
Use line breaks inside a post to separate thoughts. White space is free and it makes posts scannable.
Add one image, at most, usually in the first post: a photo of the book on your table, or your own snapshot of a page you marked (keep any visible text short). Write alt text for it, describing the image, not repeating the review.
Draft the whole thread before you post. The X composer lets you add posts to a thread with the plus button before publishing, so you can see the full shape and trim. Or write it in a notes app first and paste the posts one by one.
Count with the link in mind. A link counts as 23 characters on X no matter how long it actually is, and emoji count as two. Our tweet-sized review helper counts characters the same way X does.
When to post and what to do after
Timing matters less than people think, but weekday evenings and weekend mornings in your audience's time zone tend to work for book content. Post when you'll be around for the next hour, because replying to early comments keeps the thread alive in people's feeds.
Pin the thread to your profile if it's one you're proud of. Quote-post it a few days later with a fresh angle ("A few people asked about the ending, here's my take"), which gives it a second life without repeating yourself.
And keep a short version handy. Sometimes one post is enough, which is where a tweet-sized review earns its keep.