# Build a useful gallery and reuse good images

> **Review scope:** Linked public documentation checked October 30, 2026. Examples are proposed checks, not recorded OD results; use your account's current controls.

A gallery introduces a character through pictures. Image reuse gives you dependable starting material for later work. This lesson organizes Mira's images without confusing a display choice with a permanent appearance change.

Mira is the fictional 30-year-old adult archivist from earlier lessons. A **scene** is one pictured situation. An image **model** is the selected generator. A **preset** supplies a reusable instruction; a saved picture is different because it contains actual visual information.

## 1 Find your accepted images

Open Mira's generated-image collection. Choose pictures you have inspected, rather than every attractive result. Start with the navy-jacket archive image and any successful edit from [the editing lesson](07_Edit_Images.md).

Give each saved copy a useful name in your own notes. For example:

```text
Mira_archive_navy_base
Mira_archive_green_jacket_edit
Mira_archive_watercolor_comparison
```

These are suggested filenames, not OD commands. Record the actual image identifiers when available.

For each picture, ask whether it still shows Mira's warm brown skin, brown eyes, black shoulder-length braids, and lean build. An image that drifts should not silently redefine her.

## 2 Recover the prompt before reusing it

Open an accepted image and look for **Remix** or **More → Details**, where available, to inspect its generation prompt. Save the image and prompt together. The Known State guide recommends this pairing for reuse. [Image reuse](https://guide.ourdream.ai/characters/consistent-images)

Add the actual model, date, and settings you can see. If the complete input is not exposed, write “effective prompt unavailable”; do not fill the gap from memory.

Copied prompt text can start a new generation. Selecting the original picture in Edit supplies a different kind of input. Choose the route that matches your goal.

## 3 Plan different jobs for your display pictures

Use this original four-picture plan as a starting exercise:

| Picture | What it demonstrates |
| --- | --- |
| Clear waist-up portrait | Mira is recognizable at a small size |
| Wider archive scene | Her surroundings make visual sense |
| Examining a closed folder | A simple action connects her to her work |
| Meeting Rowan | The scene distinguishes two different adults |

Rowan is a fictional 32-year-old adult courier with light skin, green eyes, short red hair, and freckles. Use a separate appearance clause for him; do not copy his features into Mira.

The plan is not a requirement to create four paid images immediately. Reuse suitable accepted pictures and fill only the gaps that matter.

## 4 Open Display Media

Open Mira's character editor. Locate **Character Studio → Profile → Display Media** if those labels appear. The Known State gallery guide describes this location, the first item as the cover, and up to four display items. Follow the slots actually shown in your account. [Gallery controls](https://guide.ourdream.ai/characters/photo-shoot-and-gallery)

Add or replace an item using an available generated image. Preview the collection before saving. For this exercise, place the clear portrait first.

Where drag-reordering is available, move items into the intended order and verify the cover afterward. [Reordering update](https://ourdream.ai/updates/feature-friday-12)

## 5 Check the gallery as a reader would

Look at the cover at a small size. Can you identify Mira? Does the archive scene belong to the same person? Is Rowan clearly a different adult?

Save the character changes through the current editor control. Reopen Display Media and the character preview to confirm that the intended order and cover persisted. A gallery change does not itself authorize publishing a previously private character; keep the character's visibility choice intentional.

**Checkpoint:** You have a readable cover, useful variety, and a note identifying which accepted source to use for future edits.

## Keep the lineage of an accepted image

For a sequence of edits, a useful record names each parent rather than only the latest attractive result. An original local note could read:

```text
Base A: accepted navy-jacket portrait; actual image ID recorded.
Edit B: jacket-color change from A; accepted after comparison.
Crop C: tighter framing from B; face and hands still assessable.
Video D: made from C; recorded model, motion text, charge, and clip ID.
```

These labels organize your notes; they do not retrieve absent media. Keep rejected candidates separately and name the actual source selected for the next operation. A crop changes framing and may hide a feature that was visible before. It is not evidence that the character's appearance changed.

This October 31 follow-up applies the supplied community reports of repeated edits and cropping without treating their eventual successes as native guarantees. Use the [current-form continuity module](../modules/current-form-continuity.html) if a deliberate transformation also changes which appearance record applies.

## Three common problems

1. **The wrong picture becomes the cover:** inspect the first display item, reorder if supported, and confirm after saving.
2. **Every item looks alike:** replace a redundant close-up with an accepted wider scene or different activity.
3. **Reusing text loses the face:** decide whether you need a new interpretation or a source-image edit. For continuity, return to the accepted in-app picture instead of expecting its prompt to carry its pixels.

Next: [Create Community Presets](24_Community_Presets.md). Back: [Edit images](07_Edit_Images.md) or the [Tutorial index](README.md).