Design mode : "Failed to add image. The image format is not supported."

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using design mode (either cmd+L or inline), I get an error “Failed to add image. The image format is not supported.”. The issue is sometimes fixed by restarting the IDE.

Steps to Reproduce

I don’t have a reproducing pattern. The bug is often solved by closing / reopening the IDE, but happens again a few hours later.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z (4 days ago)
Layout: glass
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @r_duv,

Thanks for reporting this. The error message is misleading — “image format is not supported” is a catch-all that shows up for any failure in the image processing pipeline, not just actual format issues. Since design mode screenshots are always PNG, the real cause is likely something else (a transient file write or image loading issue), which is why restarting Cursor clears it.

To help us pinpoint the actual failure, could you do the following next time the error appears?

  1. Open the Developer Console: Help > Toggle Developer Tools, then click the Console tab

  2. Look for red error lines containing [imageUtils] — this will show the actual exception behind the generic message

  3. Right-click in the console and select Save as… to export the full log, then share it here

That will tell us exactly where in the pipeline the failure occurs and help us fix it.

In the meantime, restarting Cursor when it happens is the right workaround.

Hi @mohitjain! I recreated the issue. Here’s the log from console.

Thanks!

Thanks for the logs, @dverdev. They confirm exactly what’s happening: the screenshot is captured and saved to disk, but Cursor then fails to load it back internally. The error message (“image format is not supported”) is misleading — this has nothing to do with the image format.

The same pattern repeats several times in your log, which matches the intermittent behavior @r_duv described. I’ll file this with our engineering team so they can trace the load failure.

Restarting Cursor when it happens is still the workaround for now.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Got error: failed to add image. The image format is not supported.

Steps to Reproduce

I used design tool (ctrl+shift+d), selected an element, pressed ctrl+L to add to chat. Got error: failed to add image. The image format is not supported.

Expected Behavior

Should add selected element and image to chat.

Screenshots / Screen Recordings

Screenshot from 2026-05-01 07-27-22.png

Operating System

Linux

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
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: Linux x64 6.8.0-110-generic

Additional Information

Logyt

Does this stop you from using Cursor

Yes - Cursor is unusable

Restarting does not work for me. I get the error on a fresh restart.

This is the same underlying bug (the error message is misleading — it’s not actually about the image format). I’ve added your report to our tracking ticket with engineering.

Your case is different from the others in one important way: restarting Cursor doesn’t fix it for you. For the other reporters, a restart always cleared it. That distinction matters for diagnosis.

Could you try two things?

  1. Check the Developer Console: Open Help > Toggle Developer Tools, click the Console tab, then try the design tool again. Look for red error lines containing [imageUtils] — right-click in the console and select Save as… to export the log, then share it here.

  2. Try clearing workspace storage: Close Cursor, delete the folder at ~/.config/Cursor/User/workspaceStorage/, then reopen. Note: this will clear your chat history and workspace-specific state for all projects, so only do this if you’re comfortable with that.

If neither helps, sharing the console log from step 1 will help us figure out why it persists for you specifically.

I have additional context. I get the error when the element is close to the edge of my screen (happens 100% of the time). Error copied from developer console:

workbench.desktop.main.js:29759 [imageUtils] Error loading image Event
u.onerror @ workbench.desktop.main.js:29759
workbench.desktop.main.js:29759 [imageUtils] Error loading image Event
u.onerror @ workbench.desktop.main.js:29759
workbench.desktop.main.js:29759 [imageUtils] Error loading image Event
u.onerror @ workbench.desktop.main.js:29759
workbench.desktop.main.js:29759 [imageUtils] Error loading image Event {isTrusted: true, type: ‘error’, target: img, currentTarget: img, eventPhase: 2, …}
u.onerror @ workbench.desktop.main.js:29759