Feature Request: Persistent Asset Retrieval

Summary

I am unsure if this has been requested in the past, but I’d like you to introduce a Persistent Asset Retrieval feature that allows ChatGPT to securely retrieve user-owned files stored in the Library across conversations.

Rather than requiring users to repeatedly upload the same files or relying on recreated approximations, ChatGPT should be able to reference the original asset whenever the user requests it.


Problem

Many users use ChatGPT as an ongoing workspace for long-term projects rather than isolated conversations. These projects often rely on a collection of reusable assets that remain consistent over time.

Examples include:

  • Logos and branding
  • Icons and SVGs
  • Reference images
  • Character sheets
  • Maps
  • Design assets
  • Technical diagrams
  • Templates
  • Documentation
  • Configuration files

Currently, these assets typically need to be uploaded again in new conversations. If they are unavailable, ChatGPT may have to recreate or approximate them from previous descriptions, which can introduce inconsistencies and unnecessary repetition.


Proposed Solution

Allow users to designate uploaded files as Persistent Assets within their Library.

Persistent Assets would receive a stable identifier and could be retrieved by ChatGPT in future conversations whenever the user references them.

For example:

  • “Use my company logo.”
  • “Reference the latest project diagram.”
  • “Use the approved character reference.”
  • “Insert the canonical SVG.”
  • “Use the design template from my Library.”

Rather than asking the user to upload the file again or attempting to recreate it, ChatGPT would retrieve the original asset directly from the user’s Library.


Suggested Features

  • Mark any uploaded file as a Persistent Asset.
  • Support common file types, including images, SVGs, PDFs, documents, spreadsheets, presentations, and other supported formats.
  • Assign user-friendly names or aliases to assets.
  • Retrieve assets across conversations without requiring another upload.
  • Organise assets into folders, collections, or projects.
  • Support versioning so users can replace an asset while preserving its identity.
  • Allow users to manage, rename, archive, or remove Persistent Assets from their Library.
  • Make assets available to compatible tools, such as image generation, document creation, and other workflows where appropriate.

Benefits

Improved Workflow

Users can work across multiple conversations without repeatedly uploading the same resources.

Greater Consistency

Projects maintain a single source of truth by always referencing the original asset rather than recreated versions.

Better Long-Term Project Support

Persistent assets make ChatGPT more effective for ongoing creative, professional, educational, and technical work.

Reduced Repetition

Users spend less time managing files and more time focusing on the work itself.

Better Tool Integration

Future features and tools can build upon a common library of user-approved assets instead of requiring duplicate uploads.


Potential Use Cases

Persistent Asset Retrieval would benefit users across many domains, including:

  • Software development
  • Graphic design
  • Product design
  • Marketing
  • Education
  • Research
  • Engineering
  • Architecture
  • Technical writing
  • Business documentation
  • Creative writing
  • Worldbuilding
  • Game development
  • Personal knowledge management

Why This Matters

ChatGPT has evolved beyond a conversational assistant into a platform for ongoing projects. While conversations can retain context and users can maintain a Library of uploaded files, there is currently no straightforward way for ChatGPT to retrieve specific assets across conversations without requiring another upload.

Persistent Asset Retrieval would bridge this gap by allowing users to build a reusable library of trusted resources that can be referenced whenever needed. Instead of recreating assets from memory or requesting repeated uploads, ChatGPT could retrieve the original user-provided file, improving consistency, efficiency, and the overall experience for anyone working on long-term projects.

Thanks for taking the time to lay this out so clearly, @R3ap3rG. The examples around logos, diagrams, templates, character references, and other reusable files make the need easy to understand.

A persistent asset system with stable names, versioning, folders, and cross-conversation retrieval could remove a lot of repeated uploading while helping users keep a consistent source of truth across long-term projects. The point about making those assets available to compatible tools is especially useful as well.

We’ll send this feature request to the team for logging and consideration. Appreciate the thoughtful detail you included here.

-Mark G.