When a creator selects Runway, Luma, Kling or Google video generation inside Adobe Firefly, the interface is Adobe’s but the model may not be. Adobe documented partner choices in its August 2026 Firefly help material, alongside Adobe’s own video model. The distinction affects settings, rights review, availability and how a support case is investigated.
Which layer provides what?
Firefly provides the workspace, prompt form and media workflow. The selected partner supplies a generation model with its own capabilities and restrictions. Adobe’s help page lists Gemini Omni Flash, Kling variants, Ray variants, Runway Gen-4.5 and Veo variants among the choices at the time documented. It also says a user is asked to acknowledge when using a model not developed by Adobe. Do not equate the presence of an option in a documented menu with entitlement on all subscription plans worldwide.
Settings vary by backend
Adobe says the available video settings and controls depend on the model chosen. That means changing the dropdown can change duration choices, aspect ratios, native audio options and visual conditioning, even when the surrounding Adobe layout stays the same. For a repeatable production, record the exact partner-model label, selected duration and resolution, generated-file metadata, date and host plan. A workflow explanation that merely says “made with Firefly” is insufficient for reproducing a specific render.
A practical storyboard-to-export workflow
Create a shot brief and storyboard first, then pick an engine for the actual need: character reference, camera motion or audio handling. Review the disclaimer before uploading. Generate a single test clip and inspect identity, motion, transitions and audio against the brief. Put accepted clips into the editor for trims, voice and subtitle timing. Store both the original generation and the export, because a later change in Adobe’s list of partner models may prevent exact regeneration.
Commercial and provenance caveats
Rights and permitted content should be checked for the relevant Adobe workflow and the particular partner model. Adobe’s documentation does not justify a blanket claim that every partner model has the same training provenance, commercial indemnity or output rights as Adobe’s native Firefly model. Maintain source-asset consent records and confirm any local disclosure rules for synthetic footage. The presence of a content credential or a host-platform label cannot by itself verify the truth of the scene depicted.
Cost is a two-dimensional record
Credit cost may depend on the Adobe product plan and the selected hosted partner. A partner’s direct API rate is not automatically the host’s rate. Keep pricing cells null until the dated Adobe plan documentation and matching AI 10 price-snapshot ID are recorded. If the exact backend model must be controlled programmatically, a direct vendor API may be more suitable; if editing integration matters more, the Firefly host may simplify handoffs.
Worked editorial scenario
Suppose an agency uses Adobe Firefly for a campaign that mixes a Runway-generated character shot with a Luma environment transition. Its shot register should contain Adobe as the application host and the exact Runway or Luma model as the rendering engine. Reviewers can then understand why one shot supports a different duration or reference mode. Before publishing, the legal reviewer can check the relevant model conditions rather than accepting the blanket description “Adobe AI.” The billing team likewise records credits billed by the host, not a guessed direct API rate for each underlying vendor.
Sources & Further Reading
- Adobe and official project documentation — adobe (first-party source; checked 2026-10-25)
- Adobe and official project documentation — adobepolicy (first-party source; checked 2026-10-25)
Product availability, plans and rights should be rechecked before publication. No hands-on test, independent benchmark or rights-cleared third-party media is claimed in this article.