Work with 4K and high-frame-rate sources
Distinguish captured detail from export settings and delivered playback.
3 min read · Updated November 3, 2026For 2160p, 50/60 fps and slow-motion sources, including clips captured above the intended delivery frame rate.
Separate capture, timeline and delivery
A camera may record more frames or pixels than you intend to deliver. The editing timeline determines how those samples are used. The final export determines what reaches preparation. Increasing a number at the last stage cannot recover detail or motion discarded earlier.
For a normal-speed 60 fps delivery, a 30 fps source does not contain 60 distinct captured moments per second. An editor can duplicate or synthesize intermediate frames, but those operations are different from preserving a 60 fps recording.
- 01Capture
- 02Timeline timing
- 03Export
- 04Preparation
- 05Playback rendition
Read the source before choosing a preset
Inspect the actual file properties rather than trusting a filename containing “4K60.” Check orientation too: a vertical 2160 × 3840 frame and a horizontal 3840 × 2160 frame contain the same pixel count but frame the subject differently.
Fractional rates such as 59.94 fps are legitimate. Variable-frame-rate sources may also have an average that differs from a simple round label. If the report cannot determine a rate, keep it unavailable instead of deriving it from the name.
| Source | Delivery decision | Watch for |
|---|---|---|
| Native high-resolution footage | Retain useful detail when the route supports it. | Accidental timeline downscaling or a tight crop. |
| 50 or 60 fps action | Use a suitable timeline if smooth motion is intended. | Dropped frames from a lower-rate project. |
| 120 fps slow-motion capture | Choose the intended playback timing in the editor. | Exporting an unsupported rate instead of the intended slow motion. |
| Lower-resolution footage | Choose a sensible output size. | Upscaling that enlarges pixels without restoring detail. |
Preparation success does not mean posting eligibility
Fulres preparation and TikTok transfer apply different checks. A file can be readable and successfully prepared while exceeding a later posting constraint. The current posting validator checks a 23–60 fps range and dimensions between 360 and 4096 pixels on each axis, matching the documented API restrictions.
A high-rate source should be conformed in the editor when its exported rate exceeds the posting limit. Fulres does not turn a 120 fps export into 60 fps during container preparation. The app also has its own 2 GB input limit, separate from platform limits.
Test motion as well as detail
Compare a short section containing movement, fine texture and an ordinary shot from your edit. A still frame can hide uneven frame pacing. An action scene can hide softened small text. Both matter when deciding whether a larger export is useful.
Use the same display size and playback speed for the comparison. Do not judge a small phone preview against an enlarged desktop window as though those were equivalent conditions.
- Play the original capture and identify the intended motion.
- Confirm the timeline rate and any slow-motion interpretation.
- Export a representative section with one controlled setting change.
- Check the export’s dimensions and rate.
- After posting, inspect the identified playback stream separately.
Interpret the published result carefully
The browser can receive a different codec or resolution from another delivery surface. A phone-shaped preview on a website does not measure the native TikTok app. Keep stream identity, inspection method and check time with each result.
If the checker returns a smaller rendition, report that observation for that source. Do not conclude that all viewers receive it, or that a larger advertised option was actually played. The comparison guide explains how to read these differences.