Creator OS
creator-osmulti-accountschedulingvideo-variations

Schedule Video Variations Across Accounts: Auto Pairing Guide 2026

Schedule video variations in Creator OS: auto pair versions to accounts, post all now, or spread every 10 minutes to 8 hours from a start time. See statuses per vers

Creator OS · November 18, 2026 · 8 min read

To schedule video variations, upload one finished video and Creator OS makes up to 20 distinct versions. Each version is paired with exactly one account. Then you pick a timing mode: post all now, spread them from one every 10 minutes up to one every 8 hours, or start from a time you choose.

one finished video
        |
        v
  up to 20 versions (colour grade, zoom, hook,
  overlay, GIF b-roll, trimmed length, sound bed)
        |
        v
  uniqueness check  -->  lookalike versions held back
        |
        v
  auto pairing: version 1 -> account A
                version 2 -> account B
                version 3 -> account C  (one each)
        |
        +-- all now
        +-- spread: every 10 min up to every 8 h
        +-- from a start time you pick
        |
        v
  run page shows each version's account and status
One video in, one unique file per account, scheduled on your terms.

What Does It Mean to Schedule Video Variations Across Accounts?

Scheduling video variations means each account receives its own file, not the same upload repeated. That is the whole point of the Variations step.

A finished video becomes up to 20 distinct versions, one per account. Each version keeps your content and changes the look: colour grade, zoom or fit, the on-screen hook (font, size, position), an overlay such as grain, vignette or a bar, GIF b-roll cutaways, a trimmed length, and a faint sound bed. Claude writes a different hook, caption and hashtags for every version.

A uniqueness check compares the finished versions and holds back any that look the same. So you are not sending twenty identical clips out and hoping the platforms do not notice. You are sending twenty files that differ in ways a viewer would see.

Variations lives at /app/variations, in the API at /v1/variations, and in the MCP server as the variations_ tools. Access is on any paid plan with unlimited runs (2 at a time). During a free trial you get one run.

Get started for $0

How Auto Pairing Matches Each Variation to an Account

Auto pairing assigns every version to one account automatically, so posting a batch of variations is a review step, not a matching puzzle.

When you start a run, the run page pairs every version with an account for you. Each version then shows the account it belongs to and its status next to it. Two things stay true through the whole run:

  • No account receives two versions.
  • No version goes to two accounts.

You are not locked into the pairing. Change any pairing on the run page, or skip a version entirely if you do not want it to go out. The pairing only has to be right once, because each version carries its own caption, hashtags and cover into the post.

What you control before a variations run posts
Setting Who decides What it affects
Version look (grade, zoom, overlay, b-roll, length) Generated, per version How different each file looks
Hook, caption, hashtags Claude, per version What each account says
Cover Per version What shows before playback
Version to account pairing Auto, editable by you Who posts which file
Timing mode You When each version goes out

All Now vs Spread Every 10 Minutes to 8 Hours: Which Timing Mode to Pick

Choose all now when the accounts are unrelated to each other, and spread when the same audience might follow more than one of them.

There are three ways to send a variations run out:

  1. Post all now. Every version publishes as soon as the run finishes. Good for a set of accounts with separate audiences, or when a moment is time sensitive.
  2. Spread out. Versions go out one every 10 minutes at the tightest, up to one every 8 hours at the widest. You pick the gap. This keeps a batch from landing on the same followers all at once.
  3. From a start time you pick. The run begins at the time you choose and applies the spacing from there.

A worked example. You run one video across six accounts and your audience overlaps on three of them. Set the gap to 45 minutes and start at 9am. Version one posts at 9:00, two at 9:45, three at 10:30, and so on through the batch. Followers who see two of those accounts get two different files at two different times, not a duplicate in the same scroll.

If you want the opposite, a single push across unrelated pages, all now is the right call and there is no reason to stretch it.

How to Schedule Variations From a Specific Start Time

Starting from a set time gives you the spacing of a spread run with a launch point you control.

Set the start time in the run, choose your gap, and the versions go out from that moment. This is useful when you want the batch to begin when your audience is awake, or after a launch post goes live. For picking that moment well, Creator OS also exposes best time to post through creatoros analytics:best-time, and per-post and daily analytics through analytics:posts and analytics:daily so you can look back at what did well before you set the next start.

