Generate a Firefly marketing image with a clear usage record
The image is on the landing page, the campaign goes live on Monday, and someone in a meeting asks whether you're allowed to use it. The answer depends on things that are easy to write down now and awkward to reconstruct later.

What you'll make
an illustrative marketing image from Firefly and a short record of how it was made, ready for your organisation’s publication review.
What you'll need
an Adobe account with Firefly access and generative credits, your work account if this is for work, and permission for any reference images you plan to upload. Check your plan rather than assuming every Firefly feature is included. About 30 minutes.
Example result.
Asset: harbourline-webinar-header-v2.png · Use: webinar landing page header
Model: Firefly Image 4 (Adobe model) · Prompt enhancement: off · References: none
Commercial-use terms checked: Firefly FAQ, 10 Oct 2026 · Beta label: none
Indemnity: not established · Content Credentials on export: not checked
Review: rejected v1 (invented logo on glass door), approved v2, marketing lead
1. Choose a use you can honestly illustrate
Start with a concept image, background or clearly illustrative visual. Don’t generate a supposed photograph of your real team, customer, premises or product and present it as authentic.
Write down the intended use, such as “abstract background for a webinar landing page”, and the constraints: room for a headline, a wide crop, no real brands or people.
Then decide about references. Uploading a competitor’s artwork, a photographer’s image or a film still as a style reference is an input decision you made, and nothing Adobe says about its training data answers it. You need permission for the way each reference will be used. For a first image, use none.
Why this works: an illustrative use with no uploaded references leaves fewer questions about where the image came from.
What you should see: one line on the use, a short list of constraints and “references: none” (or each reference with its permission).
2. Separate the three rights questions
“Can I licence this image?” is three separate questions wearing one coat. Separating them is most of the work.
| Question | What answers it | Who confirms |
|---|---|---|
| Commercial use | Adobe’s Firefly FAQ, and whether the feature has a beta label | You, from the FAQ |
| Copyright and third-party rights | A check of the image, your references and the intended use | Your legal contact |
| Indemnity | Your organisation’s Adobe agreement | The contract owner |
Adobe’s FAQ permits commercial use of outputs from non-beta features, and of beta features unless the product says otherwise. That isn’t a guarantee that an individual image clears every third-party right. Adobe offers IP indemnification on qualifying arrangements, subject to terms. Don’t write “covered by Adobe” unless the contract owner has confirmed it.
Why this works: each row has a different source and a different person, so one reassuring answer can’t stand in for all three.
What you should see: the commercial-use answer and beta status noted, and the other two rows marked “confirmed” or “not established”.
3. Generate from a specific brief
On the Firefly homepage, go to Image › Generate image. Under General settings, open Model and choose an Adobe Firefly model, not one listed under Partner models. Partner models have their own terms, and Adobe’s statements about its own models don’t carry across. Choose a wide Aspect ratio for a header.
If you pick Firefly Image 4 or Image 4 Ultra, Prompt enhancement is on by default. Open the prompt-feature icon beside Generate and turn it off for anything you’ll need to account for. Otherwise the prompt that produced the image isn’t the prompt you typed.
An illustrative photograph-style view of an empty contemporary meeting room at dusk. A long table sits on the right, with soft warm lighting and an out-of-focus city view. Leave uncluttered space on the left for a headline. Muted blue and grey colours. No people, logos, readable text or screens showing content.
Why this works: the composition instruction serves the layout, which is more useful than asking for something “stunning”. The exclusions reduce problems but don’t guarantee their absence.
What you should see: generated images in the wide format, with space on the left. Keep the original file of the one you choose. The same prompt won’t necessarily give the same image again.
4. Inspect the image and fill in the record
View it at the size and crop the campaign will use. Check backgrounds for logos, signatures, readable text and recognisable people. Look for malformed furniture and impossible reflections. Make sure the caption and placement don’t imply a real customer, product or location.
Then fill in this record and keep it with the chosen file:
Asset filename and intended use:
Date generated, app and account:
Exact model name and any beta label:
Prompt (and enhanced prompt, if used):
Reference files and permission basis:
Edits after generation:
Terms checked (link and date):
Indemnity: confirmed details / not established
Content Credentials on export: present / absent / not checked
Review decision and responsible person:
Why this works: a blank or unresolved field is better than a reassuring answer nobody checked.
What you should see: a record where every field is either filled from something you saw or honestly marked unknown.
Check the result
- Nothing in the background reads as a logo, sign, screen or real person at full size.
- The model in the record is an Adobe model, named exactly as Firefly shows it.
- Indemnity and Content Credentials say “not established” or “not checked” unless someone checked.
- The caption doesn’t present the image as a real place.
The usual failure: a small invented brand mark or line of lettering in the background, on a door, a wall display or a mug, that you only see at full size. Spot it by zooming into every flat surface before you approve the image.
Keep the meeting-room concept and wide composition. Remove all wall displays, signs, door lettering and decorative text. Leave the left third as a plain softly lit wall suitable for a headline.
Review the replacement on its own. It may fix one problem and introduce another.
Worked example: a webinar header that isn’t a real office
Fictional example. Harbourline, an invented software company, needs a header for a webinar on project handovers. The marketing lead uses Firefly Image 4 with prompt enhancement off and no references, and runs the prompt from step 3.
- The failure. The best candidate has a small invented logo etched on the glass door behind the table. At thumbnail size it’s invisible. At full width it looks like a real company’s office.
- The repair. The repair prompt removed the door lettering and the wall display. The replacement was checked again at full size and approved as v2. The record notes v1 as rejected and why.
- The honest fields. The record in the example result leaves indemnity “not established” and Content Credentials “not checked” until someone confirms them. The page caption calls it an illustration, never “our London office”.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: a colleague sends a competitor's office as a reference
A stakeholder emails a photo of a competitor’s reception and says “make it look like this”. Before generating anything, decide whether you have permission to use that photo as a reference at all. Usually you don’t. A safer route is to describe the qualities they like (light wood, low lighting, plants) in words. If the reference is used, the record must say so, with its source and permission basis, and the question goes to your legal contact before publication.
Optional training: ask the contract owner a narrow question
Ask which Adobe entitlement your organisation holds and whether it covers this model, output type and use. If indemnity is included, ask for the conditions, exclusions and reporting process. Keep the answer with your asset policy. Don’t shrink a careful contract answer into “all Firefly images are safe”.
Optional training: check the version the audience sees
A website may resize, crop or re-encode the export, and metadata such as Content Credentials can be lost. Check the published version for quality and disclosure. Content Credentials can show how an asset was made, but they aren’t a licence. If your policy needs a visible disclosure, use an ordinary caption rather than relying on invisible metadata.