A file encoded at 3840 by 2160 pixels may contain substantially less genuine image information than a camera-originated 4K shot.
Output dimensions are not source detail
HeyGen explicitly clarifies this for its Avatar IV and Avatar V API output: choosing the 4K resolution setting can return a 3840×2160 file, yet the avatar itself is rendered at 1080p and scaled up. The background can remain sharper. This distinction is crucial for teams promising broadcast-ready close-ups or planning an expensive finishing pipeline.
Separate API pricing and interface rendering
The pricing help page says that Avatar IV and V through the API do not receive a separate native 4K price; billed usage corresponds to the 1080p rate, and the account is charged for actual generated seconds. It also describes an alternative route for obtaining a truly 4K avatar through the API using Avatar III with an appropriately captured digital twin or studio avatar. These statements are specific to the stated API service and should not be copied to HeyGen Studio, where export availability depends on the plan.
An editor’s acceptance checklist
Import a sample file into the timeline and inspect eyes, hair edges, teeth and mouth movement at 100% scale. Compare those details with a native high-resolution camera reference if the job contract requires it. Check whether overlay text, supplied background photographs and graphics remain sharp independently of the avatar. The delivered file’s container and pixel resolution should be recorded separately from the render-engine resolution of its visual subject. Do not tell a client that the avatar was generated natively in 4K when the provider documentation says otherwise.
A realistic job specification
A corporate training brief might require 4K file dimensions for the learning platform while accepting a 1080p avatar inside a 4K composite. That can be a legitimate requirement, but it should be written as such. If a tight facial crop, zoom-in or theater projection requires genuine detail, use the vendor’s documented higher-detail option or record a presenter on camera. The correct technical acceptance criteria depend on the intended screen size, viewer distance and post-production motion.
Data and consent still apply
Upscaling, rendering and model versions do not confer rights in the voice or face being represented. Confirm production authorization, describe synthetic delivery to the affected participant and keep an approval workflow. Product page rates can change and are not a substitute for a signed enterprise order. Use AI 10’s dated cost data to translate per-minute API line items into a contract budget.
Relevant alternatives and trade-offs
A controlled camera capture, an Avatar III 4K-capable capture as documented by HeyGen, or a lower-resolution delivery where permitted may be more appropriate than advertising an upscaled file as native 4K.