Guide
TikTok export settings that actually matter
Nearly every settings guide quietly assumes TikTok will re-encode your video. That assumption does most of the work in their advice. Take it away and several of the usual rules invert — including the one about resolution, which becomes a trap rather than a limit.
The short version
| Resolution | 1080 × 1920, 9:16 — the sweet spot for playback |
| Frame rate | 60 fps if you filmed at 60 — match your source |
| Codec | H.264 (High profile), in an MP4 |
| Bitrate | 8–12 Mbps at 30 fps, 12–16 at 60 |
| Audio | AAC, 44.1 or 48 kHz — genuinely does not matter |
| Export passes | One. Never re-export an exported file |
If you only want the numbers, that is them. The rest of this explains which of those actually change anything, and why one of them is the opposite of what you will read elsewhere.
Why the usual advice exists
TikTok re-encodes what you upload. Your export is an input to their encoder, not the thing anyone watches. That is why the standard advice is mostly about not wasting effort: do not export 4K, because it gets downscaled; do not obsess over bitrate, because it gets replaced.
That advice is correct, as far as it goes. We wrote about it in why your TikTok videos look blurry.
What changes when nothing re-encodes
There is a way to stop that re-encode happening — it is what this tool does. And the moment it stops, something subtle happens: you inherit every decision the platform used to make for you.
Your resolution is now the delivered resolution. Your bitrate is now the delivered bitrate. Your file is what viewers' phones download and decode. Nothing stands between your export and your audience any more, which is the point — but it also means your mistakes are no longer quietly cleaned up on the way through.
Resolution: 1080p is the sweet spot
This is the important one, and it is where we disagree with the obvious conclusion.
Once the re-encode stops, a 2K or 4K export survives intact. TikTok's 1080p ceiling was always a property of their encoder, not their storage, so bypassing the encoder bypasses the ceiling. It is tempting to treat that as a free upgrade.
That is where it gets interesting. In our own testing, 2K and 4K uploads played back unevenly on ordinary phones — stuttering and hitching in the feed in a way the 1080p version did not. Higher resolution means a great deal more decoding work per frame, and the feed is the worst possible place for that: the app is decoding your video while also preloading the next ones, on a device that may be five years old and thermally throttled in someone's hand.
And you gain nothing visible for it. A phone screen is around 1080p. Most of the feed is watched on a display that physically cannot show the extra detail you paid for in decode budget.
So the trade is no visible improvement in exchange for a real chance that your video stutters, and stuttering video gets scrolled past. 1080 × 1920 is the recommendation — not because higher does not work, but because it is what plays reliably for the people watching.
Bitrate: now it genuinely matters
Here is a reversal worth being explicit about. We have said elsewhere that specific bitrate recommendations are folklore — guides confidently say 5–10 Mbps, or 8–12, or "at least 2", and they contradict each other because none of them know TikTok's encoding ladder.
That criticism was right because of the re-encode. If your bitrate is going to be thrown away and replaced, arguing about it is pointless. Remove the re-encode and it becomes the opposite: your bitrate is now knowable, because it is simply what gets delivered.
Which makes the trade-off real in both directions:
- Too low and you get blocking and mush in fast motion — and now nothing downstream will ever paper over it.
- Too high and the file gets large, which slows loading on mobile data and adds decode work for no visible gain. It can also push you past the upload size limit of the TikTok app, which forces a compression pass on your own device — the exact thing you were trying to avoid.
8–12 Mbps at 1080p30 is a sensible starting point, 12–16 at 60 fps. Treat those as a place to start rather than a rule: a static talking-head clip is fine far lower, and fast camera movement or dense detail wants more. Export twice at different bitrates and look at the hard parts — a whip pan, confetti, water — on a phone.
Frame rate: 60 if you shot 60
60 fps looks noticeably smoother than 30, and TikTok is a motion-heavy feed — camera movement, transitions, animated text, things thrown at the lens. If you filmed at 60, export at 60.
It is worth being precise about the cost, because it is easy to lump this in with resolution and conclude the wrong thing. Going from 1080p to 4K quadruples the pixels in every frame. Going from 30 to 60 fps doubles how often you decode a frame of the same size. The second is a far lighter ask, and 1080p60 has been a standard hardware-decoded profile on phones for over a decade. The stuttering we saw in testing was at 2K and 4K; we have not seen it at 1080p60, and it would be sloppy to assume the two behave alike.
The rule that does hold is to match your source. Exporting 30 fps footage at 60 smooths nothing — it duplicates every frame and enlarges the file for no gain. Shoot at 60 if your camera offers it; if you shot at 30, export at 30.
Give 60 fps a little more bitrate. Twice the frames need more bits to look equally clean, which is why the table above suggests 12–16 Mbps rather than 8–12.
Codec: H.264, not HEVC
H.264 in High profile is the safe choice. It decodes in hardware on essentially every phone in use, which is exactly what you want when the file is being played rather than re-encoded.
HEVC is more efficient on paper — better quality per megabit. But hardware decode support is less universal, and a device that falls back to software decoding will struggle far more than it would with a larger H.264 file. When your file is delivered as-is, compatibility beats efficiency.
Audio: stop worrying about it
We tested this directly, uploading the same clip with audio untouched at 44.1 kHz and re-encoded to 48 kHz. There was no difference in how the video was treated. Export AAC at whatever your editor defaults to and spend your attention elsewhere.
Export once
This one predates everything else and still matters most. Every export is a lossy generation. Exporting, re-importing, editing and exporting again visibly degrades the result before it goes anywhere near TikTok, and no amount of settings tuning recovers it.
Keep your project file. Re-export from the project, never from a previous export.
If you edit in CapCut, we opened one of its exports up and read what is inside: CapCut and TikTok quality.
Test it the way it will be watched
Watch your own upload in the feed, on the cheapest phone you have access to, on mobile data rather than wifi. A flagship on fast wifi will play almost anything smoothly and will tell you nothing about what most of your audience sees.
If it hitches on that device, your file is too heavy, whatever the numbers say.
The advice above about bypassing the re-encode depends on a quirk in TikTok's ingest that could be closed at any time. If that happens, everything reverts to the usual situation — your export becomes an input again, and the resolution ceiling comes back. Nothing here will hurt you in that case; you will simply be back to the ordinary rules.