Adobe Firefly is both a creative interface and a gateway to multiple video models. The first task in documenting a Firefly job is therefore to identify the selected model, not simply write ‘generated in Adobe’. Its native video generation, partner-model generation and generative extension have different controls and credit rates, and the results should be tracked separately.
Using the native video workflow
Adobe’s help explains text-to-video, image-to-video and reference-based composition guidance. The chosen model changes which aspect ratios, durations and reference controls appear. An operator should set the destination format before prompting, then use camera direction, lighting and a simple motion objective to avoid asking one short clip to do the work of several editorial shots. A reference video can guide composition, but permission to upload that reference is not implied by the software accepting a file.
Adobe’s 30 September 2026 generative-credit FAQ lists its native Generate Video costs as 20 credits per second at 540p/24fps, 50 credits per second at 720p/24fps and 100 credits per second at 1080p/24fps. For illustration, an eight-second 720p attempt uses 400 Adobe generative credits under that schedule. This is not 400 Runway credits, and the rate must not be used for partner models. Failed or queued jobs, plan inclusions and edge cases deserve separate billing treatment.
Plan and queue economics
The same FAQ says monthly allocations and premium entitlements vary by Firefly or Creative Cloud plan. Credits on paid plans normally reset monthly; they do not roll over. It also documents special delayed queues for eligible Firefly Premium users after available credits have been exhausted, with a queue of up to twenty video generations. That queue is not a service-level completion-time guarantee. If delivery is urgent, budget the work under a paid, immediately executable route rather than assuming delayed output will arrive on schedule.
Licensing and geography
Adobe’s guidance says non-beta Firefly results can be used commercially under its terms, while eligible beta work has additional cautions and enterprise indemnity differences. This describes an Adobe usage permission, not ownership of all source intellectual property or a defense against impersonation. Adobe lists unavailable or restricted regions in its Firefly FAQ; availability can also vary for image-to-video, by user type or regulatory requirement. Verify access on the specific account and territory before promising a workflow to clients.
Handoff checklist
Record selected model/version, prompt, source media permissions, credits charged, resolution, FPS, ratio, output file and location. Inspect human and animal motion closely: Adobe’s own Video FAQ calls out distortions, unwanted objects and unintended movement as known failure modes. Add subtitles, brand artwork and regulatory claims during ordinary editing when exact spelling or timing is critical. Adobe’s promotional commercial-safety language is a provider representation, not a substitute for legal review of a specific campaign.
Worked production example
For a multilingual campaign, the same product video might be exported in 16:9 and 9:16. Choose a source composition that keeps the product and a safe text area in both crops, then render a test at the intended native output resolution. Keep the licensed logo outside the generative video layer, add it in the edit and compare readability on a phone. Cost the test as output seconds multiplied by the selected Adobe model’s own rate; do not substitute credits from an integrated partner model. Verify that the client’s operating region and Firefly entitlement allow the planned video job.
Relevant alternatives and trade-offs
For credit-priced web generation outside Adobe compare the documented control modes of Runway, Luma and Gemini Omni; continue using Premiere or another editor for exact captions and graphics.