Skip to content
BTW

How to document Ideogram work for client delivery

Ideogram surfaces more per-image state than most generators, from seeds to enhanced prompts. Delivering client work means copying that state out of the app and choosing privacy and file formats deliberately.

Published July 22, 2026.

Ideogram is one of the few image tools that shows its documentation-relevant state directly in the interface. Select any image and the Details Panel carries its Seed Number, and, if Magic Prompt was active, both the original prompt you typed and the enhanced prompt Ideogram actually ran. That panel is the closest thing the tool has to a generation record, and everything in it stays on Ideogram's side. The downloaded file carries none of it.

Two defaults deserve attention before any client work happens. First, images are public by default unless you choose private generation where it is available, and private generation requires a Plus plan or higher. For confidential client work that is a decision to make before generating, not at delivery. Second, reproduction is weaker than the visible seed suggests. Ideogram documents that in Model v3.0, using the same Seed Number with different Render Speeds no longer produces identical images the way earlier versions did, and changing a key concept in the prompt or switching to another model produces different images entirely. The seed is a useful field in your record. It is not a guarantee of re-creation.

Downloading has its own discipline. Ideogram's documentation tells you to use the Download controls rather than the browser's right-click menu, because the controls decide the file type and size, with JPEG, PNG, and WebP available, some types and sizes locked to paid plans, and JPEG disabled for transparent outputs. Library multi-select downloads arrive as a ZIP that follows your most recently used download rules. Every one of those choices changes what you archive, so your record should say not just which image shipped but which format and size of it.

What Ideogram stores on its side

  • Every image's Seed Number appears in the Details Panel on desktop or below the image on mobile, and Ideogram assigns a random seed when you do not enter one. Source
  • Ideogram documents that in Model v3.0, using the same Seed Number with different Render Speeds will not generate identical images as in earlier versions. Source
  • When Magic Prompt was active, the Details Panel shows both the original and the enhanced prompt for a selected image. Source
  • Images are public by default unless you choose private generation where it is available. Source
  • Private generation requires a Plus plan or higher, and private images remain accessible and downloadable in JPG format after the subscription ends. Source
  • Downloads are offered as JPEG, PNG, or WebP, some file types and sizes require a paid subscription, and multi-selected Library images download together as a ZIP file. Source
  • Ideogram states that it does not claim ownership of your generated outputs or restrict your rights in them. Source

What gets lost without your own record

  • The downloaded file carries neither the Seed Number, nor the prompt, nor the model version; all of that lives in the Details Panel on Ideogram's side.
  • On a default account the image is public from the moment of generation, so confidentiality for client work depends on choosing private generation beforehand rather than on anything in your delivery.
  • A seed alone no longer guarantees reproduction, because v3.0 ties output to the Render Speed, and any change of prompt concept or model produces different images.
  • Saving via the browser's right-click menu bypasses the Download controls and can archive a different file type and size than you intended.
  • After a paid plan ends, private images stay downloadable in JPG format and the full set of download options requires resubscribing, so uncompressed masters need to be exported while the plan is active.

The documentation checklist for Ideogram

  1. Copy the Seed Number from the Details Panel into your record for every image you shortlist.
  2. Record the model version and the Render Speed together with the seed, because v3.0 output changes when the Render Speed changes.
  3. If Magic Prompt was active, save both prompts shown in the Details Panel, the one you typed and the enhanced one Ideogram ran.
  4. Set visibility to private before generating anything confidential, and note in the record that the work was generated privately.
  5. Download through the Download menu rather than the browser right-click, choose the file type and size deliberately, and write down what you archived.
  6. For shortlist batches, use Library multi-select so the ZIP applies one consistent download rule, and log that rule with the batch.

The Details Panel earns a place in your workflow as the thing you capture before it changes. Copy the seed, both prompt versions, the model, and the Render Speed into your record while the image is on screen, and pair them with the exact file you archived from the Download menu. If the work is confidential, the public-by-default setting means the record should also state when the image was made private, or that it was generated privately from the start.

For EU deliveries, image work is covered by the same Article 50 transparency logic as video: AI-generated content is expected to be identifiable, penalties for transparency violations reach up to €15 million or 3% of worldwide turnover, and the practical defence is a delivery record showing what was generated, disclosed, and archived. Ideogram gives you unusually good raw material for that record. It just keeps it in a panel instead of in the file.

Frequently asked questions

Ideogram shows a seed for every image. Is that enough to recreate it later?

Not on its own. Ideogram documents that in Model v3.0 the same Seed Number with a different Render Speed no longer produces identical images, and changing a key concept in the prompt or switching models produces different images. Record the seed together with the prompt, the model, and the Render Speed.

Is my client work visible to other people on Ideogram?

By default, yes. Images are public unless you choose private generation where it is available, which requires a Plus plan or higher. For confidential work, set visibility before generating and note the setting in your record.

