Skip to content

Part 3 · Operate

Reels everywhere

A finished Reel joined into one video file in your browser, then posted to Instagram, Facebook, YouTube Shorts and TikTok from one approval.

01What it is

Once a Reel is rendered, it plays in a phone frame in the Reel composer, and one button, Schedule to Instagram, TikTok, YouTube Shorts and Facebook, makes its finished file (the clips in order with their captions and words burned in, the same as the preview), approves the Reel and adds it to each network’s queue. One post goes to each network with the same file, and each shows Published with its link once it is up.

02Why it exists

A Reel that ends as a folder of clips still needs an hour in each network's editor, which is the work the founder was trying to stop doing. So the last step happens here: the file is joined in your own browser, where the clips already are, and goes out through each network's own API.

Making the file is free. It joins clips the Reel already paid for with words you already approved, so it never uses the render budget, a revision or a Reel from your allowance. Posting is one approval because it is one piece of work: the same video, in the same words, on every network you ticked. Every network's checks still run first, and if any of them would refuse, nothing is scheduled.

03How to use it

  1. 01Reels everywhere waits behind the reels_everywhere flag, on top of Reels. Open a Reel in the composer and render it.
  2. 02Under the phone preview, each network says what scheduling does there, read from its connection: Posts for you at the scheduled time, Lands in your TikTok inbox to finish there, You get a reminder to post it, or Not connected yet with a Connect link.
  3. 03Press Schedule to Instagram, TikTok, YouTube Shorts and Facebook. Your browser joins the clips into the finished file (the screen counts the scenes as it goes, about as long as the Reel plays), then the Reel is approved and added to every network’s queue for your next posting time. A network that is not connected still gets the post on the calendar and a reminder at its time.
  4. 04Want the file first? Make the finished file makes it without scheduling, and Download keeps a copy. Change a caption, a word or the order later and the file says it is out of date; the Schedule button makes it again, still free.
  5. 05With reel_audio on, the Sound step before Render gives the Reel music and, if you want it, your captions read aloud. The file carries the sound, and a change to the music, its level or the voice marks it out of date the same way.
  6. 06Each network then shows Scheduled, Published with a link, or what went wrong. Check again reads them afresh.

04What good looks like

You give it
A rendered four-scene Reel with captions, Instagram, Facebook, YouTube and TikTok connected; the founder presses Schedule to Instagram, TikTok, YouTube Shorts and Facebook.
You get
The file is made in the browser, the Reel is approved, and one post group with four posts is queued for the next posting time. At that time Instagram and Facebook post it as Reels, YouTube uploads it as a Short, and TikTok, not yet approved for direct posting, puts it in the founder’s TikTok inbox to finish there, as its row said before the press.
Why
FinishReel runs makeAndSave, then approveReelAction, then postReelEverywhereAction with kind queue; postReelEverywhere saves the group and schedules it through scheduleGroup, and the publisher posts each through its adapter. Each row’s words come from scheduleHow, which reads the live connection, the adapter’s configured state and TIKTOK_DIRECT_POST_APPROVED.

Derived from the rules in the code

05What weak looks like, and what it costs

You give it
The founder made the file, then edited a caption, and has only Instagram connected. They press Schedule to Instagram, TikTok, YouTube Shorts and Facebook.
You get
The file is made again first, so every network gets the words as they now stand. Instagram is queued to post itself; Facebook, YouTube Shorts and TikTok go on the calendar with a reminder at their time, which is what their rows said: Not connected yet.
Why
finalIsCurrent compares the file’s assemblyHash with the Reel’s current one, so the button remakes an out-of-date file before scheduling and postReelEverywhere never sends a file made from another version; a target with no connection is saved with no account and becomes a reminder.

Derived from the rules in the code

06Read next