Inspiring

Answered

Content credentials flagging content that I create, preventing me from using it for generating video.

Forum|Forum|3 months ago
April 16, 2026
20 replies
405 views

Unable to use AI generated imagery for the start frame in GenAI video. When uploading an image created in Firefly or another application, this warning pops up: “Upload another image. This image has Content Credentials that indicate it can't be used with generative Al features.” This also occurs using images from Generation History or previously uploaded content (“Your stuff” folder). This also occurs when attempting to use photos as a start frame.

This issue persists across browsers (Safari, Chrome) and across accounts (personal, company), and across Firefly modules, with the exception of Firefly Boards.

Correct answer RenderSlop2001

@Kartika Rawat I spoke with our IT department and it appears the Content Credential API call may be blocked by our security software - which explains why image to video works in firefly boards (drag and drop from desktop) and not in the generate module (where the upload function triggers the call). I’m working to get an exception for Firefly and will report my findings.

S

Sugiyama

Participant

Any solution for this? I have security white-listed Firefly and Adobe Generative AI but still getting the same message and unable to use my own images.

Tarun Saini

Community Manager

Hi @Sugiyama,

Thanks for reporting this. The message indicates that the uploaded image contains Content Credentials that restrict its use with certain generative AI features in Firefly.

Could you let us know whether the issue occurs with all images or just this specific file? In the meantime, please try exporting the image as a new JPG or PNG, or test with a different image to see if the behaviour persists.

If that doesn't help, please share a screen recording of the issue to investigate further.

Regards,

Tarun

S

Sugiyama

Participant

hi Tarun,

Thank you for your response. The issue occurs with all images and I’ve tried the copying and exporting images as well. I’ve seen the other post about whitelisting API so I’m forwarding that to my IT department to review.

Attached is not a video but the msg I get when trying to upload an image.

12Mellon

Participant

I am a professional director using Nano Banana 2 assets as base frames for generative video production. This workflow has worked perfectly for months. Now, I am suddenly blocked by the error: "This image has Content Credentials that indicate it can't be used with generative AI features." This is a major bottleneck for my current production. Is this a bug or a deliberate policy to block external C2PA metadata? Manually stripping metadata for every frame is not a viable professional solution.

RenderSlop2001Author

Inspiring

-

Rafiq07

Participant

The exact same issue!

Hajar Toutsi

Community Manager

Hi Rafiq07,
Thank you for letting us know.

Could you please try the workaround that our expert @Oh.N8 shared earlier in this thread and let us know if it resolves the issue?

If not, please upload an image where the issue persists and share the details of how you were using it. We’d love to look into this further.

Hajar

S

Sugiyama

Participant

Here’s a simple image that I exported from Illustrator. I tried to upload this image to animate it but Firefly won’t let me.

O

Oh.N8

Hey @RenderSlop2001

I find Firefly Boards works great for images that you have downloaded and cleaned up. Bring those images into Firefly Boards. Firefly Boards is very powerful.

Here’s a short video for a possible workaround when you generate and want to use that image w/o making any adjustments.

Cheers

Nate

RenderSlop2001Author

Inspiring

I don’t know what’s more frustrating about this copy-paste reply, the fact that you are using a community forum to self promote this remedial video, or that in spite of my very clear description of the software bug, you fail to acknowledge that content credential flagging is still broken in the primary video-generation module in the Adobe Firefly dashboard.

This is no way the “correct” answer to this issue. Acknowledging the bug and clarifying further action, e.g forwarding this to engineering or dev team, would perhaps be the “correct” answer. But marking this as correct in an attempt to close this thread with tyour video as the solution is lazy at best and disingenuous at worst.

Kartika Rawat

Community Manager

Hi RenderSlop2001!

I’m sorry for the frustration. Does this happen with a specific image? If so, could you please share it with us so we can test on our end? We haven’t been able to reproduce the issue so far, and having the image will help us investigate further.

Thanks,

Kartika

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.