Skip to content

History

Local Dream keeps a per-model generation history so you can revisit recent work without manually organizing every output yourself.

What It Stores

Each model has its own history view.

  • the full history page shows that model's generated images
  • the generation result screen also shows a smaller list of recent history entries

Starting with v2.5.0, history is backed by a database rather than per-record JSON files on disk. Each entry records additional fields such as the generation mode (txt2img / img2img / inpaint / ultrafix), denoise strength, a favorite flag, and (where applicable) the upscaler id. Upscaled and UltraFix images are stored as first-class history entries so you can find and re-use them just like regular generations.

The list is paged, so very large histories load smoothly a chunk at a time instead of all at once.

Global History Screen

Besides the per-model history, there is a global History screen opened from an entry in the top-right of the home screen. It shares the same grid, filter sheet, and parameter / share flow with the run screen, but spans every model — including models you have since deleted (their history is kept by default). It is the place to browse, filter, favorite, back up, or batch-manage across your whole library.

First-Run Migration

The first time you open Local Dream after upgrading to v2.5.0, a one-shot migration screen appears and imports your existing on-disk history into the new database. The migration is quick on most devices, but please wait for it to finish before leaving the app — once it completes, a flag is stored and the screen will never appear again.

Filter and Sort

The history tab has a top "current / all" toggle that switches between entries for the model currently loaded and entries for all models.

A bottom-sheet filter is also available, where you can narrow the list by:

  • generation modes (txt2img / img2img / inpaint / ultrafix)
  • favorites (Favorited / Not favorited)
  • models
  • image sizes
  • time range
  • schedulers
  • devices (CPU / GPU / NPU)
  • prompt substring

You can also pick a sort order from the same sheet. The result and history parameter detail dialogs now also show the generation mode and denoise strength alongside the other parameters.

Favorites

You can mark any image as a favorite:

  • from the action row on the result page
  • from the history-preview overlay (which also offers upscale and UltraFix, with the same gating as the result page)

Favorited entries get a heart badge on the grid, and the filter sheet can show only favorites (or only non-favorites).

Copy Parameters From History

You can copy generation parameters from a historical image back into the current generation form.

This is useful when you want to:

  • reproduce a result you liked
  • compare a new prompt against an older setup
  • continue iterating from an earlier image without re-entering everything manually

If you want to send parameters between devices instead of within the same install, see Share Parameters.

1-Click img2img

Local Dream also supports a 1-click path from an existing image into img2img.

You can send an image directly to img2img from:

  • the generation result page
  • the history page

This is much faster than saving the image first and then selecting it again manually.

Batch Select, Save, and Delete

The history page supports multi-select. Select all covers every entry that matches the current filter, not just the part of the list currently scrolled into view.

Once one or more entries are selected, the selection toolbar exposes:

  • Save — writes every selected image into your photo gallery in one run. A confirmation dialog asks first, a modal progress dialog blocks dismissal until the run finishes, and the result is reported with a toast (how many saved, how many failed).
  • Delete — removes the selected entries. A large batch is deleted in a single transaction so the grid refreshes once, cleanly, with no leftover thumbnails.

Backup & Restore

You can export your generation history — images plus their parameters — to a single .zip archive with a JSON manifest, and import it again later or on another device.

  • Import merges by (model, timestamp): entries you already have are skipped, so re-importing the same backup is safe.
  • Records whose model is not installed are still imported and stay viewable in the global History screen; install the model later to act on them fully.

This is the way to move your history between devices or keep an offline backup. (For sending just the parameters of a single image, see Share Parameters instead.)

Keeping History When Deleting a Model

Deleting a model keeps its history by default — there is an opt-out checkbox in the delete dialog if you want the images gone too. Orphaned history stays browsable in the global History screen.

Screen Stays On During Model Sessions

While the model run screen is active, the display is kept on so long generations and batch operations are not interrupted by the screen timeout. The behavior is automatic and ends as soon as you leave that screen.