Five steps. Your video is patched on our side and streamed straight back — nothing is re-encoded, so what you export is what you post.
Connect Discord before you do anything else. It unlocks the optimizer and ties every patched file to your account, so a run you did last month is still there if you need it again.
Your account
Sign in once — the session persists.
This is the one that catches people. A variable frame rate — what CapCut and Alight Motion output by default — is the most common reason a file can't be patched.
Set it to constant in your editor before you export, not after.
Your export settings
Check these three in whatever editor you use.
MP4 or MOV, H.264 or HEVC with an AAC audio track, up to your tier's file-size limit — 90 MB on the free tier, 150 MB on Booster and 300 MB on Donor. MOV files are remuxed to MP4 for you, so you can hand over either one.
The patcher rewrites your MP4's internal moov atom — sample tables, edit lists and timing metadata — so the file is already in the shape TikTok expects before it ever reaches them.
Your pixels and audio samples are copied across untouched. That's why there's no quality loss: there's nothing being encoded a second time.
Optimizing… 100%
> Streams ready for optimisation…
> Patching metadata on the server — streams copied, never re-encoded…
> Ready to save — download your optimised video
A patched file only pays off if it goes up without being re-compressed. Post through the TikTok app and it re-compresses on the way up — which is exactly what you just spent four steps avoiding. There are two routes that avoid that: TikTok Studio's web uploader, or the Zilem Upload page.
Do this on every upload. It's the step people skip.
Different ingestion path — which is why this is also the fix when the web uploader refuses a file. See below.
If TikTok says it “couldn't process this video”
This comes from TikTok's own uploader, not from Zilem. Your file is intact — TikTok's web pipeline just declined it. Work down this list.
TikTok's web uploader and TikTok's publishing API are two different ingestion pipelines with different limits. A file the web uploader refuses is frequently accepted through the API, so open the Upload page and post the same patched file from there. Nothing needs re-exporting.
On the Upload page, switch on Send as a draft to your TikTok inbox before you send. TikTok hands the video to your inbox and lets you finish posting inside the app — a separate route from direct publishing, and one that also works for videos you want to keep non-public.
Export the clip again as an MP4 using H.264 at a constant frame rate, then run it back through the optimizer. H.265 / HEVC is a common reason an uploader declines a file, and H.264 is the format every route accepts. You lose nothing here — the optimizer re-patches the new export.
Still stuck? Bring the file and the exact wording of the message to the Discord and we will look at it with you.
What a job costs
Jobs are paid for with credits, bought in the Shop at 10 credits per $1. What a job costs depends on the video itself, so heavier jobs cost more. Credits never expire.
Nearly always a variable frame rate. Re-export with the frame rate set to constant and run it through again — that fixes it in the vast majority of cases. If it still fails, open a ticket in the Discord server and we'll look at the file with you.
Another route that works: publish through Zernio, which posts to TikTok over their Content Posting API — the file goes straight to TikTok's ingestion endpoint instead of up through the app.
It rewrites the container around your video — the MP4/MOV structure — so TikTok's compressor doesn't strip quality on the way in. The video and audio streams inside are copied, never re-encoded, so the pixels you exported are the pixels that get posted.
MP4 and MOV. The in-browser engines — Zeta 3 and Zeta 3.5, which patch on your own device and upload nothing — take H.264 or H.265/HEVC video with an AAC audio track, and decline AV1, VP9, silent video and PCM audio. The server-side engine, Zeta 2, accepts the wider range including AV1 and VP9, but it is currently listed as offline on the optimizer page. H.264 with AAC is the export both engines accept. MOV files are remuxed to MP4 automatically, so there's nothing extra for you to convert.
With Discord, Google or Telegram, in one click. Signing in ties every patched file to your account, so a run from last month is still there if you need it again. Run /myid in the Discord bot whenever you need your Zilem ID, handle and plan in one line.
Seconds. Nothing is re-encoded, so the file is only restructured — a long clip doesn't take proportionally longer to patch.