# Image Generation Only Has Fixed Resolution

**URL:** <https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764>\
**Category:** Bug Reports\
**Tags:** image-gen, composer\
**Created:** [February 24, 2026, 7:00am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764 "2026-02-24T07:00:36Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Redstone1024](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/redstone1024/32/95950_2.png) [@Redstone1024](https://forum.cursor.com/u/Redstone1024)\
**Post date:** [February 24, 2026, 7:00am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/1 "2026-02-24T07:00:36Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Starting 24 hours ago, when using the image generation tool, in most cases, I can only generate images at a fixed resolution of 1376 x 768. Previously, I could request the tool to generate images with any aspect ratio.

### Steps to Reproduce

Using the “Generate a night sky image with a 1:1 aspect ratio.” prompt.

### Expected Behavior

Returns a night sky image with a 1:1 aspect ratio.

### Operating System

Windows 10/11

### Version Information

Version: 2.5.20 (user setup)  
VSCode Version: 1.105.1  
Commit: 511523af765daeb1fa69500ab0df5b6524424610  
Date: 2026-02-19T20:41:31.942Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.4.0  
Chromium: 142.0.7444.265  
Node.js: 22.22.0  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### For AI issues: which model did you use?

Composer 1.5

### For AI issues: add Request ID with privacy disabled

e2efb363-4396-4c66-b1e2-c1b96b418395

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 24, 2026, 10:48am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/3 "2026-02-24T10:48:56Z")

</div>

Hey, thanks for the detailed report and the request ID.

I’ve passed this to the team. It looks like something changed on the backend and it’s affecting image generation permissions.

I’ll post an update here if we hear anything new.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 12, 2026, 6:38am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/7 "2026-04-12T06:38:49Z")

</div>

Opened on April 12, 2026, 6:38am UTC



---

<div class="post-metadata">

