Discussions

We’re using the Heygen API to generate short videos (usually 20–30 seconds), which are then displayed within our custom app. We noticed that the direct video URLs sometimes stream in-browser as expected, but other times they trigger an automatic download instead.

Examples:

• ✅ Streams in browser:
https://files2.heygen.ai/aws_pacific/avatar_tmp/5ce859a4ffc54d52be42e954154a0b80/d3ed669c3273486bbd96b4837e436c1a.mp4

• ❌ Triggers download:
https://files2.heygen.ai/aws_pacific/avatar_tmp/5ce859a4ffc54d52be42e954154a0b80/934f0d8e5f3e451f884e8065d44ed65d.mp4
https://files2.heygen.ai/aws_pacific/avatar_tmp/5ce859a4ffc54d52be42e954154a0b80/6870ba524f954ce591d8ce6abc9d717b.mp4

Browsers and OS tested:
Google Chrome and Arc on macOS.

Embedding method:
We use the Video module in Softr, a no-code builder. Not sure if it uses a native HTML5 player or wraps it differently.

Request example from our API integration:
POST /v2/template/16247ce0152f455b96d750ea91938869/generate
With the application/json content type.

Question:
Could this behavior be linked to specific response headers (like Content-Disposition, Content-Type, or cache settings)? Is there any way to enforce a consistent streaming behavior for all direct links?

We want to avoid redirection or sharing via Heygen’s website UI for UX reasons—everything stays within our app.

Thanks in advance for your insights!