Check the file’s Content Credentials. Firefly output is not the only signed file you will meet: our Google Photos how this was made guide shows how the same record looks inside the Google Photos app. Adobe Firefly signs every image it generates, so open the original file in the Content Credentials verify tool and read the record it returns. If the record names Adobe Firefly as the maker, the image was made with Firefly. If no record exists, look for other evidence, because a missing record proves nothing.
This guide shows you how to tell if an image was made with Adobe Firefly, step by step, using the same check Adobe built for the job. You will learn what Firefly writes into a file, how to read that record in under a minute, what a real Firefly file looks like when you open it up, and what to do when the record is missing. Adobe is the last major image generator with no dedicated guide on this site, and its case is different from the others: Firefly signs its output by default, so the file itself usually gives you the answer. The hard part is knowing where to look, and knowing what a blank result does and does not mean.
Adobe Firefly is Adobe’s family of generative AI models for making images, video and design assets from text prompts, built into the Firefly web app and into Photoshop. Content Credentials are a signed, tamper-evident record attached to a file under the open C2PA standard, listing who made the file, which tools were used, and whether AI was involved. Think of it as a nutrition label for a picture: it does not judge the image, it lists what went into it.
What does Adobe Firefly write into an image file?
The short answer is that Firefly signs its own work automatically, and you do not need the maker’s help to see it. Adobe says it automatically applies Content Credentials to assets where 100 percent of the pixels are generated with Adobe Firefly, such as images made with Text to Image. That page on Adobe’s own help site was last updated on 25 August 2026, and it is the primary source for everything in this section.
The record Firefly attaches is deliberately short. It carries non-personal information only, unless the maker chose to add more through Photoshop, Lightroom or Adobe’s Content Authenticity app. Here is what is always in it.
| Field in the record | What it tells you |
|---|---|
| Issuer | Adobe Inc., the organisation that issued the credential. |
| Date | The date the credential was issued, which is the date the image was generated. |
| App or device used | The Adobe software or hardware that generated the asset. |
| AI tool used | The Adobe generative AI tool used, such as Firefly Text to Image. |
| Actions | The general editing and processing actions taken. For Firefly output this is usually a single Created action. |
| Output thumbnail | A small visual thumbnail of the output, shown only for assets made with Text to Image on the Firefly website. |
Two things about that list matter for your check. First, the record names the tool, not the person. Firefly does not add the maker’s name unless they opted in, so a Firefly record will not tell you who typed the prompt. Second, the record lives in two places: it is attached to the file itself, and it may also be stored in Adobe’s public Content Credentials cloud. The cloud copy matters because it can survive when the file copy does not, which we come back to below.
One more point before you start checking. Firefly is not only a standalone web app. Its models also power features inside Photoshop, such as Generative Fill, and Adobe says Firefly-powered features in Photoshop automatically attach Content Credentials to the content they produce. A Firefly check therefore has two shapes: a picture made entirely by Firefly, and a real photo with a Firefly-made patch inside it. This article covers both, in that order.
How do you check an image for Firefly Content Credentials?
Use the official verify tool, on the original file, and read the record line by line. The check takes about a minute when the file is in your hands, and it needs no account, no sign-in and no payment. Here are the steps.
- Get the original file, not a copy of it. Download the image from where it was first posted, or ask the sender for the file itself. A screenshot, a re-saved copy or a version pulled from a social feed may have lost the record already.
- Open the verify tool. Go to the Content Credentials verify tool at verify.contentauthenticity.org. It runs in the browser on desktop and on mobile, and it accepts JPEG, PNG, WebP, AVIF, HEIC and other common formats.
- Upload the file. Choose the file from your device or drag it onto the page. The tool reads the file in your browser and does not store the image you check.
- Read the panel it returns. If a valid record is present, the panel shows who signed it, when it was signed, which tools were used, and the edit history, including any AI-generation flag. If the file has no record, the tool says plainly that no Content Credentials were found.
- Check the generator line first. A Firefly-made image lists Adobe Firefly as the AI tool, with a Created action and Adobe Inc. as the issuer. That line is the answer to your question.
For the same workflow applied to any photo, not just a Firefly one, see our guide to checking Content Credentials on a photo.
If the panel shows a record, save a screenshot of it before you go further, because you may want the date and the tool name as evidence later. If the panel shows nothing, do not stop there: a missing record is the start of the next check, not a verdict. The rest of this guide explains why, and what to check next.
There is also a second way to read the same record without the verify tool. Adobe’s Content Authenticity site has an Inspect tool that can look up credentials stored in Adobe’s Content Credentials cloud, which can recover a record even from a screenshot, but only if the maker published the credentials to the cloud in the first place. The file check above is the one to try first, because it works on the file in front of you and needs nothing from the maker.
What did the check find on a real Firefly image?
This is the worked example, and it was done on 14 November 2026 on a real image from Adobe’s own gallery. The Firefly gallery page that older guides link to no longer exists: the /inspire address now returns a page-not-found error, and the gallery has moved to an “Inspiration from others” section on the Firefly home page. There I found a picture of iridescent holographic headphones floating against a grey gradient background, credited to Liz Hayes, listed as Type: Image and Model: Firefly Image 5, with its full prompt visible on the detail page. I downloaded the full-size file from Adobe’s own content server. It arrived as a PNG, 1024 by 1024 pixels, 1,025,247 bytes.
The first thing I did was open the file itself and look for the provenance record, before trusting any website to read it for me. A PNG stores its data in chunks, and a file carrying C2PA credentials has a chunk called caBX. This file has one, 84,798 bytes long, holding a complete C2PA manifest. Reading the manifest gave the following, exactly as written in the file.
| What I checked | What the file said |
|---|---|
| Provenance chunk | caBX chunk present, 84,798 bytes, containing a signed C2PA manifest. |
| Action recorded | c2pa.created, dated 9 April 2026 at 21:48:05 UTC. |
| Software agent | Adobe Firefly. |
| Claim generator | Adobe Firefly, recorded with the C2PA reference software version. |
| Signer | Adobe Product Services G4, under Adobe Trust Services, with a DigiCert certificate chain and a trusted timestamp. |
| Thumbnail | A claim thumbnail is embedded in the manifest, so the record can be matched to the picture it describes. |
That is a clean, unambiguous result: the file says it was created by Adobe Firefly on 9 April 2026, and the signature chain runs back to Adobe. The picture itself backs the record up in a softer way. The headphones are transparent and iridescent, floating in mid-air with small red and wooden shapes scattered around them, lit by a perfect studio light that no real product shoot would produce. None of that proves anything on its own, and you should never call an image AI-made from a floating object alone. But when the pixels look generated and the signed record names Firefly, the two pieces of evidence agree, and that is as settled as this kind of check gets.
Honesty requires a note about the verify tool itself. When I tried to run this same file through the official verify tool on 14 November 2026, the tool failed: the file attached, the page showed “Loading” briefly, then a generic red message said “Something went wrong” and the page returned to the empty upload form. It failed three times, including once after a fresh reload, and it failed identically on an ordinary photograph with no credentials at all, which points to the tool’s inspection pipeline rather than to my file. The URL route failed too: the inspect-by-URL address rewrites itself and never starts an inspection. So I verified the same file’s manifest directly, by reading the record out of the file, instead of quoting a verify panel I never saw. If you try the tool and it works for you, use it: it is the intended route. If it fails the same way, the file-level read above is the fallback, and a missing panel is a statement about the tool that day, not about your image.
For contrast, I ran the same file-level check on an ordinary photograph: a real photo of a kitchen food-photography setup, a camera on a flexible tripod beside a bowl of strawberries, taken from Flickr under a Creative Commons licence. It contains no C2PA data at all, and no mention of Adobe anywhere in the file. That is what a normal camera photo looks like to this check: silence. Silence is also what a stripped Firefly file looks like, which is why the next sections matter.
How to tell if an image was made with Adobe Firefly when the file has no record?
Start by assuming nothing, then work through the other evidence in order. A missing record has three common causes, and only one of them means the image is a real photo. The file may have been re-saved, resized or screenshotted, which strips the record. It may have been posted through a platform that strips metadata on upload. Or it may genuinely have no record because no tool ever signed it. Your job is to separate the first two from the third, and the steps below do that.
First, get the best copy you can. Ask the sender for the original file, or download it from the earliest place it appeared. Reverse image search is the fastest way to find that earliest copy: search the picture with Google Lens or TinEye and look for the oldest or highest-resolution version, then check that copy instead. Our how to reverse image search guide walks through the steps. If the earliest copy you can find still has no record, that is a real result, not a failure of method.
Second, read the picture itself, but treat what you see as a hint, not a verdict. Firefly images often share a look: impossibly clean studio lighting, floating objects, iridescent or glass-like surfaces, tiny background objects that make no sense, and text that dissolves into shapes. The headphones in the worked example show three of those at once. But Firefly has improved fast, and a careful prompt can produce an image with none of them, so a clean-looking picture proves nothing either way.
Third, run the picture through an AI image detector as a second opinion, and read the score the way the tool intends. Our how to tell if an image is AI generated guide explains how detectors score a picture and why a mid-range score means “look closer”, not “fake”. A detector cannot name Firefly specifically, and no detector is certain, so use it to support the record check, never to replace it.
If all three checks come back empty, say so plainly: there is no evidence this image was made with Firefly, and no evidence it was not. That sentence is the honest answer, and it is far more useful than a guess dressed up as a verdict.
What if the photo is real but part of it was made with Generative Fill?
Then the record tells a two-part story, and you need to read both parts. Photoshop’s Generative Fill lets you select a region of a real photograph and have Firefly invent what goes there: remove an object, extend a background, add a detail that was never in the scene. The result is part camera and part model, and its Content Credentials record says so. Adobe states that Photoshop automatically attaches Content Credentials to images made with Generative Fill and Generative Expand when they are exported as PNG or JPG, or saved with Save As.
Open such a file in the verify tool and the panel reads differently from a fully generated image. Instead of a single Created action, you will see the original photograph listed as an ingredient, plus an AI action for the filled region. The record is honest about the split: most of the pixels are genuine, one region is model-made. That is also why a detector can be confusing here. A whole-image detector expects generation fingerprints across the frame, but only the filled patch carries them, diluted by genuine photo around it. The detector may return a middle score, and the middle score is the tool being cautious, not broken.
For the manual side of this question, the signs of hand retouching, clone-stamp repeats, warped lines and mismatched grain, live in our guide to telling if a photo has been photoshopped, and this article does not repeat them. The boundary is simple: if a person moved pixels by hand, that guide is the one to use; if Firefly invented pixels, the record check above is the one to use. Many real pictures have both, and then you need both guides.
One trap is worth knowing. People who use Generative Fill in Photoshop report that a generative step, once used and then undone, can still be declared on export. The record is technically accurate, some pixels were generated at some point, but it can make a photo look AI-edited when the final image contains no generated pixels at all. If you are the person checking, treat a Generative Fill line as “AI touched this file”, not “AI is visible in this picture”. If you are the person editing, check the Content Credentials panel in Photoshop before you export, because that panel previews exactly what a checker will see.
What survives a re-save, a resize or a screenshot?
Almost nothing survives a re-save, and that is the single most important fact in this whole guide. Content Credentials are metadata attached to a specific file. Change the file, and you risk losing them. The table below states what happens to the Firefly record in each common case.
| What happened to the file | Does the Firefly record survive? |
|---|---|
| Downloaded as published from Firefly or Adobe Stock | Yes. The original file carries the full manifest, as in the worked example. |
| Re-saved as a JPEG, resized, or re-encoded as a PNG | No. A test by the team behind a rival detector found that each of those steps removed the manifest entirely from their C2PA reference files. |
| Screenshotted on a phone or computer | No. A screenshot is a brand-new file of your screen, and it carries none of the original file’s record. |
| Uploaded to a social feed or messaging app | Usually no. Most platforms strip metadata and re-encode the image on upload. |
| Published to Adobe’s Content Credentials cloud | The cloud copy can survive. Adobe’s Inspect tool can recover credentials stored in the cloud, even from a screenshot, if the maker published them there. |
That table explains most of the confusing results people report. A Firefly image that has been through Instagram, WhatsApp or a screenshot will usually show no record, and the absence proves nothing about where it came from. It also explains why the first step of the check is always “get the original file”. Every copy you accept after the original is a copy that may have been cleaned of exactly the evidence you need.
The cloud row deserves a caution. Recovery through Adobe’s cloud only works when the maker published the credentials there in the first place. Firefly attaches the record to the file automatically, but publishing it to the cloud is a separate choice the maker makes in Photoshop, Lightroom or the Content Authenticity app. You cannot assume a cloud copy exists, and you cannot create one for someone else’s image. If Inspect finds nothing, you are back to the file check and the other evidence, not to a verdict.
What can you tell from looking at the picture alone?
Less than most guides promise, but more than nothing. Use the visual check only after the record check, and only as supporting evidence. The signs below are the ones that show up most often in Firefly output, and each of them has a real-photo explanation too, so none of them settles the question alone.
- Floating objects. Firefly loves a product floating in empty space with a soft shadow underneath. Real product shots use stands, strings or supports, and the supports are usually visible if you zoom in. A floating object with no support and a perfect shadow is a hint, not proof.
- Glass, chrome and iridescence. Transparent and rainbow surfaces are easy for Firefly and hard for a camera to light cleanly. The headphone picture leans on this heavily. But a skilled photographer with a light tent can produce the same look, so treat it as a nudge.
- Background clutter that means nothing. Small shapes, pebbles, pins or fragments scattered around the subject, with no purpose and no pattern, are a common Firefly habit. The headphone picture has red blocks and a wooden shape floating at random. Real stylists place props with intent.
- Text that almost says something. Letters on packaging, signs or clothing that dissolve into marks are still one of the most reliable visual tells, because models paint the shape of text rather than writing words. Zoom in on any text before you decide anything.
- Hands, ears and edges. Fingers that bend wrong, ears that merge into hair, and edges where a subject meets the background too cleanly are all worth a close look at full size. Firefly has improved here, so a clean result means little, but a bad one means a lot.
Run a reverse image search alongside the visual check. If the same picture appears on a stock library, a Firefly gallery page or a prompt-sharing site, the listing will often say how it was made. If it appears nowhere, that tells you nothing either way: a new generation has had no time to be indexed. The visual check is a way to decide whether the record check is worth pursuing harder, not a substitute for it.
What mistakes waste the check?
Most failed Firefly checks fail the same few ways, and all of them are avoidable. Check your own method against this list before you conclude anything.
- Checking a screenshot instead of the file. A screenshot has no record to find. Always work from the original file, and say so in your notes if you could not get it.
- Trusting a detector score alone. A detector estimates, and it cannot name Firefly. Use it as a second opinion behind the record check, never as the verdict.
- Treating “no credentials found” as “real photo”. A missing record means the file carries no record. It does not mean a camera took the picture. Re-saves, screenshots and social uploads all erase the record.
- Trusting a badge baked into the picture. Anyone can paint a “Made with Firefly” label or a small CR logo onto an image with any editor. A real credential lives in the file’s signed record, not in its pixels. If the badge is part of the picture, ignore it and check the file.
- Forgetting the cloud copy. If the file check is empty, try Adobe’s Inspect tool before giving up. A cloud-published record can be recovered from a screenshot, and it is the one route that survives a file being stripped.
- Checking the wrong file. Galleries and social feeds serve compressed previews. Download the full-size original from the source, and check that, not the thumbnail your browser showed you.
If you want to add credentials to your own work so other people can check it the same way, our guide to adding Content Credentials to your photos explains the settings in Photoshop and Lightroom, including what to include and what to leave out. And if you want the full background on the standard itself, Adobe’s own Content Credentials in Adobe Firefly help page is the source this article relied on most, and it is worth reading in full before you rely on a check for anything serious.
FAQs
Can I check a Firefly image from a screenshot?
No, not from a screenshot. A screenshot is a new picture of your screen and carries none of the original file’s Content Credentials, so the verify tool will find nothing. Ask the sender for the original file, or search for the earliest published copy. If the maker published the credentials to Adobe’s cloud, the Inspect tool may still recover them.
Does a missing Content Credentials record mean the image is a real photo?
No. A missing record only means this copy of the file carries no record. Re-saving, resizing, screenshotting and social media uploads all strip Content Credentials, so a genuine Firefly image that has passed through any of those steps will show nothing. Treat a blank result as no evidence either way, and check the original file before deciding.
Can someone fake Firefly Content Credentials?
Not convincingly. Content Credentials are cryptographically signed, so editing the record breaks the signature and the verify tool will flag it. What a person can fake is the appearance: they can paint a Firefly label or a small badge onto any picture. Always check the signed record in the file, never a badge drawn in the image.
Does Photoshop Generative Fill mark the whole photo as AI?
No. Generative Fill records the original photo as an ingredient and adds an AI action for the filled region only. The verify panel reads differently from a fully generated image, and a detector may return a middle score because only part of the frame was generated. Read the ingredient list, not just the headline result.
Will the verify tool work on my phone?
Yes. The verify tool runs in a mobile browser and accepts uploads from your phone, including JPEG, PNG, WebP and HEIC files. The steps are the same: open the tool, upload the original file, and read the panel. Save the file to your phone first rather than checking a screenshot, because a screenshot carries no record to find.
What should I do if I need proof for a client or a dispute?
Keep the original file untouched, save a screenshot of the verify panel, and note the date you ran the check. If the panel is empty, record that too. A signed record naming Adobe Firefly is strong evidence of origin, but it says nothing about who typed the prompt, so keep your own notes on where the image came from.







