Midjourney burns through fast GPU hours quickly
Recent tracked changes that can explain it:
What’s going on
Midjourney meters your plan in fast-GPU time, and jobs aren't priced equally — that's why a normal-looking month can drain it. A video job runs about eight times the fast-hours of a typical image job (four short clips per generation), so even occasional video quietly dominates your usage. Styling is heavy as well: on the V8 alpha, style-reference and Moodboard jobs cost roughly four times a standard job and ran about four times slower, and V8.1's native 2K HD uses around a third more GPU time than SD. A steady image count paired with evaporating fast hours is this job-cost weighting, not a cut to your quota — and the way to see it is to look at what kind of jobs you ran rather than how many, since a week with a handful of video or sref generations spends far more fast-time than the raw prompt count implies. The remedies follow the cost. Draft in Relax mode wherever it's available — it's unmetered and never touches fast hours, though it wasn't supported on the V8 alpha, so working on a stable V8.1 generation matters if you want it. The dedicated Draft mode added for V8.1 in June 2026 is the cheap way to iterate before committing fast time to a final render. Hold video and heavy style-reference jobs for when you're near final rather than exploring with them, and keep HD output for images you actually intend to keep. And if you consistently need video or high volume, the tier is the real lever: Relax is unlimited on Standard and above (Pro adds SD video), whereas Basic's roughly 3.3 fast hours disappear quickly once video enters the mix. Once you price work by job type rather than job count, the drain stops looking mysterious.
Midjourney has eased its constraints recently.
Low recent constraint volatility — few meaningful restrictions in the last 12 months.
Related problems