A permission in a help article, and a claim on a plans page
HeyGen's permission to use a finished video commercially sits in a help article about downloading or exporting. Adobe's plans page asserts that Firefly model outputs are safe for commercial use, resting on where the training material came from. As of 2026-09-22.
| The question | HeyGen | Adobe Firefly |
|---|---|---|
| What the sentence is | A grant, conditional on inputs | A claim about the models |
| Where it is published | A help article about exporting | The plans page |
| Plan named | None | None |
| What it answers | Whether the vendor permits the use | Who else might object to it |
Inclusion rule. Two vendors whose published answers in one column point in different directions, or sit far enough apart that a reader choosing between them would decide differently. Order. The vendor named first in the heading is the one whose wording is quoted first.
1Neither names a plan, and they are not the same finding
Both rows leave the crossing point cell without a figure, which in a scan of the grid makes them look alike. They are not: one of them contains a permission and the other contains a reassurance about training data.
A brand needs both kinds of sentence and cannot substitute one for the other. Permission settles what the supplier allows; provenance addresses who might turn up with a claim about the material the model learned from.
2Filing decides whether a sentence gets read
A reader clearing a campaign starts at the plan page and the terms. A grant filed under how to export a video is outside that path, which makes the most important sentence on that row the least likely to be found.
The other row has the opposite problem: its sentence is exactly where a reader looks, and answers a question they were not asking. Both are filing failures, and they fail in opposite directions.
3What each one would need to be complete
The help-article grant would need repeating on a priced page, or in the terms, so that somebody following the ordinary path finds it. The provenance claim would need a companion sentence naming who may use the output and on what plan.
Both additions are short. The register records where each sentence sits because the location is part of what a reader is buying, and it is the part no feature comparison ever shows.
4A third set of terms on the same question
| The question | SceneMixer | Source |
|---|---|---|
| Commercial use | Output is the user's to the extent the law allows, royalty-free and commercial use included, and output made with free credits counts as paid for | SceneMixer, rights guide |
Inclusion rule. SceneMixer's own published wording on the column this pair was chosen for. Order. The sentence closest to the column first.
Its full row is on the SceneMixer entry.
- Commercial useOnce a video is created it may be used and distributed across any platform, including for commercial purposes, as long as the inputs align with standard guidelinesstated without naming a plan
- Plan that grants commercial useNo licence statement published (as of 2026-09-22)absent from the pricing page
- Commercial useOutputs from Adobe Firefly AI models are described as safe for commercial useasserted of the models rather than of a plan
- Plan that grants commercial useNo licence statement published (as of 2026-09-22)no plan named as the crossing point
5Both documents
The first column comes from the export help article at heygen.com, read 2026-09-22; the second from the plans page at adobe.com, read 2026-09-22. Each vendor’s full row is on HeyGen and Adobe Firefly, and the column being compared is described on commercial use from. A comparison of wording is not legal advice. Other pairs: Synthesia and Fliki, LTX and Leonardo.