Separate the source from the platform versions
Your reusable master should preserve the material you control before destination-specific stickers, promotional overlays, or edits are added. Keep the editable project, original footage, transcript, and rights information alongside it. If a later platform needs different framing or a shorter cut, return to that source instead of repeatedly downloading and recompressing a previously published copy.
A master is a production asset, not a promise that one file fits every endpoint. TikTok's media-transfer guide recommends MP4 and H.264 among its supported formats and codecs. YouTube's encoding guide also describes MP4 and H.264, although the fetched page carries a Content Manager partner notice. Treat such documentation as scoped guidance and verify your actual channel and route rather than treating a shared codec as universal approval.
Inspect the exported file, not just the preset name
Record the actual container, codec, dimensions, duration, frame rate, audio streams, and color treatment. A preset called 'social video' can hide important choices. Play the export from beginning to end before uploading. Check spoken words, music balance, readability, and the first and last frames. If the file is wrong locally, investigate the production export before blaming a destination's processing.
Use a vertical composition when that is appropriate for the intended placements, but preserve enough source material to make other versions honestly. Do not stretch a landscape shot to fill a portrait frame. Reframe the action deliberately or use another layout. Text should remain readable and away from important native controls; inspect the real destination preview because overlay placement varies between platforms and surfaces.
| Keep with the master | Why | Review before reuse |
|---|---|---|
| Editable project and original footage | Create a new cut without rebuilding | Missing files, fonts, and linked assets |
| Clean export | A known source for destination versions | Actual media properties and playback |
| Transcript and caption source | Correct language and timing | Changes introduced by a new cut |
| Asset-rights notes | Track permitted uses | Music and footage rights for each destination |
Create derivatives for real constraints
Check the current requirements for the specific destination and publishing mode, including any account-specific duration limit. The same network can offer different native and API paths. TikTok's transfer documentation, for example, distinguishes media-transfer restrictions from the user's actual publishing duration and notes native trimming in an upload handoff. Avoid copying a native app's headline limit into every automated workflow.
Keep platform-specific music choices separate from the clean source unless you have the rights needed for every intended use. A track available in one app does not establish permission elsewhere. If an export includes captions burned into the image, retain the original caption text too. A later crop or translation may need different placement, and visible captions do not eliminate every accessibility requirement.
Verify one representative release before batching
Send a harmless representative file through each intended route and inspect the delivered result. Compare image clarity, audio, framing, and any text. If a destination needs a different derivative, name it clearly and record the reason. The goal is a small set of understood exports, not an untraceable pile of files named final-final. Use a version label that connects each derivative to its source.
When a native upload works but a tool upload fails, preserve the file and exact error for a controlled comparison. Do not re-encode repeatedly without knowing whether the rejection concerns format, account authority, or URL delivery. Ferryman can distribute supported content through its available flows; keep export preparation and native finishing explicit around that workflow. A reliable master reduces repeated production work without erasing destination differences.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.