What happens when you press publish.
The checks that run first, how the upload is chunked, and how a post is confirmed rather than assumed.
Before anything is uploaded
The app asks TikTok which privacy levels your account may currently use, and posts at one of those. Requesting a level your account is not eligible for is rejected outright, so the allowed list is read rather than assumed.
The rendered file is then checked locally against TikTok's constraints. This matters more than it sounds: a file TikTok will not accept still uploads in full first, and the rejection only arrives at the status check afterwards — so without the check you would wait out an entire upload to be told no.
| Checked | Requirement |
|---|---|
| File size | Must be under 4 GB, and not empty |
| Duration | At least 3 seconds, and within the maximum your account may post |
| Video codec | H.264 |
| Audio | An audio track must be present |
The upload itself
Publishing goes through TikTok's documented Content Posting API. There is no browser automation, no scraping and no unofficial endpoint.
TikTok requires a file of 64 MB or less to be sent as a single chunk whose declared size equals the whole file; above that, chunks fall in the 5 to 64 MB range. Getting this wrong is quiet rather than loud — the upload is accepted and simply never completes — so the app follows the rule exactly.
Confirmation
After upload, the publish status is polled until TikTok reports the post as complete or failed. A post is only recorded as published once TikTok says so, and a failure surfaces the reason TikTok gave rather than being silently dropped.