Variations covers one video becoming many files for many accounts. For the posts around it, the Creator OS CLI scheduling guide covers how to queue and list what goes out next with creatoros posts:create and creatoros posts:list.

Reading Each Version’s Status After a Run

Every version reports its own status on the run page, next to the account it went to, so a mixed result is visible per file rather than as one pass or fail for the whole batch.

A version that did not go out is tied to that version and that account, not to the rest of the run. Why failures happen one at a time rather than all at once: each version is its own post with its own caption, hashtags and cover, going to its own account. A problem with one account or one file does not take down the rest.

If a post does fail, creatoros posts:retry <postId> resends it, and creatoros posts:list --status failed shows what needs attention.

This is worth checking after a run, since a failed version is a hole in your coverage you would otherwise miss. If you want to know which versions actually performed, read the per-account numbers in tracking faceless video performance across platforms.

Variations vs Format: One Video, Many Accounts or Many Networks

Use Variations when one video goes to many accounts of the same kind. Use Format when one video goes to many kinds of network.

Format (API /v1/format, MCP format_ tools) reformats one finished video for every network it will be posted on, using each platform’s rules for size, length, file size, frame rate and bitrate, with a caption written to each platform’s limits. Each output comes with a ready POST /v1/posts body for that platform.

So the split is simple. Variations answers “how do six Instagram accounts each get their own file?” Format answers “how does the same video fit Reels, Shorts, X and LinkedIn?” You can run both on the same source video.

Can You Schedule Video Variations With Claude and MCP?

Yes. The MCP tool variations_post posts versions to accounts, and the Claude Code plugin’s publish guard asks before it runs.

The Variations step is reachable from an AI app through the hosted MCP server at https://mcp.creatoros.ca/mcp. A Claude connection is added under Settings > Connectors > Add custom connector, then you paste the URL, sign in, pick the workspace and choose read only or read & write. Claude Code can add it with:

claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp --header "Authorization: Bearer cos_live_..."

A worked prompt. You have a video ready and want it out to four accounts, spaced an hour apart:

Turn this video into four variations, one per account.
Use spread timing, one every 60 minutes, starting at
9am my timezone. Show me the pairings before posting.

Because it is a publish action, the Claude Code plugin’s mod puts a publish guard in front of it: Proceed or Cancel before anything is published, spent or deleted. The mod needs Claude Code 2.1.287 or later. Setup steps are in the Claude Code plugin docs and the MCP docs.

If you would rather watch it happen, the walkthroughs are on the KevBuildsApps YouTube channel, and the launch video at youtube.com/watch?v=-QBJH_PK3pY shows the tool in motion.

FAQ

How do I schedule the same video to multiple accounts without posting duplicates?

Use Variations instead of posting the same file several times. Creator OS turns one video into up to 20 distinct versions, and a uniqueness check holds back any versions that look the same. Auto pairing then gives each version exactly one account, and no account gets two versions.

What is the best time gap between video variations posted to different accounts?

There is no single right number, and Creator OS does not pretend there is one. The spread mode lets you set a gap from one every 10 minutes up to one every 8 hours. If your accounts share followers, a wider gap such as 45 to 60 minutes keeps the versions from landing in the same scroll.

Can I schedule video variations with Claude using MCP?

Yes. The MCP tool variations_post posts versions to accounts through the hosted MCP server at https://mcp.creatoros.ca/mcp. In Claude Code with the Creator OS plugin, the publish guard asks you to choose Proceed or Cancel before anything is published.

Why did one of my scheduled variations fail while others posted?

Each version is its own post, to its own account, with its own caption, hashtags and cover. A problem with one account or one file affects that version only, which is why the run page reports status per version. Find the failed post and resend it with creatoros posts:retry <postId>.

How do I find which version went to which account?

Open the run page. Every version is listed with the account it belongs to and its status right beside it. If you changed a pairing before the run started, the run page shows the pairing you set.

Get Started With Creator OS

Pick one finished video, upload it, and let the run page pair the versions. Change a pairing, set your gap, check each version’s status once it is done.

Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Variations runs unlimited on any paid plan, 2 at a time.

Get started for $0
Free trial for new subscribers. Cancel anytime.

Keep reading