Download Saved to Root Folder or Renamed to UUID

This document explains why exported Markdown files may be saved directly to the Downloads root folder instead of the configured subfolder, or why the filename may become a random UUID such as 719443b4-06be-452e-9bb1-efc7d53dd887.md.

---

Symptoms

You may see one or both of these issues during export:

• The file is saved to the Downloads root folder instead of your configured subfolder
• The file name is replaced with a random UUID instead of the expected title-based name

Example:

• Expected: Downloads/ChatGPTBackup/My Chat Title.md
• Actual: Downloads/719443b4-06be-452e-9bb1-efc7d53dd887.md

In many cases, the file content is correct, but the save location and filename are wrong.

---

Root Cause

The most common cause is another Chrome extension intercepting downloads.

Some download-related extensions can hook into Chrome’s download flow and override the filename and folder path requested by this extension.

A confirmed example is:

• Image Downloader

When this happens, the other extension may:

• Ignore the configured subfolder path
• Replace the requested filename with its own generated UUID
• Force the file into the default Downloads root folder

This is not caused by the export content itself.

---

Why This Happens

The extension uses Chrome’s downloads API to save Markdown files with a specific path and name.

For example, it may request something like:

• ChatGPTBackup/My Chat Title.md

If another extension with download interception behavior is active, that extension can modify the final download result before the browser writes the file.

That means:

• The export extension sends the correct filename and subfolder path
• Another extension overrides the result
• Chrome saves the file using the overridden name and location

---

How to Confirm the Issue

Step 1: Disable Other Download Extensions

Open:

• chrome://extensions/

Temporarily disable extensions related to:

• image downloading
• download management
• file grabbing
• media saving

If you have Image Downloader installed, disable it first.

Step 2: Try Export Again

Export the same chat again.

If the file is now saved correctly:

• into the expected subfolder
• with the expected title-based filename

then the issue is confirmed: another extension was overriding the download behavior.

---

Confirmed Real-World Case

A user reported that:

• exports always went to the Downloads root folder
• filenames were changed to UUIDs
• the issue only happened on that specific browser setup

After disabling the Image Downloader extension, exports immediately returned to normal.

That means the export logic was correct, but the browser environment was modifying the result.

---

Recommended Solution

Best Fix

Disable the conflicting download extension while exporting.

Recommended steps:

1. Open chrome://extensions/
2. Disable Image Downloader or similar download-related extensions
3. Export your chats
4. Re-enable the extension later if needed

If You Need Both Extensions

If you want to keep both installed:

• disable the downloader extension only during export
• check whether the downloader extension has settings to avoid intercepting non-image downloads
• if available, add exclusions in that extension’s configuration

Not all download-related extensions support exclusions.

---

Not Usually the Cause

In confirmed cases like this, the problem is usually not caused by:

• the export Markdown content
• the chat title
• the configured subfolder name
• browser language or region
• the extension’s filename generation logic

If disabling the conflicting extension fixes the issue, then the problem is environmental, not in the export data.

---

Troubleshooting Checklist

If your files are still being saved incorrectly, check the following:

• ✅ Is Ask where to save each file before downloading disabled in Chrome download settings?
• ✅ Are all other download-related extensions temporarily disabled?
• ✅ Does the issue disappear after disabling Image Downloader?
• ✅ Are you testing on the same browser profile where the issue occurs?

If the answer to the third question is yes, then the root cause is confirmed.

---

Chrome Download Settings to Check

Open:

• chrome://settings/downloads

Recommended settings:

• Location: your normal Downloads folder
• Ask where to save each file before downloading: Off

This setting is still worth checking, but in the confirmed UUID case, the main cause was the conflicting extension.

---

FAQ

Why does the file content still look correct?

Because the export itself succeeds. The conflict happens during the final save step, where another extension changes the filename or path.

Why does it only affect some users?

Because only some users have download-related extensions installed that intercept browser downloads.

Is this caused by the user’s region, such as Hong Kong?

Usually no. Region alone is not the confirmed cause here. The confirmed cause was another extension intercepting downloads.

Can the export extension prevent other extensions from doing this?

No. Chrome extensions cannot reliably block other installed extensions from modifying the browser’s download behavior.

---

Summary

Issue	Most Likely Cause	Fix
File saved to Downloads root folder	Another extension intercepted the download	Disable download-related extensions
Filename changed to UUID	Another extension replaced the requested filename	Disable Image Downloader or similar tools
Only some users are affected	Browser environment differs between users	Compare installed extensions and settings

If your export path or filename is being overridden, the first thing to check is other download-related browser extensions, especially Image Downloader.