I'm encountering a persistent issue where Adobe Firefly is appending a small "Adobe Stock" watermark to the lower-right corner of generated images, despite being on a paid Creative Cloud plan that includes the full Firefly service. This is severely limiting my ability to use the outputs in production client work, which was the primary reason for our subscription tier.
I have conducted a systematic check to rule out common causes:
* **Account Status:** Verified in Adobe Admin Console that our enterprise seat is active, with "Generative Credits" available and the Firefly service enabled.
* **Usage Context:** Generating images directly within the Firefly web app (`firefly.adobe.com`), not via the API or within another Adobe application like Photoshop.
* **Prompt Engineering:** Experimented with prompts that explicitly avoid trademarked characters or styles (e.g., "a generic fantasy landscape in a painterly style"). The watermark appears regardless of prompt specificity.
* **Output Format:** Tried both JPEG and PNG downloads. The watermark is present in both.
The workflow is straightforward, but here is the exact sequence I follow:
1. Log into `firefly.adobe.com`.
2. Select "Text to Image."
3. Input prompt: `A serene lakeside cabin at dawn, digital art`.
4. Select "Photo" style.
5. Click "Generate."
6. Download the preferred result via the download icon.
The resulting image contains the discreet "Adobe Stock" text watermark. This suggests a potential backend licensing flag misapplied to our account.
Before I engage Adobe Support, I wanted to query the community to see if this is a known issue with a documented resolution. Specifically:
* Has anyone else on a paid plan (Teams or Enterprise) experienced this?
* Were there specific account or permission configurations that resolved it?
* Is there a chance this is intended behavior for certain types of generated content, even on paid plans?
Any reproducible steps to clear the account cache or force a license re-validation would be appreciated. I will update this thread with any solution provided by Adobe Support for future reference.
-ck
You've checked the obvious stuff, which is good. But before anyone here can give you real advice, you need to prove the cost of the problem.
> severely limiting my ability to use the outputs in production client work
That's a business impact claim. I need to see the actual bill. Screenshot your Adobe Admin Console billing page showing the paid plan and the specific Firefly service line item. Blur out your account number, but leave the product SKU and cost visible.
Without that, we're just guessing about license tiers and your admin might have provisioned the wrong service. Happens all the time with cloud entitlements.
show me the bill
Yep, user389 is steering you in the right direction. That billing detail is often the culprit. In our migration project, we found our seat licenses were active but the actual billing assignment for the premium image gen was still stuck on a trial SKU. Adobe's console can be weirdly siloed like that.
Ask your account admin to pull the invoice and cross-check the SKU against the current Firefly service tiers. It's a quick fix if that's it. Good luck!
Trust the trial period.
You've done a good job ruling out the usual suspects, particularly confirming you're working directly in the web app. That's a crucial detail.
Could you clarify one point? When you say you checked your enterprise seat is active with credits, did you also verify the "Commercial Use" terms for your specific Firefly service? Some enterprise bundles include Firefly but still require a separate toggle to permit commercial outputs without the Stock attribution. That setting can be in a different part of the Admin Console than the credit display.
—daniel
That's a solid point. Our company dashboard shows our "Generative Credits" but I haven't actually seen a separate "Commercial Use" toggle anywhere. I've only looked at the Billing and Services sections.
Is that setting usually under user permissions or a product-specific terms agreement? I'm asking our admin to look, but knowing where to point them would help a lot.
Yeah, the "Commercial Use" flag is buried. It's not in Billing or the main Services list.
Your admin needs to check the actual product-level Terms for your Firefly service subscription in the Admin Console. It's often a separate, tiny checkbox agreement you accept after the main seat license is assigned. I've seen it tucked away on the service detail page itself, almost like an EULA you have to acknowledge.
Tell them to look for any link labeled "Terms" or "Usage Rights" on the Firefly service line. It's a weird, easy-to-miss step. Good luck getting them to find it
That's the exact step.
Can confirm the "Commercial Use" toggle exists as a separate action on the service detail page. It's not automatic with the credit purchase. Our team missed it for a week after provisioning.
The UI label on ours was "Review Terms", and clicking it opened a modal with a single checkbox at the bottom. No new info, just the commercial use grant. Ticking it and saving fixed the watermark issue instantly.
Benchmarks don't lie.
Good rule out of the basic prompts and formats. You've missed one variable. The web app's default generation style.
It defaults to "Photo", which pulls from Adobe Stock's reference library more heavily. Switch your generation style to "Art" or "Graphics" and test. The watermark is tied to the source training data licensing, and the style setting changes that source pool.
If that stops the watermark, then your issue is the "Commercial Use" toggle others mentioned, but specifically for the "Photo" style assets. Still an admin problem, but you've got a workaround until they find the checkbox.
If it's not a retention curve, I don't care.
That "workaround" misses the point. You're still paying for a service that won't do the core job.
If switching to "Art" style is the only way to avoid watermarks on a paid plan, then Firefly's training data is half-baked. Stock licensing shouldn't bleed into the final product if you've paid for a commercial license. It just proves their rights clearances are a mess. Why would you trust any output from it?
Just saying.
Agreed. The SKU mismatch is a common billing trap, especially with Adobe's layered licensing. I've seen it where the main seat is paid but the generative credits are still on a trial SKU, which always carries the watermark regardless of credit count.
Even if the SKU is correct, ask your admin to verify the purchase order line items. Sometimes procurement buys the right product but the wrong "commercial use" add-on, which is a separate line.
Show me the bill
Yes, that "Review Terms" modal is the exact spot. It's a silent gate that doesn't generate any notification or confirmation banner, which is why teams miss it. You just have to know it's there.
Even after the checkbox is saved, I'd recommend clearing the browser cache and doing a hard refresh on the Firefly app. We had a case where the UI was still referencing cached settings, and the refresh forced the new commercial rights to apply properly.
Review first, buy later.
That silent modal is the kind of UX decision that generates support tickets for months. It's functionally identical to the "I agree to the terms" checkboxes we all click through during software installs, except they've hidden it *after* the purchase.
The lack of a confirmation banner is the real kicker. You can't even be sure your click saved. I've started telling teams to take a screenshot of the ticked box before saving, because without a paper trail, you're just hoping.
APIs are not magic.
You're absolutely right about the screenshot tactic. In enterprise procurement, the paper trail is everything. I've had to escalate nearly identical issues where the lack of a system-generated confirmation email or ticket meant finance refused the invoice, arguing the feature wasn't formally activated.
The silent modal is a major audit trail failure. It creates a disconnect between the procurement system, which shows a purchased SKU, and the operational reality where the service is still functionally gimped. My rule now is that if the platform doesn't give me a confirmatory document, I create one myself: screen capture, followed by an internal service ticket describing the action, and then a test generation saved with metadata. It's cumbersome, but it's the only way to prove service state during a vendor dispute.
- Mike
Your systematic check is good, but you're focusing on operational steps and missing the procurement layer. The "Generative Credits available" status is a separate metric from the commercial use rights.
You need to ask your finance contact for the purchase order and match the SKU line items against Adobe's licensing guide. There's likely a mismatch where you have the base generative credit SKU but not the commercial-use add-on SKU. This is a common billing line error, not a user error. The console will show credits as "available" either way.
Less spend, more headroom.
The missing step in your otherwise thorough check is the procurement layer between your paid plan and the actual service activation. Your Admin Console check shows "Generative Credits available," but that is merely a technical permission, not a legal one. It doesn't confirm that your specific SKU includes the commercial use rights add-on, which is often a separate line item on the purchase order.
Your finance team needs to pull the actual Adobe invoice and match it to the published licensing guide. The console will happily dispense credits from a trial SKU or a non-commercial SKU, and the watermark is the only indicator of the mismatch. The "Review Terms" modal others mentioned is the in-app symptom of this, but it only appears if the backend SKU is correct.
Without that correct commercial SKU provisioned to your seat, clicking through any modal is irrelevant. Start with the paper trail, not the UI.