> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postqueen.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Threads and Multi-Part Posts
> Say more than one post can hold, and let her publish the parts in order
Write your post in parts. She publishes the first part, then attaches every part after it to the one that came before.
On X that reads as a thread. On LinkedIn it reads as a comment sitting under your post. You write it the same way for both, and she works out the difference at publish time.
## Adding parts
Under the last part of your post sits a button that adds another one. Each new part is a full editor block: its own text, its own attachments, its own place in the order.
| Control | What it does |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| The add button under the last part | Appends an empty part below |
| Up and down arrows | Move a part earlier or later in the run |
| Trash icon | Removes a part. It only appears once there is more than one, and it asks first: *Are you sure you want to delete this post?* |
| Delay control | Sets a wait before that part goes out. It only appears on parts after the first |
The wording on the add button follows the channel you are editing.
| Editing | The button reads |
| ------------------------------------------------------------- | -------------------- |
| Every channel at once | Add comment / post |
| A single channel configured for both, which today means Skool | Add comment / post |
| A single channel configured for posts | Add post in a thread |
| A single channel configured for comments | Add comment |
The label comes from the channel's own configuration and is a hint, not a promise. Reddit and VK read as **Add post in a thread** while the network stores the extra parts as comments. The tables further down are the authority on what actually lands.
### Media on a part
Every part carries its own attachments. Insert media from the toolbar, drop files onto the block, or paste them straight in.
One upload session caps at 1 GB. Go over and she stops you with *Upload size limit exceeded. Maximum 1 GB per upload session.*
Three channels take media on the first part only: Instagram, Twitch and Kick. On those, the later parts lose the insert-media button, and dropping or pasting a file into them does nothing at all.
### Spacing the parts out
Every part after the first can wait before it publishes. The wait starts the moment the part before it lands, so five minutes means five minutes of quiet, then the next one.
| Setting | Value |
| ------------ | --------------------------------------- |
| Presets | 1m, 2m, 5m, 10m, 15m, 30m, 1h, 2h |
| Custom | Any whole number of minutes |
| Remove delay | Publishes right after the previous part |
Delays turn a wall of text into a slow burn. Without one, each part lands straight after the part before it.
## What each network does with the extra parts
She publishes the first part, waits for the network to hand back an id, then walks the rest one at a time. Each part is attached to what came before it. What that attachment *means* is the network's business, not hers.
Every network has [its own page](/providers/overview) with the detail.
### Networks that build a thread
Each part points at the previous one, so the whole run hangs together as a single chain.
| Network | Where the later parts land |
| --------- | ------------------------------------------------------------------------------------------- |
| X | Replies chained to the part before, published as one native thread |
| Threads | Replies chained to the part before |
| Bluesky | Replies chained to the part before, with the root and the parent both recorded |
| Mastodon | Replies chained to the part before |
| Nostr | Reply notes chained to the part before |
| Farcaster | Casts chained to the part before, once per channel you posted to |
| Telegram | Each message replies to the one before it |
| Slack | Threaded replies under the message in the channel |
| Facebook | The first extra part comments on the post, and each one after replies to the comment before |
| Whop | Forum posts chained to the part before |
| Skool | Comments under the post, each one nested on the part before |
| Moltbook | Comments under the post, each one nested on the part before |
### Networks that hang the parts off the post
Here every extra part attaches to the original post rather than to the part before it, so you get a flat run of comments instead of a chain.
| Network | Where the later parts land |
| ------------- | ---------------------------------------------------------------- |
| LinkedIn | Comments on the post |
| LinkedIn Page | Comments on the post |
| Instagram | Comments on the post |
| Reddit | Comments on the submission |
| Lemmy | Comments on the post, repeated for every community you posted to |
| VK | Comments on the wall post |
### Discord
Discord sits on its own. The second part opens a thread on your original message and lands inside it. Every part after that goes back into the channel as a separate message, because the thread is created on the first extra part only and the ones that follow are not routed into it.
Two parts on Discord read the way you expect. Three or more do not, so keep a Discord run to a post and one follow-up.
### Chat channels
Twitch and Kick are live chat rather than a feed. The first part is a chat message, and every part after it is another message replying to the last.
On Twitch a part can go out as an announcement instead, depending on the message type you picked in the channel settings.
### Networks that take the first part and nothing else
Some networks have no comment or reply of their own for her to use.
The editor knows there is nowhere to put a second part, so what you write is what goes out.
* Pinterest
* Tumblr
* YouTube
* TikTok
* MeWe
* Dev.to
* Dribbble
* Google My Business
* Hashnode
* Listmonk
* Medium
* WordPress
Those seven will let you add a part in the editor even though the network has nowhere to put it. Only the first part is published, so keep everything that matters on part one.
## Breaking a long piece into parts
You wrote the whole thing in one block, and now it needs to be a thread. Where the cuts go is still your call to make.
Read it back and mark the places where one thought ends and the next begins.
One part per thought, cut at the seam you marked.
The up and down arrows move a part earlier or later if the run comes out wrong.
The character badge at the end of the attachments row counts while you type, so you can see a part cross its channel limit before you commit to the break.
## What she checks before publishing
Every part is validated on its own, not just the first one.
| Check | Applies to | What she says |
| ----------------------------- | --------------------------- | ------------------------------------------------------------ |
| Part has content | Every post, drafts included | *Your post should have at least one character or one image.* |
| Part fits the channel limit | Scheduled posts only | *post is too long, please fix it* |
| Channel settings are complete | Scheduled posts only | The specific settings error for that channel |
A part counts as filled if it has text **or** an image, so an image-only part passes the content check.
On X she counts the way X counts, weighting the characters exactly as the network does.
Drafts skip the length and settings checks, which is what makes a draft a useful place to park a long thread you are still cutting down. Promote it and the checks run.
## Next steps
The composer that builds the chain
Build a multi-part post from your own tooling
Pass `-c` more than once to thread from your terminal
What happens to the rest of a chain