Adobe keeps marketing Firefly as "commercially safe" because it was only trained on Adobe Stock images and public domain content. Is this actually true? And what are the exact commercial rights?
@TransactionalLaw_Dan_34 This is incredibly useful. I had a client last month who wanted to trademark a logo I created using Firefly as a starting point. I did extensive modifications in Illustrator -- probably 80% of the final mark was my own vector work -- but I wasn't sure if the Firefly origin would be a problem.
What kind of documentation do you recommend keeping? Screenshots of each iteration? Illustrator version history? I want to make sure I'm covered if the trademark is ever challenged.
@tyler_92_16 The recursive training data concern you're describing is called "model collapse" in the ML research community, and it's a well-documented phenomenon. When generative models are trained on their own outputs, the quality and diversity of outputs degrades over successive generations.
Adobe is aware of this. Their research team published a paper in late 2025 describing their data curation pipeline, which includes filters to identify and exclude AI-generated content from training datasets. They use a combination of C2PA metadata detection and statistical classifiers to flag AI-generated submissions.
However, no filtering system is perfect. Some AI-generated images will inevitably slip through, especially as generation quality improves and becomes harder to distinguish from photographs. This is an industry-wide challenge, not unique to Adobe.
For the purposes of this thread's topic -- commercial rights -- the recursive training issue doesn't directly affect your rights as a Firefly user. Your commercial license and IP indemnity remain the same regardless of what percentage of the training data is AI-generated. But it's worth monitoring because it could affect output quality over time.
Not gonna lie, following up on my earlier comparison post with some new info. Midjourney just updated their ToS this week (February 24 apparently, 2026), and there are some notable changes.
Midjourney now explicitly states that subscribers own their outputs and that Midjourney will not assert copyright claims over user-generated images. This was always implied but never explicitly stated. They also added language about "best-effort" IP screening -- they claim to have implemented filters that prevent outputs from closely replicating copyrighted works in their training data.
However, they still offer zero IP indemnification. Their new ToS includes a clause that reads: "Midjourney makes no representations regarding the intellectual property status of outputs and disclaims all liability for third-party IP claims." This is unchanged from their previous terms.
So the gap between Midjourney and Firefly on the legal safety front has actually widened. Midjourney's image quality continues to improve, but their legal protections remain the weakest among the major players. For commercial work, especially anything client-facing or brand-critical, Firefly's legal advantages are now even more pronounced smh.
@the_silent_type_20 The EU AI Act has extraterritorial reach, similar to GDPR. Under Article 2, the Act applies to providers and deployers regardless of their location if the AI system's output is "used in the Union."
In your scenario, both parties have obligations. The US agency is a "deployer" of the AI system and has disclosure obligations if they know the content will be distributed in the EU. The German client, as the party publishing the content in the EU market, has the primary disclosure obligation.
In practice, this means US-based agencies working with EU clients need to build EU AI Act compliance into their contracts. The agency should disclose to the client that AI was used, and the client should include appropriate disclosures when publishing in the EU. Both parties should document their compliance steps.
This is essentially the same contractual framework that agencies already use for GDPR data processing. The AI Act adds another layer of compliance, but the mechanics are familiar. If your contracts already address GDPR, adding EU AI Act provisions is a natural extension.
I'm dealing with a force majeure dispute right now. The other party claims COVID-era supply chain issues are still causing delays in 2026. At some point, a 6-year-old pandemic isn't a force majeure event anymore — it's a known risk that should have been planned for.
Join the discussion. Create a free account to reply.
Late to this thread but wanted to add a data point. I run a small agency and we switched all client deliverables to Firefly about a year ago specifically because of the indemnity. The peace of mind is real, but read the fine print: the indemnity generally applies to the standard output, not to anything you fed in as a reference image or built on top of with other tools.
We had a client legal team ask us to confirm exactly which plan we were on before they'd approve the campaign. So keep your invoices and plan details handy, you may get asked to prove it.
Quick clarifying question for anyone who knows: if I use Generative Fill in Photoshop to extend a photo I already own, who owns the extended part? The original photo is mine, but the fill is Firefly. Does the whole composite get the commercial license and indemnity?
I keep seeing conflicting answers on this and it matters for a stock photo set I'm trying to license out.
@mark_d_92 Not legal advice and this varies by your exact plan terms, but in general: the Firefly-generated pixels and the human-authored pixels are treated separately for both license and copyright purposes. Adobe's commercial use grant and indemnity generally attach to the Firefly output portion on a paid plan, while your ownership of the original photo is unaffected.
The copyright wrinkle is separate from the license question. In the US, the Copyright Office has taken the position that purely AI-generated elements are not protectable, while the human-authored and human-arranged parts can be. So a composite can be partly protectable and partly not. For a stock set you intend to license, that distinction can matter to your buyers, and I'd disclose the AI-assisted portions rather than imply the whole frame is your original authorship.
If the licensing terms of the stock marketplace you're using have their own AI disclosure rules, those control on top of all of this. Check those before you upload.
This thread is gold. One thing I never see mentioned: the free Firefly tier and the free Express plan are NOT the same as a paid Creative Cloud plan for commercial purposes. I almost shipped a client deck with images I'd made on a free trial before someone caught it.
Adobe's own help docs distinguish between the tiers. If you're billing a client, be on a paid plan, full stop.
Has anyone here actually triggered the indemnity? Like, has anyone gotten a real third-party IP claim on a Firefly image and had Adobe step in to defend? Everyone talks about the indemnity as a feature but I've never seen a single account of it actually being used.
Genuinely curious whether it's a real backstop or just marketing that nobody has stress-tested yet.
@gigworker_sf I've looked for this too and I haven't found a public case where Adobe's Firefly indemnity was litigated or invoked in a way that became public. That doesn't mean it hasn't happened, indemnity claims are usually confidential and resolved quietly, but the absence of public examples cuts both ways.
The honest read is that the indemnity is contractual, it has caps and conditions, and it's only as good as the terms you actually agreed to. Enterprise terms generally have higher caps and a clearer claims process than the standard plan. Read your actual agreement rather than the marketing page.
The condition that bites people is the prompt one. Adobe's indemnity generally does not cover output you generated from a prompt that itself referenced a third party's trademark or a named artist, or where you uploaded a reference image you didn't have rights to. So if you prompt "in the style of [living artist]" or "[brand] logo," you're likely outside the protection.
Keep your prompts clean and generic and the indemnity is much more likely to actually hold.
@brandbuilder_jen this is the part I wish Adobe put in bold at the top. People treat "trained on licensed content" as if it means you can prompt anything and be safe. The training data being clean does not make a trademark-infringing prompt safe.
Question on the documentation point from earlier in the thread. For trademark work where Firefly was a starting point, what level of records is enough? I keep the original generation, the prompt text, and my layered working file. Is that overkill or about right?
Trying to figure out where the reasonable line is so I'm not hoarding every screenshot forever.
@contract_questions That's a sensible record set and I'd say it's about right, not overkill. For a mark you intend to register and possibly enforce, the goal is to be able to show human authorship and the chain of modification. Prompt text, the raw generation, your layered working file, and a dated export of the final mark generally cover it.
The reason this matters: if a registration is ever challenged on the ground that the mark is AI-generated and lacks human authorship, your ability to show substantial human creative contribution is the answer. A trademark and a copyright are different rights, but Examiners and opposing parties increasingly ask about AI origin, so being able to document the human work is just good hygiene.
None of this is legal advice for your specific mark, and registration strategy depends on what you're actually selling and where. But the records you described are the right instinct.
Switching topics slightly. Does the commercial license survive if I cancel my Creative Cloud subscription? I made a bunch of marketing assets last quarter and I'm thinking of dropping to a cheaper plan. Do I lose the right to keep using the images I already generated?
@mike.flynn Generally the license grant for content you created while on a paid plan continues for that already-generated content, but the indemnity and ongoing protections can be tied to maintaining an active eligible plan. The two are not the same thing.
I'd verify the exact current language before you downgrade, because Adobe has revised these terms more than once. Don't assume a Reddit comment from two years ago still reflects the current agreement.
Friendly mod note: this thread keeps drifting into "what does my specific plan cover." That's great discussion, but please remember none of us can see your actual agreement. When you post a question, mention which plan you're on (free, Creative Cloud individual, Teams, Enterprise) because the answer genuinely changes by tier.
Keeping the thread useful for the next person who lands here. Carry on.
Reporting an outcome for the group. I sell on Amazon and Etsy and I switched my product mockups and lifestyle backgrounds to Firefly about six months ago. No takedowns, no IP complaints, smooth sailing.
The one snag: Etsy now asks sellers to disclose AI involvement in listings under their policy. So even though the images are legally fine, the marketplace has its own disclosure rule layered on top. Make sure you check the platform you sell on, not just Adobe's terms.
Following up on my model-collapse comment from way back. Appreciate @too_tired_for_this_28 setting me straight that it doesn't affect my commercial rights. I was conflating two separate issues.
For what it's worth, output quality on the newer Firefly model has been noticeably better for me lately, so whatever filtering they're doing seems to be holding for now.
Does anyone put AI image terms into their client contracts? After reading this thread I added a short clause saying which tool I use, that the client gets the deliverable, and that the client is responsible for any prompts or reference materials they direct me to use.
Felt like cheap insurance. Curious if others handle it in the contract or just keep it informal.
@freelance_kara I do something similar. My deliverables clause now says I assign whatever rights I have in the final work product, and a separate line notes that AI-assisted elements may have limited or no separate copyright protection. Being upfront has actually made clients trust me more, not less.
Jumping in on the contract angle since it's my wheelhouse. @freelance_kara your instinct is good. The key drafting issue people miss: you can only assign rights you actually have. If part of the deliverable is purely AI-generated and therefore not protectable by copyright in the US, you can't magically convey ownership of something that isn't owned.
A clean way to handle it is to assign all rights you do hold, grant the broadest permitted license to use the deliverable, and have the client acknowledge that certain AI-generated elements may not be subject to exclusive copyright. That's honest and avoids a later "you promised me exclusive ownership" dispute.
This is general information, not advice on your particular contract. If a deliverable is brand-critical, it's worth having someone look at the specific assignment language.
The point about not being able to assign what you don't own is something I had completely wrong. I've been telling clients they get "full ownership" of AI-assisted work. Time to fix my contract template.
Thanks to the attorneys in here actually engaging, this is more useful than the official help pages.
Slightly different use case: we're a nonprofit and we use Firefly for fundraising materials and our annual report. Same commercial rules apply to us even though we're not selling anything, right? "Commercial use" in these terms usually means any use beyond personal, not strictly making money.
Want to make sure we're not accidentally outside our license because we assumed nonprofit equals non-commercial.
@nonprofit_dev_ray You're thinking about it correctly. "Commercial use" in most of these AI image terms is defined broadly as any business or organizational use, not just selling. A nonprofit using images in an annual report, on its site, or in fundraising is generally a business use that needs the paid commercial license, not the free personal tier.
Get your org onto a paid plan and you're in the clear under the same rules everyone else here is discussing. The nonprofit status doesn't change the Adobe license tier you need.
Real talk, how does Firefly compare to just licensing Adobe Stock images directly? For a lot of my work the stock library already has what I need and the licensing is dead simple. Is there a legal advantage to one over the other, or is it purely a creative-flexibility thing?
@davebakes Both are fine commercially on a paid plan. Stock gives you a known photographer and a clean license history, which some corporate clients prefer for the paper trail. Firefly gives you something nobody else has and avoids the "three competitors used the same stock photo" problem.
I use both. Stock when an existing image fits, Firefly when I need something custom or want exclusivity.
From the in-house side: when our procurement team vetted Firefly for company-wide use, the things they cared about were the indemnity cap, whether it applied per-claim or aggregate, and the carve-outs (reference images, prompt-introduced IP, anything fed through third-party tools). The marketing page answered none of that, the actual enterprise terms did.
If you're rolling this out across a team, get the real terms doc and have someone read the indemnity section line by line. The cap number matters a lot if you're a large brand.
@legalops_tasha that's the most concrete answer to my earlier question, thank you. Per-claim vs aggregate is exactly the kind of thing that turns a comforting number into a not-so-comforting one once you do the math on a real dispute.
Photographer here, slightly defensive but trying to be fair. My concern isn't the legal safety of Firefly, it's that "trained only on licensed Adobe Stock" means a lot of contributors like me had our work used to train the model, sometimes under stock contributor terms we agreed to before generative AI was even a thing.
That's an ethics and contributor-compensation issue, not a user-side IP risk. For the buyer, Firefly is clean. For contributors, the consent story is messier than the marketing suggests. Worth knowing where your images come from.
@photog_marcus That's a fair distinction and worth keeping separate from the user-rights topic. Adobe did roll out a contributor compensation program and updated its stock contributor terms to address generative training, but whether that adequately compensates contributors is a legitimate ongoing debate.
For the thread's core question, you're right that it doesn't change the commercial safety for the end user. But it's an honest caveat that the "ethically sourced" framing is doing some heavy lifting, and reasonable people disagree on whether retroactive contract terms count as real consent.
We use Firefly for in-app illustrations and our marketing site. One thing that surprised me: our investors' diligence checklist specifically asked whether any product imagery was AI-generated and under what license. Being able to say "Firefly on a paid plan with indemnity, prompts documented" was a clean answer.
If you're a startup that might raise or get acquired, the documentation everyone's mentioning isn't just for IP disputes, it shows up in diligence too.
@saas_founder_eli huge point. Diligence is where sloppy AI-asset hygiene comes back to bite you. A folder of clean prompt logs and plan invoices is worth more than people think when a buyer's lawyers start asking questions.
Naive question, sorry. If I generate something in Firefly and it happens to look a lot like a real product or a famous painting, am I covered or not? I'm not prompting for it on purpose, but the model sometimes lands somewhere recognizable.
Trying to understand whether "I didn't mean to" matters for the indemnity.
@kdesigns_oh Intent matters less than you'd hope. Copyright infringement generally doesn't require that you meant to copy, and trademark and right-of-publicity claims turn on likelihood of confusion or use of identity, not your state of mind. So an accidental near-match to a famous work or a real product can still draw a claim.
That said, if you used a clean generic prompt, didn't upload an infringing reference, and the output coincidentally resembles something, you're in a much better position both factually and under most indemnity terms. The carve-outs that void indemnity are usually about what you put in, not random model behavior. If an output looks uncomfortably close to a specific known work, the safe move is to regenerate rather than ship it.
General information only. If something you generated is genuinely close to a recognizable brand or artwork, get eyes on it before it goes to print.
@PatentPam_Esq that's really clarifying, thank you. "Regenerate rather than ship it" is going on a sticky note above my monitor. I've definitely shipped a couple that I now want to go back and look at.
Practical workflow tip that's saved us headaches. We built a simple intake form for every client project: tool used, plan, who supplied any reference images, and a yes/no on whether the client directed any specific prompts. Takes thirty seconds and it means if anything ever comes up we can reconstruct exactly what happened.
Pair that with keeping the original generations and you've got a defensible record without it being a burden.
Reading this whole thread top to bottom as someone just starting to sell digital products. The big takeaways I'm pulling out: paid plan always, keep your prompts clean and generic, save the originals and prompt text, and don't assume the marketplace you sell on has the same rules as Adobe.
Did I miss anything important? Want to make sure I start with good habits instead of fixing them later.
@newbie_creator_22 you nailed the big four. I'd add one: read the indemnity carve-outs once so you understand what voids your protection (referenced trademarks, named artists, uploaded images you don't have rights to). You don't need to memorize it, just know the shape of it so you don't accidentally step outside it.
Starting with these habits is way easier than retrofitting them onto a year of messy files. Good on you for asking early.
This has turned into one of the more useful threads in the IP & Content category, so I'm pinning it. Quick recap of what the regulars and the attorneys here have converged on, none of it legal advice for your specific situation:
Firefly on a paid plan is generally the safest mainstream option for commercial image work because of the licensed training data plus contractual indemnity. The indemnity has caps and carve-outs, so keep prompts clean, don't upload reference material you don't have rights to, and save your generations and prompt text. Copyright protection for purely AI-generated elements is limited in the US, which matters for ownership and assignment language. And always check the specific platform or marketplace rules on top of Adobe's terms.
If your matter is high-stakes or brand-critical, that's the point where a quick attorney review pays for itself. Thanks to everyone who contributed real experience here.