{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib2fw5hxaybjhoxthu3kx4om6xgbwx7vkoliask7dkhqmtkbkk6gm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3milxrztzwkf2"
  },
  "path": "/t/inconsistent-image-filenames-and-unclear-download-vs-upload-ui-in-chatgpt/1378459#post_1",
  "publishedAt": "2026-04-03T13:46:37.000Z",
  "site": "https://community.openai.com",
  "textContent": "I would like to report a design consistency issue in ChatGPT’s image generation workflow that affects professional use and reproducibility.\n\nThis is not a minor usability concern, but a structural inconsistency that impacts how users manage and reuse generated images.\n\n* * *\n\n### 1. Inconsistent File Naming\n\nThe same image can have different filenames depending on how it is downloaded.\n\nFor example:\n\n  * From thumbnail: “Spring Day Traveling Cat”\n\n  * From edit/download view: “ChatGPT Image 2026…”\n\n\n\n\nThis creates several problems:\n\n  * Difficult to identify whether files are identical\n\n  * Breaks file identity tracking\n\n  * Complicates comparison and asset management\n\n  * Increases risk of errors when reusing images\n\n\n\n\n**Request:**\n\n  * Assign a consistent base filename to the same asset across all entry points\n\n  * Use clear suffixes for variations (e.g., name.png / name_edit.png)\n\n\n\n\n* * *\n\n### 2. Unclear Separation of Upload and Download Actions\n\nCurrently, upload and download are effectively combined or visually ambiguous in the UI.\n\nThis leads to:\n\n  * Unclear user intent\n\n  * Increased risk of misclicks\n\n  * Reduced workflow stability\n\n\n\n\n**Request:**\n\n  * Provide a clearly dedicated download button\n\n  * Separate upload into a distinct interaction (e.g., drag-and-drop or a clearly labeled button)\n\n\n\n\n* * *\n\n### 3. Lack of Preview vs Original Quality Clarity\n\nThere is no clear indication whether the in-chat preview (thumbnail/lightbox) is:\n\n  * compressed\n\n  * identical to the original\n\n  * or conditionally optimized\n\n\n\n\nBecause preview images can appear identical in resolution, users cannot determine whether they are working with original-quality data.\n\nThis is especially problematic for workflows involving:\n\n  * video generation\n\n  * upscaling\n\n  * further editing\n\n\n\n\n**Request:**\n\n  * Clearly indicate that preview images may be compressed\n\n  * Add a visible note such as: “Preview image – download for full quality”\n\n  * Define and document the behavior of preview vs downloaded images\n\n\n\n\n* * *\n\n### 4. Summary\n\nWhile the core functionality works, the level of design consistency is insufficient.\n\nThis affects:\n\n  * file identity tracking\n\n  * workflow reproducibility\n\n  * user confidence in the system\n\n\n\n\nThese are not feature enhancements, but baseline requirements for a reliable tool.\n\n* * *\n\n### Final Recommendation\n\nI strongly recommend addressing this as a design-level issue:\n\n  * Define a unified identity for each generated asset\n\n  * Enforce consistent naming across all surfaces\n\n  * Clearly separate upload and download actions\n\n  * Improve transparency between preview and original-quality images\n\n\n\n\nThese changes would significantly improve reliability and usability, especially for advanced and professional workflows.",
  "title": "Inconsistent image filenames and unclear download vs upload UI in ChatGPT"
}