Which file should I archive as the master?

Choose it deliberately in the Download menu, where JPEG, PNG, and WebP are offered, some types and sizes are locked to paid plans, and JPEG is disabled for transparent outputs. Record which format and size you archived, because a right-click save can silently give you something else.

What happens to my private images if I cancel my subscription?

Ideogram states that private images remain private after the subscription ends and stay accessible and downloadable in JPG format. Unlocking the full set of download options again requires resubscribing, so export your preferred masters while the plan is active.

Who owns the images I deliver to the client?

Ideogram states that it does not claim ownership of your generated outputs or restrict your rights in them, and that you are responsible for making sure the content does not violate laws or third-party rights. Ownership and documentation are separate questions, and the client will eventually ask for both.

Related guides

  • How to document AI-generated work for client delivery What broadcasters, platforms, agencies, and rights offices already require when AI is part of delivered work, and the per-shot checklist that answers all of them.
  • EU AI Act Article 50 for creative teams What the transparency obligations for AI-generated and AI-manipulated content actually say, the real timeline and penalty ceiling, and what a team should record to be ready.
  • AI provenance: what you can prove and what you cannot An honest map of provenance claims: what a record can demonstrate about inclusion, integrity, and time, and which causal claims no system can support.
  • Prompt and model documentation: a practical checklist for studios The fields worth capturing for every generation: prompts, models, versions, settings, references, and edits, and how to keep the habit alive in production.
  • What is an AI production log? An AI production log is the per-asset record of prompts, models, settings, references, edits, rights decisions, and approvals behind AI-assisted work. Here is the minimum useful structure and the limits of what that record can prove.
  • C2PA vs. AI workflow documentation C2PA and AI workflow documentation solve different parts of the provenance problem. C2PA protects signed assertions attached to media; workflow records preserve prompts, sources, decisions, rights, versions, and approvals around the file.
  • AI shot log template for image and video production A practical AI shot log template for prompts, models, references, versions, human edits, disclosure, and approval. Download the CSV and adapt the field guide to your production workflow.
  • How to record client approval for AI-generated work A client approval record for AI-generated work should identify the exact version, disclosed AI use, review scope, requested changes, approver, and time. This guide turns sign-off into evidence instead of an ambiguous email.
  • Guide editorial and verification policy How Behind The Workflow researches, sources, dates, updates, and corrects its AI production guides. Product facts use primary sources, legal claims link to official text, and machine-readable markup mirrors visible content.
  • How to document Sora work for client delivery Sora embeds C2PA metadata in every asset and marks downloads with a visible moving watermark, but the prompts, iterations, and cameo consents behind a clip stay in the app. This guide covers what OpenAI's provenance signals prove and what you still have to record before client delivery.
  • How to document Google Veo work for client delivery Every Flow output made with Veo carries an invisible SynthID watermark, and Gemini can verify it, but the check names Google AI as the origin and nothing else. This guide covers what to record so a Veo delivery can answer the questions SynthID cannot.
  • How to document Luma Dream Machine work for client delivery Dream Machine keeps your work organized in Boards and an Ideas stream, but the watermark and the commercial license of a clip depend on the plan that generated it, and the exported file names neither. This guide covers the records that close that gap before client delivery.
  • How to document Midjourney work for client delivery Midjourney keeps a searchable archive of everything you generate, but the record stays inside your account and images are publicly discoverable by default. This guide covers what midjourney.com actually stores, what never travels with a delivered file, and the per-job checklist that closes the gap.
  • How to document Runway work for client delivery Runway keeps your generations in sessions and an asset browser, with a Fixed seed option for related takes, but the video you deliver carries no prompt, seed, or settings. This guide covers what Runway stores in the account and what a producer has to record per shot.
  • How to document ComfyUI work for client delivery ComfyUI automatically embeds the workflow graph in the metadata of every image it saves, which makes it unusually self-documenting. This guide covers what that embedded workflow proves, where it silently disappears, and what a client record still needs on top.
  • How to document self-hosted Stable Diffusion work for client delivery A self-hosted Stable Diffusion setup writes its generation parameters into every image by default, at least in the AUTOMATIC1111 web UI most teams run. This guide covers what that buys you, what silently breaks it, and what a client record still needs.
  • How to document FLUX work for client delivery The FLUX API from Black Forest Labs delivers each image through a signed URL that stays valid for ten minutes, and the docs describe no archive to return to later. This guide covers what the API gives you at request time and the logging your pipeline must do in that window.
  • How to document Adobe Firefly work for client delivery Firefly attaches a Content Credential naming the model and version to what it generates, and its API returns the seed for every image. This guide covers what that provenance layer proves, how it can be stripped, and what a client delivery record still adds.

Every requirement in this guide is answered from a record kept while the work happens. BTW keeps that record for you.

Start your own record