# Windows: Failed to add image — all methods fail (local C:\\ path too) **URL:** \ **Category:** Bug Reports\ **Tags:** context, windows\ **Created:** [June 24, 2026, 11:51am UTC](https://forum.cursor.com/t/windows-failed-to-add-image-all-methods-fail-local-c-path-too/163983 "2026-06-24T11:51:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Pawel\_Z](https://avatars.discourse-cdn.com/v4/letter/p/77aa72/32.png) [@Pawel\_Z](https://forum.cursor.com/u/Pawel_Z)\ **Post date:** [June 24, 2026, 11:51am UTC](https://forum.cursor.com/t/windows-failed-to-add-image-all-methods-fail-local-c-path-too/163983/1 "2026-06-24T11:51:42Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Image attachment in Agent chat always fails with toast: “Failed to add image. The image format is not supported.” Happens with PNG/JPEG from Paint, local path C:\temp\test.jpg, all models (Auto, Sonnet, GPT), all methods (+, drag-drop, @, paste, Add to Chat). Worked right after first install, then stopped permanently. Reinstall did not fix. Error is misleading — not a format issue. ### Steps to Reproduce 1. Windows 11, Cursor 3.8.23 2. Save test.jpg in Paint to C:\temp\test.jpg 3. File → Open Folder → C:\temp 4. Open Agent chat, select Claude Sonnet 5. Click + and select test.jpg (or drag into chat) 6. Error toast appears, image not attached ### Expected Behavior Image attaches to chat and can be sent to a vision-capable model for analysis. ### Operating System Windows 10/11 ### Version Information IDE: Version: 3.8.23 VSCode Version: 1.105.1 Commit: d5c0e77a0214208f36b56d42e8e787de88d02ea4 OS: Windows\_NT x64 10.0.26200 ### For AI issues: which model did you use? Auto, Claude Sonnet 4, GPT-4o — all fail with image attachment ### Additional Information - Error: “Failed to add image. The image format is not supported.” - Local file C:\temp\test.jpg also fails (+, drag-drop, @, paste). - Worked after first install, then broke. Reinstall + cache clear (Cache/GPUCache) did not fix. - TEMP uses 8.3 path: C:\Users\aaa\AppData\Local\Temp - DevTools Console: no errors. renderer.log: no “image” entries. - Related: forum threads on imageUtils / misleading format error. ### Does this stop you from using Cursor Sometimes - I can sometimes use Cursor ---
**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:** [June 24, 2026, 12:29pm UTC](https://forum.cursor.com/t/windows-failed-to-add-image-all-methods-fail-local-c-path-too/163983/5 "2026-06-24T12:29:25Z")
Hey, thanks for the detailed report. The “The image format is not supported” error is misleading here. It’s almost certainly not about the format, but about Cursor not being able to write or read the cached copy of the image in its internal storage. This is a known pattern on Windows. To figure out which case you have, we need a bit more info: 1. Open DevTools via Help \> Toggle Developer Tools, go to the Console tab, and try attaching the image again. Clear the log level filter so you see everything, including Verbose, then check if you get: 2. Check if `%APPDATA%` or the Roaming folder is being redirected to a network drive by a corporate policy. Open `%APPDATA%` in File Explorer and see if it’s a UNC path like `\\server\...`. 3. Quick workaround to test. Launch Cursor with a local user data directory, for example: Let me know the results and we can narrow down the exact cause. ---
**Author:** ![Pawel\_Z](https://avatars.discourse-cdn.com/v4/letter/p/77aa72/32.png) [@Pawel\_Z](https://forum.cursor.com/u/Pawel_Z)\ **Post date:** [June 24, 2026, 12:42pm UTC](https://forum.cursor.com/t/windows-failed-to-add-image-all-methods-fail-local-c-path-too/163983/6 "2026-06-24T12:42:34Z")
Test 1 — DevTools Console: - Help → Toggle Developer Tools → Console tab - Filter: All levels, Preserve log enabled - Tried attaching C:\temp\test.jpg via + button Result: No [imageUtils] errors, no CSP/img-src / vscode-file:// violations. Console only shows unrelated logs, e.g.: [background\_composer] Refreshing background composers {arch: ‘x64’, platform: ‘win32’, channel: ‘stable’, client\_version: ‘3.8.23’, layout: ‘unifiedAgent’, …} [background\_composer] No repo URL, not refreshing background composers Test 2 — APPDATA: \\a\folderredirect$\aa\AppData\Roaming UNC/network path — corporate Folder Redirection (not local C:\). Test 3 — --user-data-dir workaround: Launched from PowerShell: Stop-Process -Name Cursor -Force -ErrorAction SilentlyContinue & “$env:LOCALAPPDATA\Programs\cursor\Cursor.exe” --user-data-dir C:\CursorLocalTest Result: SAME ERROR — “Failed to add image. The image format is not supported.” Also tried with explicit TEMP (8.3 path issue): $env:TEMP=“C:\Users\a\AppData\Local\Temp” $env:TMP=$env:TEMP & “$env:LOCALAPPDATA\Programs\cursor\Cursor.exe” --user-data-dir C:\CursorLocalTest Result: STILL SAME ERROR. Environment notes: - %TEMP% normally: C:\Users\a\AppData\Local\Temp (8.3 short path) - Local test file: C:\temp\test.jpg (valid JPEG from Paint) - Models tried: Auto, Claude Sonnet 4, GPT — all fail - Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1 - Cursor 3.8.23, Windows 10.0.26200 Conclusion: Not fixed by local user-data-dir or corrected TEMP. Console empty for image pipeline errors. Issue appears deeper than AppData storage path alone. ---
**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:** [June 26, 2026, 11:39am UTC](https://forum.cursor.com/t/windows-failed-to-add-image-all-methods-fail-local-c-path-too/163983/7 "2026-06-26T11:39:01Z")
Thanks for the detailed tests, they help a lot. There’s an interesting detail here: a clean console log with no `[imageUtils]` and no CSP violation, plus the fact that `--user-data-dir` didn’t help, is different from the usual UNC/CSP case. In the typical UNC/CSP case, the console clearly shows a block on `vscode-file://...`, and using a local user data dir fixes it. The most likely explanation is that the `--user-data-dir` flag didn’t actually apply because Cursor may have reused an already running instance. Let’s verify: 1. Fully close Cursor and make sure no processes are running: 2. Launch with a local profile: 3. In that fresh instance, open DevTools using Help \> Toggle Developer Tools \> Console, try attaching an image again, and check whether `[imageUtils]` or any CSP violation for `vscode-file://` appears. Also, if you can, please share logs from the test run: Help \> Open Logs Folder, then the files `main.log` and `renderer*.log`. Let me know what you find, and we’ll be able to tell if this is the UNC/CSP case or something else. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [July 26, 2026, 11:39am UTC](https://forum.cursor.com/t/windows-failed-to-add-image-all-methods-fail-local-c-path-too/163983/8 "2026-07-26T11:39:38Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.