01 / MEDIA
Source-aware preparation
Start from a local file you control. The desktop app can prepare supported platform variants and a selected cover image while preserving the link to the source chosen for this post.
THE MULTIPOST WORKSPACE
Preparation has a place.
So does the final decision.
The intended workflow starts from creator-selected media. It makes the account, destination, and post state visible without presenting a completed upload as automatically public.
02 / COPY
Captions that stay reviewable
Begin with a master description, then review the platform version before it is sent. Assisted rewriting is a suggestion. It never replaces the creator's decision to publish.
03 / ACCOUNTS
Destination context stays visible
Connected accounts authorize through their platform pages. The review surface is designed to show which destination and account will receive the selected content.
04 / ACTIVITY
States with a next action
The activity queue distinguishes review needed, scheduled locally, media preparation, platform processing, confirmed posting, and attention-needed outcomes.
TRAFFIC ROUTING
Choose one post as the destination.
In the current desktop source, YouTube can be selected as a primary traffic destination. It is published first. When YouTube returns its video URL, compatible secondary posts receive that URL before their upload starts.
If the primary YouTube post fails or does not return a usable URL, MultiPost stops the dependent posts instead of publishing a misleading call to action. A failed secondary can keep the resolved URL for a retry without re-uploading the primary video.
Platform-specific behavior stays visible
- Pinterest receives the YouTube URL as the Pin click destination.
- Other compatible captions receive the returned URL within their platform limit.
- Instagram may display an external URL as plain text rather than a tappable link.
- TikTok receives an editable, reviewed YouTube discovery line before consent. Its caption is not modified after consent.
BATCH HELP, INDIVIDUAL CONTROL
Do the repetitive work together. Approve each destination yourself.
Batch preparation reduces repeated copy work, but the final values still belong to the destination row. The creator can edit, omit, or stop any row before publish.
Review row checklist
- Selected account and intended destination
- Caption, hashtags, title, or board where supported
- Cover choice where the platform accepts one
- Format or length warning before transfer
- Audience, disclosures, and consent for TikTok
ACTIVITY THAT EXPLAINS ITSELF
One label is not enough.
A queue becomes useful when a creator can see whether a job needs review, is waiting for a chosen time, is still processing on a platform, or is actually complete.
Something changed or needs consent.
Return to the selected row to confirm the details. Nothing is silently sent because a caption, file, account, or platform requirement changed.
The platform still owns the next step.
The upload was accepted, but the platform has not yet confirmed a final outcome. A new upload should not be the first response.
The problem stays attached to its destination.
Errors are shown against the relevant account and platform, so one failure does not make the rest of the publishing result unreadable.
SCOPE, NOT A PROMISE
Platform availability is verified per release.
Connected platform support depends on the released desktop build, each platform's terms, app permissions, account eligibility, and service availability. The product does not promise reach, visibility, or uninterrupted third-party APIs.