**Author:** ![sscally](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@sscally](https://forum.cursor.com/u/sscally)\
**Post date:** [April 11, 2026, 6:53pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/8 "2026-04-11T18:53:37Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Note - this is a re-report of this closed/inactive issue: [Image Generation Only Has Fixed Resolution](http://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764)

When generating any image using Composer 2, the output is always 1376x768 despite any instructions to use other resolutions/ratios.

### Steps to Reproduce

Generate any image and specify the dimensions, e.g.:

> generate me a 512x512 image of a cat

### Expected Behavior

The expected behavior would be, well, a 512x512 output image.

### Screenshots / Screen Recordings

 ![cat.png](https://us1.discourse-cdn.com/cursor1/original/3X/7/7/774a3118f703e5eba3f014404880a1ad7598da3e.jpeg)

### Operating System

Windows 10/11

### Version Information

Version: 3.0.16 (user setup)  
VSCode Version: 1.105.1  
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50  
Date: 2026-04-09T05:33:51.767Z  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### For AI issues: which model did you use?

Composer 2

### For AI issues: add Request ID with privacy disabled

92631806-3d83-44cc-904b-66e60d554332

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![sscally](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@sscally](https://forum.cursor.com/u/sscally)\
**Post date:** [April 12, 2026, 2:51pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/9 "2026-04-12T14:51:52Z")

</div>

I did a bit more digging and I’d like to follow up with some more information if that would help in the aid of debugging/fixing this issue…

1. Cursor 2.4 changelog states that “Google Nano Banana Pro” is used for image generation: `https://ai.google.dev/gemini-api/docs/image-generation#generate-4k-images`
2. According to Google docs, this is Gemini 3 Pro: `https://ai.google.dev/gemini-api/docs/models/gemini-3-pro-image-preview`
3. Per Google docs, Gemini images generate 1K resolutions by default: `https://ai.google.dev/gemini-api/docs/image-generation#generate-4k-images`
4. Using a 16:9 ratio for 1K resolution images, the output is 1376x768: `https://ai.google.dev/gemini-api/docs/image-generation#3-pro-image-preview`

To me, this suggests that the `image_size` value being passed from the Cursor backend –\> Gemini is always set to `1K`. My guess is also that the `16:9` ratio is either explicitly set, or used as a default by omission. These two combined result in output images always being set to 1376x768.

Hope this is helpful! Thank you

P.S. Apologies for using backticks to format the links! I am considered a “new user” and so can’t actually post the links, but I wanted to include references

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 12, 2026, 3:42pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/11 "2026-04-12T15:42:13Z")

</div>

@sscally, great research, thanks. Your analysis matches what we’re seeing on our side. The image generation tool really isn’t passing size or aspect ratio parameters to the provider, so the result is the Gemini default (1K, 16:9 = 1376x768).

I shared your analysis with the team, it’ll definitely help with prioritization. No ETA yet, but having a clear root cause makes this much easier to fix.

Let me know if you find anything else.

---

<div class="post-metadata">

**Author:** ![Ayaan\_Rulhania](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ayaan_rulhania/32/105099_2.png) [@Ayaan\_Rulhania](https://forum.cursor.com/u/Ayaan_Rulhania)\
**Post date:** [April 12, 2026, 5:23pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/12 "2026-04-12T17:23:38Z")

</div>

I still occur with this, when I tell it to generate 9:16, it still makes landscape. Super Frustrating!

---

<div class="post-metadata">

**Author:** ![Alexander\_Kotev](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@Alexander\_Kotev](https://forum.cursor.com/u/Alexander_Kotev)\
**Post date:** [May 16, 2026, 5:03pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/13 "2026-05-16T17:03:13Z")

</div>

I can confirm that the issue is still present.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [May 16, 2026, 8:12pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/14 "2026-05-16T20:12:41Z")

</div>

Hey @Alexander_Kotev, thanks for confirming. This is a known bug and we’re tracking it on our side. We understand the root cause, the backend isn’t passing the size and aspect ratio parameters to the provider, so you get the default Gemini output 1K at 16:9, which is 1376x768. We don’t have an ETA for a fix yet, but we’ll post an update here as soon as we have one.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 28, 2026, 2:33pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/16 "2026-05-28T14:33:54Z")

</div>

Hey @Redstone1024,  
Just checking in - are you still seeing image generation locked to 1376x768? We’ve shipped a number of updates since this was reported. If a recent update resolved it, feel free to let me know. Otherwise, any additional details would help us dig deeper.  
cc: @sscally @Ayaan_Rulhania @Alexander_Kotev

---

<div class="post-metadata">

**Author:** ![sscally](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@sscally](https://forum.cursor.com/u/sscally)\
**Post date:** [May 30, 2026, 2:15pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/17 "2026-05-30T14:15:18Z")

</div>

@mohitjain Can confirm I’ve been able to generate images with other dimensions (like 512x512 for example).

However, doing a quick test this morning a simple “generate me a 512x512 image of a cat” produced a 1536x1024 image. That’s not 1376x768 like the original bug, but still wasn’t what I was looking for! (I understand these things are non-deterministic but I figured I’d bring that up)

EDIT: I was wrong earlier. I’m only getting 1536x1024 images. The 512x512 images I was referring to earlier were due to post-processing automation I have set up for my project. So it seems like there are still some bugs.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [June 1, 2026, 9:14am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/18 "2026-06-01T09:14:35Z")

</div>

Thanks for the detailed follow-up (and the edit correcting the 512x512 observation - that’s really helpful to know).

So the resolution shifted from 1376x768 to 1536x1024, but custom dimensions still aren’t being respected. That confirms the core issue is still present on current versions. I’ve re-escalated this with the team.

---

<div class="post-metadata">

**Author:** ![light\_english](https://avatars.discourse-cdn.com/v4/letter/l/8dc957/32.png) [@light\_english](https://forum.cursor.com/u/light_english)\
**Post date:** [June 3, 2026, 4:50am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/19 "2026-06-03T04:50:18Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

When generating images in Cursor (via Agent or Composer), explicitly requesting a specific size such as 750x1500px completely ignored. Regardless of how the prompt is phrased, the generated image is always 1536 × 1024 pixels.  
This makes it impossible to generate UI assets, icons, thumbnails, or any image that requires precise dimensions.

Impact:  
This blocks all workflows that depend on exact image sizes. A quick fix or support for explicit width x heightparameters would be greatly appreciated.

### Steps to Reproduce

1. Open Cursor Agent / Composer
2. Prompt: Generate a 200x200px solid blue square
3. Download or inspect the generated image

### Expected Behavior

The image should match the requested dimensions (e.g., 750x1500 px).

Actual Behavior:​  
The image is always generated at 1536 × 1024 px, ignoring the requested size entirely.

### Screenshots / Screen Recordings

 ![ScreenShot_2026-06-03_124519_842.png](https://us1.discourse-cdn.com/cursor1/original/3X/c/6/c680a993541ad0bea0088a6c7669195c252882ea.jpeg)

### Operating System

MacOS

### Version Information

Environment:​  
Cursor Version:  
Version: 3.6.31 (Universal)  
VS Code Extension API: 1.105.1  
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60  
Date: 2026-05-31T17:46:29.630Z  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
xterm.js: 6.1.0-beta.220  
OS: Darwin arm64 25.3.0  
System: macOS  
Model: Auto

### For AI issues: which model did you use?

Auto

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![light\_english](https://avatars.discourse-cdn.com/v4/letter/l/8dc957/32.png) [@light\_english](https://forum.cursor.com/u/light_english)\
**Post date:** [June 3, 2026, 5:19am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/20 "2026-06-03T05:19:48Z")

</div>

Thanks for the clarification! I really hope custom sizes can be supported soon. The main reason I use Cursor’s built-in tool is to avoid switching to external image generators—I’d love to keep my entire workflow within Cursor. Fingers crossed for an update!

---

<div class="post-metadata">

**Author:** ![JBDev](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@JBDev](https://forum.cursor.com/u/JBDev)\
**Post date:** [June 3, 2026, 7:11am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/21 "2026-06-03T07:11:09Z")

</div>

Critical issue for me. As long as this is not fixed, I need to have the images generated using Gemini Pro directly. I canceled my Cursor Pro+ subscription because now the costs are generated on Gemini side. And I need to integrate every picture manually which is very cumbersome. Please prioritize this fix.

---

<div class="post-metadata">

**Author:** ![Jackyfan](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@Jackyfan](https://forum.cursor.com/u/Jackyfan)\
**Post date:** [June 4, 2026, 7:47am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/22 "2026-06-04T07:47:49Z")

</div>

I also encountered the same issue. The integration between Codex and GPT-Image-2 has greatly improved convenience, not only for coding. I hope Cursor can fix this bug as soon as possible.

---

<div class="post-metadata">

**Author:** ![light\_english](https://avatars.discourse-cdn.com/v4/letter/l/8dc957/32.png) [@light\_english](https://forum.cursor.com/u/light_english)\
**Post date:** [June 7, 2026, 2:14am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/23 "2026-06-07T02:14:12Z")

</div>

Now that you know what’s wrong, please prioritize fixing it.

---

<div class="post-metadata">

**Author:** ![Jackyfan](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@Jackyfan](https://forum.cursor.com/u/Jackyfan)\
**Post date:** [June 8, 2026, 7:39am UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/24 "2026-06-08T07:39:48Z")

</div>

Yes, I strongly agree, and this is just a minor issue. Using Cursor itself should have solved it in a very short time, yet this problem has existed for several months. I really can’t imagine what new things you are developing.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [June 8, 2026, 12:01pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/26 "2026-06-08T12:01:50Z")

</div>

Thanks for the continued reports - and for confirming it’s still happening on the latest version with custom sizes ignored (1536×1024 regardless of what’s requested).

This remains a known issue we’re tracking, and the extra confirmations from @light_english, @JBDev, and @Jackyfan genuinely help it get prioritized. The cause is what @deanrie described earlier in the thread: the requested size isn’t being passed through to the image provider, so you end up with a default output. I don’t have a timeline to share yet, but I’ll post here as soon as that changes.

I know that’s frustrating when exact dimensions are central to your workflow, so I won’t pretend there’s a clean workaround — there isn’t a reliable in-product way to force a specific size today. I’ll keep this thread updated.

---

<div class="post-metadata">

**Author:** ![dustymcp](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dustymcp](https://forum.cursor.com/u/dustymcp)\
**Post date:** [June 10, 2026, 3:30pm UTC](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764/27 "2026-06-10T15:30:24Z")

</div>

You can set the sizing in nano banana the model needs to be able to do the same please fix 🙂

[Next page](https://forum.cursor.com/t/image-generation-only-has-fixed-resolution/152764.md?page=2)
