ChatCut Desktop can render locally with presets up to 4K, but export dimensions do not prove native generated detail. Generation creates the source pixels; upscaling processes an existing clip; export encodes the timeline at a chosen canvas size. Full Seedance 2.0 documents native 4K, while ChatCut blocks it pending pricing and its configured Ark endpoint’s acceptance remains unverified.
Last verified: October 28, 2026
| Fact and scope | Current finding | Source |
|---|---|---|
| Native generation | Full Seedance 2.0 documents 4K; this does not apply to Fast, Mini or 2.5 | Official API, Ark tutorial (accessed 2026-10-27) |
| ChatCut generation route | Full 2.0 exposes 480p/720p/1080p; 4K blocked pending pricing; Ark acceptance unverified after timeouts | Pricing rationale, verification scope |
| Desktop export | Local video export offers a 4K preset; dynamic range and performance depend on hardware | Preserved export steps, Export Panel |
| Upscaling | Enhancing an existing clip differs from encoding it; no completed ChatCut upscale acceptance run was supplied | Higgsfield upscale tool, verification scope; a third-party tool |
Native generation, upscaling and export
Generation creates a model output. Upscaling processes existing frames and may infer detail. Export renders the edited timeline at the selected dimensions. Encoding a smaller take at 4K does not establish native 4K detail. A competitor’s upscale control is not evidence of an implemented or tested ChatCut feature.
A measured example, with limits
A ChatCut local previs acceptance record reviewed on 2026-10-28 measured a 2520×1080 guide, a 2206×946 Seedance 2.5 take (30.080s container), and a 2520×1080, 30.000s timeline delivery. The export dimensions did not establish generation at that size. This was not a native-4K or upscale test. The workflow passed 15/17 checks; side-view proof failed and speaker assignment/no-music audio remained independently unverified. Source and scope.
Check the pixels at each stage
- Keep the unedited generated file. Record the exact model, requested resolution and measured width and height.
- If you use a separate upscale operation, preserve its input, output and processing record. Renaming a file is not that operation.
- Inspect the final exported file’s dimensions, codec, frame rate, duration and sound. Compare source and export frames at the same time.
- Report source dimensions, processing and delivery dimensions separately. An audio stream alone does not prove correct sound.
Export locally
- Open the project in ChatCut Desktop.
- Select Export → Video.
- Choose Dynamic Range: SDR, or HDR when available on your computer.
- Choose Resolution (480p, 720p, 1080p or 4K), Frame Rate, Video Bitrate and the export Range.
- Select Export, or Export Zone when exporting a marked Zone. Respond to the save dialog to choose the destination, then follow the queue. Keep Desktop open while the local render runs.
- When complete, use Show in Finder or Open from the export row. Open the actual file to check picture and sound before sharing it.
4K means a target short side of 2160 pixels. Available dynamic-range options and performance depend on the computer and its hardware support. If HDR is unavailable, choose SDR.
These steps describe local video export. Audio, transparent graphics and editable handoffs have their own output settings and requirements; follow the selected tab and the detailed guides linked from Export Panel.
Where does an agent export save the file?
When the agent exports a file without an explicit output path, Desktop uses a ChatCut subfolder in your system’s video directory. A supplied output path changes that destination. Use the export tool’s returned outputPath to locate the actual file; manual exports use the folder you selected. Editable Jianying/CapCut drafts use the destination app’s project directory instead.
Frequently asked questions
What is the difference between native 4K, upscaling and 4K export?
How do Seedance 2.0 4K and 1080p differ?
Verification scope and related guides
Last verified 2026-10-28. Native documentation was accessed 2026-10-27. ChatCut integration findings come from an internal source/receipt audit of product beta b3cbb24d, not live production certification. Dimensions come from the local previs acceptance record reviewed on October 28; underlying receipts are not public and private media is not published here. Export instructions preserve the published Desktop guide; no new device-compatibility or upscale test was run.
See the capability matrix, generation references, credit policy, generation failures and Web vs Desktop Export.