Is there a scheduled fix for this bug? I have also encountered this issue.
Still blocked on this in July 2026 — Pro subscriber, Agent mode, any requested aspect ratio or size (9:16, 1:1, 512×512, etc.) still returns the fixed default (1536×1024). The underlying Gemini API supports aspectRatio and imageSize; Cursor just isn’t passing them through.
For game/UI art this means paying for a second API or manually cropping every asset. That’s a lot of friction for what should be a one-line backend fix.
I’m currently spending Cursor credits to explore whether this gap means moving off Cursor entirely for image-heavy game/UI work — Gemini direct, separate tooling, hybrid stacks. That feels like poor ROI on a Pro subscription when the provider already supports custom sizes and the fix should be trivial.
Please prioritize passing size/ratio params to the image provider, or document clearly that custom dimensions aren’t supported so Pro users don’t waste time working around it.
Windows 10 · Cursor Pro
Hey all!
You should now be able to ask for a fixed adds fixed aspect ratios (1:1, 4:3, 3:4, 16:9, 9:16) when generating images. Give it a try!
Yes, but can it support generating images in any aspect ratio?
No, it’s fixed to the ones mentioned.
Thanks @Colin — confirming this works on my side as of Aug 3 2026.
Just tested in Agent mode: requesting aspect ratio 1:1 returned a real 1024×1024 image (not the old fixed 1536×1024 default). Huge improvement for game/UI art workflows where square portraits and other fixed ratios matter.
Still noting for others: this covers the supported preset ratios (1:1, 4:3, 3:4, 16:9, 9:16), not arbitrary pixel sizes like 512×512 or 750×1500 — which matches what you clarified. For my use case the presets are enough.
Appreciate the team shipping this. Windows 10 · Cursor Pro
Hey @darkKnight, @Jack_ryan!
Thanks for pressing on this. I looked into it more and you’re describing the current behavior accurately.
Some context on why it works this way: image requests can be served by different providers depending on a team’s model settings, and the provider mix can change over time (that’s why we offer fixed ratio presets rather than exact pixel dimensions, and why exact output sizes aren’t guaranteed).
That said, the presets should track the requested ratio more closely than they do today and I’ve taken that feedback to the team!
Staff confirmed here that GenerateImage does not pass size/aspect to Gemini (default 1K). We are seeing a related overnight quality collapse at the SAME 1024x1024:
- 2026-09-09 00:50 CST: ~1.6MB PNG / ~180k unique RGB (photoreal skin)
- same morning: ~300KB / ~50-60k unique RGB (plastic/CGI)
Same account. Grok 4.6 parent and Composer 2.5 subagent both hit the cheap lane. Extra image_size=2K / quality / model args are ignored (matches this thread).
Full measurements and Request IDs:
Please also check whether the backend is silently routing to Flash (gemini-2.5-flash-image / 3.1-flash-image) instead of Nano Banana Pro. If Pro is rate-limited, fail with 429 instead of returning Flash-class images with no notice.
how can you guys just arbitrarily change resolutions like this, what if a project is using certain resolutions and then you can’t use those resolutions because it’s changed? Now we have to go back and change everything else we did before?
Edit: This actually created a lot of problems, where I had locked picture size to specifics amounts and it started producing errors lots of errors, and or just kept spending tokens and wasting tokens!

