Prompt details

Making prompt details or related details visible alongside an an artifact in galleries, feeds, or shared workspaces gives viewers a direct sense of how a result was produced. This helps them learn phrasing, assess originality, and decide whether and what to remix, while making details easily accessible to reuse for additional inputs.

When visible in galleries, prompt details makes work legible and reproducible by others. Users can be inspired by prompts created by others, and discover new ways to engage with the model. This reduces the initimidation of getting started for new users and expands creativy as users get more advanced.

Prompt details may appear inline under the artifact, in a side panel on selection, or within an expandable “Details” section. What is included varies: some products show just the raw prompt text, others also include parameters like model name, seed, style tags, or negative prompts. In audio tools, visibility often means surfacing descriptive tags or lyrical snippets. In image tools, it is usually the full text prompt with optional parameters. Choose the depth to expose based on the amount of control and transparency required by the user's experience level and contextual use case.

Details to include

Consider sharing all or some of these details alongside the generated asset:

  • The prompt itself
  • Negative tokens
  • Model name and version
  • Seed and profile details
  • Parameters like image size and ratio
  • Referenced attachments, with their purpose labeled
  • Descriptive tags or style tokens

In a generative setting, the prompt details can be action triggers in of themselves, where clicking on each adds it to the input box to be used in the next run. This makes the details interactive and not just informative, and encourages creative exploration.

Design considerations

  • Make prompt text easy to copy and reuse. Describing what you are looking for is a burden for people who lack prompt and context engineering skills, and all users benefit from capabilities to save them time and manual steps. Support learning and remixing by allowing users to copy the text on a click or send it to their input box.
  • Expose reference input (image, URL) when relevant. Not all context is provided via direct text. Allow users to see and access the images, seeds, and profiles that inspired the prompt and inspect them to understand their tokens and remix with them if they want.
  • Default to visibility in learning contexts. When the platform’s value is community discovery, make prompts visible by default. This normalizes openness and accelerates learning.
  • Give creators clear control. Offer a setting to hide or redact prompts on their own work. This balances community value with author consent.
  • Label additional parameters distinctly. If you include model, seed, or tags, group them separately from the main prompt. This helps users understand what is required for reproduction.
  • Support copy and remix actions. Place a “Copy prompt” or “Use as template” control adjacent to the visible prompt. This makes visibility actionable.
  • Design for cross-modal prompts. Audio and video may use tags or parameter sets rather than long text. Present them consistently as “prompt details” so users recognize the pattern.

Examples

Midjourney exposes the prompt details associated with each example in the gallery, including the prompt itself as well as parameters and custom styles
Sora2 reveals the prompt details for every video in the feed. However, users can change the details after the video is published, so it is not a reliable guide for other users wishing to emulate the original.
Suno shows the prompt used for each sample song in its gallery so users can understand how prompt tokens and parameters mix to create a new generation.