Skip to content

Conversation

@Filippo-Venturini
Copy link

@Filippo-Venturini Filippo-Venturini commented Nov 14, 2025

Summary

This draft PR is meant to continue the discussion from [Issue #6291] and the related Discord conversation regarding original image metadata for upscaled images.

Currently, upscaled images store a reference to the source image via upscale_initial_image, but the full metadata (prompt, seed, scheduler, etc.) is not stored.

Two alternatives are under discussion:

  1. Expose a UI way to jump to the source image in the gallery, leveraging the existing reference.
  2. Store the full original metadata under a separate field (e.g., source_image_metadata) for external/export use.

This PR does not include any implementation; it is intended to facilitate review and discussion among maintainers.


Related Issues / Discussions


QA Instructions

Not applicable — no code changes in this PR.


Merge Plan

  • Marked as draft to indicate discussion PR.
  • No merging expected until a consensus on the approach is reached.

Checklist

  • PR title is short but descriptive
  • Implementation to be added after discussion
  • Documentation updated once implementation is decided

@github-actions github-actions bot added the frontend PRs that change frontend files label Nov 14, 2025
@lstein
Copy link
Collaborator

lstein commented Dec 16, 2025

Here's my 2c (with apologies for taking so long to join the conversation). While it is more elegant to maintain a reference to the source metadata via the existing upscale_initial_image field, there is nothing to prevent the user from inadvertently deleting the initial image and thus irrevocably losing the generation parameters. Therefore, I'd go with the second proposal of using a source_image_metadata field.

What do you think of the idea of generalizing this so that if there is a chain of source images (e.g. a series of upscales are applied), the metadata from each upscale operation is presented as well.

@Filippo-Venturini
Copy link
Author

Thanks for the feedback, I agree. Relying solely on upscale_initial_image does risk losing metadata if the source image is deleted, so the source_image_metadata approach makes more sense.

I also agree that generalizing this to include the full chain of source images (e.g. multiple upscales) would be beneficial, and I’m happy to proceed in that direction.

@skunkworxdark
Copy link
Contributor

Why not do both by adding the 'upscale_initial_image' inside the 'source_image_metadata' so for people that do keep everything they have a way of traversing back to the original.

@joshistoast
Copy link
Contributor

I like @skunkworxdark's idea of having both the original and upscale with full metadata and pointers to each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

frontend PRs that change frontend files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants