Worked example: creator baseline
The default scenario uses 80 images, 2 videos, and 20 seconds per video. That is 82 total assets and 40 generated video seconds.
Midjourney Pro monthly is $60 and includes 30 fast GPU hours. The scenario plans 38 fast hours, so overage is 38 - 30 = 8 hours. At $4/hr, overage is $32 and total Midjourney cost is $92.00, or $92.00 / 82 = $1.12 per asset.
Runway Pro is $28 per month in the captured annual-billed pricing page. Image credits are 80 x (2,250 / 281) = 640.57. Video credits are 2 x 20 x 12 = 480.00. Total credits are 1,120.57, below the 2,250 included credits, so Runway stays at $28.00, or $0.34 per asset.
Google Vertex AI uses Imagen 4 Fast at $0.02/image and Veo 3.1 Lite 1080p video-only at $0.05/sec. Image cost is 80 x $0.02 = $1.60. Video cost is 40 x $0.05 = $2.00. Total Google cost is $3.60, or $0.04 per asset.
For this exact cost-only setup, Google Vertex AI is the cheapest path. The result does not score output quality, style fit, moderation policy, editing UX, rights, or support burden.
How to estimate AI image and video generation costs for one month
Start from the number of final images, the number of generated videos, and the average video length. Then compare subscription plans, credits, GPU-hour overage, and pay-as-you-go rates on the same monthly basis.
How Midjourney fast GPU hours turn into overage charges
Midjourney cost is plan price plus fast GPU overage. The calculator does not invent a per-image conversion because the cited source gives included fast GPU hours and the $4/hr extra GPU rate, not a direct asset conversion.
How Runway credits are spent across images and seconds
Runway cost depends on included monthly credits and the credit burn of the selected tools. The default uses the sourced image equivalents and a 12 credits/second video rate for Gen-4.5 style video. Override it when your actual Runway tool uses a different rate.
How Google Vertex AI prices Imagen and Veo by resolution and second
Google Vertex AI is modeled as pay-as-you-go: images cost the selected Imagen rate per image, and videos cost the selected Veo rate per generated second. Resolution and audio change the Veo rate.
When OpenAI GPT-Image-2 token costs become useful in visual budgeting
OpenAI GPT-Image-2 is useful when you have measured image input and output tokens for your exact settings. The calculator keeps that path manual because exact per-image token accounting can vary by prompt, image settings, and source updates.
Why a Sora manual mode is required without current official per-video prices
The current source set does not include a verified per-video Sora price table. The Sora block is manual so teams can compare a verified plan only after checking current official app limits and pricing.
How to read cheapest path, tie cases, and overage risk
The cheapest result is a cost screen, not a quality score. If two paths are within 10%, choose by output quality, editability, commercial terms, speed, moderation policy, watermarks, and workflow fit.
What to verify before locking a production budget
Run one dry week, export the actual provider usage, and replace every editable assumption. Check plan changes, private contract terms, regional pricing, rights, review time, and failed-generation rates before committing budget.