Threads video is not a Reels master
A Reel is not a Threads master. Chrome, caption length, and conversation sit in different places. Re-export the cut.
Threads video is not a Reels master. Cross-posting the Reel MP4 is a repost with a different bottom bar. Threads is a conversation feed that happens to play video. Reels is a full-screen watch. The chrome, the caption field, the first line, and the ask are not in the same place. Repurposing means a new asset. A scheduler that fires one 9:16 file at both apps is how a legal Reel caption sits under Threads playback controls, and how a Threads joke arrives on Reels with no cover and a 500-character leftover.
Two feeds, two jobs
Reels is a vertical player. 9:16, 1080×1920, full-screen, a username and audio pill at the top, a button column on the right, caption and CTA chrome at the bottom. The file is the post. The hook is frame one. Hook rate is the meter. Saves and shares sit on that watch.
Threads is a text feed that will play a video. Meta's July 2023 introduction still describes videos up to five minutes. Reels recording help has allowed much longer files, with a published discovery cutoff past three minutes for new audiences. Shorts still hard-caps at three. Threads will take four minutes. That extra minute is not a reason to paste a Reel. It is a reason to keep a format that actually needs it — a demo, a caveat, a failure then a fix — and to write a text post that sets it up.
Hootsuite's video-requirements note, updated 28 August 2026, lists Threads caption format as not supported on the scheduler path it documents, same as Instagram direct publishing. The feed still autoplays muted. Burn-in is the type the scroller sees. Platform closed captions are not the plan.
Replies are the Threads currency. A Reel that ends on a shop card and silence is a broadcast in a room that ranks conversation. Rewrite the last beat as a question, or put the question in the text post and let the video be the proof. The Reel master will not do that work.
Chrome is not portable
Safe area is per surface. A caption block that clears Reels' bottom 320px can still collide with Threads playback controls. Edge-caption Reels are the usual miss: karaoke hugging the bottom fifth, legal on Instagram, covered on Threads. Keep essential type in the upper two-thirds if the same pixels have to survive both, or — better — recaption.
The right-hand like column on Reels is not the Threads layout. Faces and packs that were composed around that rail will look off-centre in a feed unit that is not full-screen. Threads often shows tall video left-aligned with space beside it until you tap through. A 9:16 master designed to fill a phone will sit next to a paragraph. The first line of the post, not the first burned caption, is now the hook for a lot of scrollers.
Instagram captions can run long. Threads is a short text field. A pasted Reel caption that was 2,000 characters of hashtags is the wrong object. One topic, one question, a link if the surface still tolerates it. Native media still outperforms a link-only post, but the text is not optional decoration.
Nine-sixteen vs 4:5 vs 1:1 still applies. Reels wants 9:16. Threads will take 9:16, 1:1, and 16:9; vertical fills more of the phone; landscape wastes the feed. A 4:5 Instagram feed cut is a third composition. Do not treat the Reel as the parent of all three.
What to rebuild per surface
First line. On Reels, burn it. On Threads, write it in the post and burn a shorter claim in the picture so mute autoplay still has a reason to stay. A greeting is not a first-second hook on either surface.
Length. If the idea fits in 20 seconds, do not use Threads' five-minute ceiling as permission to pad. If the idea needs four minutes, do not crush it into a Reel that will not be recommended past three. Cadence is also not shared. Three Reels a week copied onto Threads is a dump in a reply culture.
Ask. Reels can carry a CTA card or a platform button. Threads wants a reply. "Link in bio" on a Threads video is a Reel leftover. Ask a question the comments can answer. Put the shop line on the surface that actually shops.
Captions. Recaption after the reframe. Burned-in captions survive the upload. Sidecar SRT will not draw on a Threads play in the feed. The AI caption generator is 165 codes and a burn-in. Check the new chrome on a phone, not on a desktop timeline.
Labels. Threads is still Meta. Organic Made with AI / AI info via C2PA and self-disclosure still exists as Meta's organic path. It is not an FTC #ad and it is not Article 50. If the file is a paid integration, disclose money on the creative. If it is a NY synthetic performer ad, the on-ad sentence still applies when NY consumers can see it. The Reel toggle does not travel.
Cut a Threads file on purpose
Start from the script or the scene list, not from the Reel export. If the source was generated, re-render 9:16 with a first line written for a text feed. If the source was a shoot, recut the open so the claim is visible as a still-plus-type poster in a timeline of paragraphs.
Leave Reels its own master: full-screen, hook in pixels, ask in a card, caption clear of the button column. Leave Threads a sibling: text that invites a reply, video that proves it, burn-in clear of playback chrome, no hashtag wall.
The UGC video generator can give you both opens against one body. That is a hook pack, not a cross-post. Score them separately. Threads hook rate is whether they stopped in a text feed. Reels hook rate is whether they stayed in a player. One MP4 cannot win both tests unless you were lucky.
Threads video is not a Reels master. Conversation versus watch. Recut the open.
Make the Threads cut a file, not a cross-post, in Versely.
FAQ
Can I cross-post the Reel if I crop the captions up?
You can. You still have a Reels ask, a Reels caption field, and a Reels last beat. Rewrite the post text and the last second or you shipped a broadcast into a reply feed.
Does Threads' five-minute cap mean I should ship longer cuts?
Only if the extra minutes have a job. Reels discovery past three minutes is a different rule. Do not pad a 20-second joke to look "native to Threads."
Is 9:16 still right for Threads?
It fills the phone when someone taps through. In the feed it may sit beside text. Compose so the claim is readable in both states, and do not rely on Reels-only chrome.