Separate three questions
- What resolution does the model generate before extra processing?
- What processing, including upscaling or interpolation, is applied?
- What are the dimensions and frame rate of the file you deliver?
A tool may show all three stages under a single export label. Keep separate fields in your project log. That prevents a comparison table from equating different operations because both produce a file named “4K.”
What the current sources actually establish
Google’s Gemini Omni guide explicitly marks 1080p and 4K output as upscaled. Runway’s Gen-4.5 help page lists 720p as the base output. Kuaishou’s Kling 4.0 release uses future wording for some higher-resolution formats. Luma describes 1080p output and HDR/EXR workflow support.
These statements do not establish a visual-quality ranking. They tell you what to investigate and how to label the workflow. We preserve the source wording about availability rather than presenting every announced option as a feature you can use today.
Inspect detail and motion separately
Use a frame with fine structure, such as hair, fabric, foliage or a patterned surface. Look at the actual playback size first, then inspect a detail crop. Check whether edges stay stable through movement and whether small structures change from frame to frame.
A sharp still frame can coexist with unstable video. Conversely, a smaller output may be perfectly suitable for a small embedded player. Judge fitness at the delivery context, not only at an enlarged screenshot. If processing adds halos or unstable texture, retain the original export for comparison.
When a larger export is worth testing
Test higher output size when your delivery genuinely needs it: a large screen, substantial crop or downstream compositing may justify the extra processing. For a small social preview, improving composition or stability may be more valuable than increasing file size.
Render one representative shot through the full workflow before processing a batch. Compare original and processed versions on the device and player the audience will use. Include any extra charges and turnaround time in the budget.
A compact export record
| Field | Example record format |
|---|---|
| Model and version | Exact model identifier shown by your provider |
| Base generation | Pixel dimensions before extra processing, if disclosed |
| Processing | Upscale, retime, denoise or other operation |
| Delivered file | Width × height, frame rate, codec and duration |
| Review | Accepted/rejected and reason at target playback size |
The example format intentionally contains no invented test measurements. Fill it with your real files, and mark undisclosed information as unknown.
Sources and verification
Reviewed October 25, 2026. Provider documentation supports specifications; it is not evidence of an independent performance test.