HeyGen is an AI avatar video platform from HeyGen, Inc., the US company founded by Joshua Xu and Wayne Liang. Teams use it to turn a script into a talking-avatar video, translate and dub footage with matched lip-sync, clone a voice or likeness, and run real-time interactive avatars through its LiveAvatar service. When it fails, product demos miss deadlines, localization stalls, and API pipelines break mid-render. If you landed here mid-problem, start with the live verdict and recent user reports at the top of this page.

Common reasons HeyGen stops working
- Render queue overload. Videos sit in processing at a fixed percentage or fail with a generic error when servers are saturated or your account exceeds its concurrency limit. Badly stuck jobs sometimes need support to terminate them.
- Studio front-end failures. The editor at app.heygen.com can load to a white screen, with avatars never rendering in the browser, even while the back end stays healthy for others.
- Voice cloning pipeline problems. Instant voice clone uploads can fail repeatedly, or the finished clone comes back garbled, which points at the cloning pipeline rather than the whole platform.
- Lip-sync and dubbing errors. Video Translate jobs can fail or return dubs with badly desynced lip movement, and custom audio uploads sometimes produce lip-sync that is completely off.
- Independent component outages. The studio, the API at api.heygen.com, and the interactive avatars on the separate LiveAvatar domains are distinct status components, so one can go down while the others keep working.
- IP and region blocks. HeyGen is not available in mainland China and blocks Chinese IPs, so API calls routed through affected ranges or proxies can suddenly fail and break automated pipelines.
How to fix HeyGen when it is not working
- Check the status at the top of this page first. If our check and user reports show a broad outage, the problem is on HeyGen’s side and waiting is usually the fastest fix.
- Reload the studio. A hard refresh or a fresh tab clears many white-screen and stuck-editor states at app.heygen.com.
- Try a private window or another browser. This rules out stale cache and blocking extensions. Disabling a VPN or proxy can also help.
- Give stuck renders time, then escalate. Copy the video ID before you do anything else. If a job stays pinned at the same percentage for hours, support may need to terminate it and refund the credits.
- Respect concurrency limits. Let running renders finish before submitting new ones, and avoid resubmitting duplicates of a stuck job.
- Re-upload audio for dubbing problems. If Video Translate or a custom-audio lip-sync comes back desynced, retry the job with a clean, clearly recorded source file.
- Check your network path for API failures. If api.heygen.com errors from a server or proxy, test the same call from a different network to rule out an IP block.
For a fuller checklist that applies to any AI service, see our guide on what to do when an AI tool is down.
Is HeyGen down, or is it just you?
The fastest way to tell is to compare your experience with what others see. If the verdict and reports at the top of this page show a spike, the outage is real and shared, and the fix is on HeyGen’s end. If reports are quiet but your renders still fail, the cause is more likely local: your browser, your network, a concurrency limit on your account, or a single stuck job. Trying the studio from a second device or network is the quickest single test, and running an API request from a different server shows whether an IP block is in the way.
How we check HeyGen
We determine HeyGen’s status from two signals rather than one. We read HeyGen’s official status feed, which reports the studio, the API, and the LiveAvatar service as separate components, and we also run our own independent reachability check against the service from the outside. Combining both means we catch problems even when one source is slow to update, and it keeps the verdict honest. You can read more about how this works on our methodology page.
Alternatives to HeyGen during an outage
If HeyGen is down and a deadline is not moving, a few tools cover parts of its job. Runway and Kling AI handle generative video well, while ElevenLabs covers voice cloning and dubbing. None replicates HeyGen’s full avatar workflow, so treat them as stopgaps for individual steps. Before switching, confirm your backup is healthy on its own status page, since AI services sometimes fail together during broad infrastructure events.
Why HeyGen fails in pieces, not all at once
HeyGen is really six endpoints wearing one brand. The main site, the studio at app.heygen.com, the API at api.heygen.com, and three LiveAvatar domains for interactive avatars are tracked as separate status components and fail independently. Partial outages are the norm: a streaming avatar session can refuse to connect while the studio renders fine, or the API can error while the website looks normal. Check the specific component you depend on.
The other signature pattern is the frozen render. A video pinned at the same processing percentage for hours usually means the queue or your concurrency limit, not your file, and because HeyGen deducts credits the moment generation starts, failed renders need a support ticket with the video ID before the balance comes back. Add the geography quirk, US-hosted data and Chinese IPs blocked outright, and some failures are policy rather than outage.
- A render pinned at the same processing percentage for hours
- The studio loading as a blank white screen
- Interactive avatar sessions failing to connect while the studio works
- Dubbed videos coming back with lip-sync far out of alignment