AILIMIT.WATCH
LIVE

HeyGen

Last verified: Jun 8, 2026

5 sourced changes·100% official·verified against official docs, changelogs & Wayback·last checked Jun 8, 2026

01 / VERDICT

Watch

Some recent constraint changes — monitor before depending on it.

WHY WATCH — trend: tightening · drift -8% over 90d · 1 tightening in 90d

Constraint Stability

77/100

higher = fewer recent restrictions

tightening-8% / 90d

HeyGen has become more restrictive over time, mainly in pricing.

Most noticeable: Power users on unlimited forced to credit-based plans (effectively per-minute billing); migration irreversible

Recency
69
days since it last tightened
Velocity
5.4
tightenings per year
Silent
0%
of tightenings were unannounced
Reversals
0%
of tightenings later reversed (same dimension)

HeyGen constraint metrics — computed from 3 tracked tightenings · median 67 days between tightenings. Original to this site; not published by the vendor.

IMPACT BY PERSONA
Solo / occasional
Brief, occasional use is rarely touched by limit changes.
low
Power user / daily heavy
Exposed to sustained-session, rate / frequency tightening.
medium
Team / shared workflow
Exposed to usage-based cost changes across the team.
high
Startup / cost-scaling
Exposed to usage-based cost as usage scales.
high
Enterprise / long-term dependency
Continuity exposure: ownership / policy shifts.
medium

02 / ANALYSIS

HeyGen has been methodically dismantling the more generous grandfathered arrangements early adopters relied on. Its three most severe tracked events all push the same way: in January 2026 the Team plan closed to new purchase, replaced by Business at $149/mo plus $20/seat, which lifted a new team's floor from roughly $78 to $189/month; in February 2026 free API credits were removed, leaving pay-as-you-go only with a $5 minimum, so developers can no longer test or onboard without paying upfront; and in May 2026 the legacy 'Unlimited' plans were decommissioned, forcing power users onto credit-based billing that behaves like per-minute pricing. These migrations are fragile and irreversible — grandfathered access is lost on any payment lapse, and switching or cancelling is permanent with no return path. There is one clear loosening: audio dubbing became unlimited for paid users in May 2026, with cost shown before generation, joined by June feature additions (live avatar APIs, cloud rendering). But the credit economics stay punishing in practice — a user report notes 200 Creator credits vanishing in a single Avatar IV session because every render iteration is metered, not just the final export, and credits lapse after 12 months. Price the workload at full per-minute rates today, not on any legacy or unlimited plan, because those protections are precisely what keeps getting retired, permanently.

03 / CURRENT LIMITS

04 / WHERE IT MATTERS

Which usage patterns the recent changes affect — each line backed by the events driving it.

Agentic / high-volume costhigh exposure
May 2026↓Power users on unlimited forced to credit-based plans (effectively per-minute billing); migration irreversible·source
Feb 2026↓Developers can't test/onboard without upfront payment; risk shifted to the developer·source
Jan 2026↓New teams' base cost jumps from ~$78 to $189/mo minimum; grandfathering is fragile·source
High-frequency usagemedium exposure
May 2026↓Power users on unlimited forced to credit-based plans (effectively per-minute billing); migration irreversible·source
May 2026↑Removes a monthly credit drain for dubbing users; more predictable spend·source
Feb 2026↓Developers can't test/onboard without upfront payment; risk shifted to the developer·source
Sustained sessionsmedium exposure
May 2026↓Power users on unlimited forced to credit-based plans (effectively per-minute billing); migration irreversible·source

05 / WHAT CHANGED

Technical 1 · Product 3 · Business 1 · Policy 0

  1. May 2026

    ↓ Power users on unlimited forced to credit-based plans (effectively per-minute billing); migration irreversible

    productImpact High · source

    ↔ shipped alongside Removes a monthly credit drain for dubbing users; more predictable spend (May 2026) — more for more, not a pure cut.

  2. Feb 2026

    ↓ Developers can't test/onboard without upfront payment; risk shifted to the developer

    technicalImpact High · source
  3. Jan 2026

    ↓ New teams' base cost jumps from ~$78 to $189/mo minimum; grandfathering is fragile

    businessImpact High · source
▸ View full constraint history (3 events)
  1. May 2026

    ↓ Power users on unlimited forced to credit-based plans (effectively per-minute billing); migration irreversible

    productImpact High · source

    ↔ shipped alongside Removes a monthly credit drain for dubbing users; more predictable spend (May 2026) — more for more, not a pure cut.

  2. Feb 2026

    ↓ Developers can't test/onboard without upfront payment; risk shifted to the developer

    technicalImpact High · source
  3. Jan 2026

    ↓ New teams' base cost jumps from ~$78 to $189/mo minimum; grandfathering is fragile

    businessImpact High · source
▸ Other product updates (2) — feature launches, not constraint changes
  1. Jul 2026

    ↑ New features added including live avatar APIs and cloud rendering capabilities.

    productImpact Low · source · secondary source
  2. May 2026

    ↑ Removes a monthly credit drain for dubbing users; more predictable spend

    productImpact Low · source

06 / OUTLOOK

Active

Active. Last 12 months: 1 pricing, 1 limit/quota, 3 model-availability changes (3 tightenings).

Observed past cadence — not a prediction.

07 / USER SIGNALS

What users report

  • • “200 Creator credits vanished in a single Avatar IV session — every render iteration counts, not just the final video.” source

08 / ALTERNATIVES

ALTERNATIVES

By constraint history — not capability.

More stable:Bolt.new, Leonardo.ai, Ideogram
Similar risk:Perplexity, Devin, Claude, Cursor
→ Full comparison matrix

09 / RELATED