FLUX AI Image Detector
FLUX AI image detector test results: FLUX.2 was the hardest family for both engines, its signer isn't on the trust lists, and a screenshot slipped.
Check an image
Drop an image here, paste a screenshot (Ctrl+V), orChoose a photo or screenshot
JPG, PNG, WebP, GIF or HEIC up to 25 MB · 3 free checks a day · We don’t keep your image
No image handy? Try a sample:
Tick the box to continue. Your image is still here.
Your recent checks (only on this device)
Tested on 100 images: 98 judged correctly, 1 answered “Can't tell”, 1 judged wrong. 0 of 50 real photos flagged as AI. How we tested
- Images tested
- 9: 7 original files and 2 screenshots
- Models tested
- FLUX.2 [pro], FLUX.2 [max]
- Original files with AI Content Credentials
- 5 of 7
- Made by us for this test
- 5 of 5 with AI Content Credentials
- From public datasets
- 0 of 2 with AI Content Credentials
- Credential signers
- Black Forest Labs Inc.
- Tools named in the credentials
- Black Forest Labs API
- Signer trust
- not on the trust lists we check
- Screenshots that kept Content Credentials
- 0 of 2
- Original files with an unsigned AI label in metadata
- 0 of 7
- Settled by trusted Content Credentials, no model call
- 0 of 9
- Sent to the detection model
- 9 of 9, 5 of them with a label anyone can write
- Our checker's answers (Sightengine: AI at 0.8 or above, real photo at 0.2 or below)
- 8 right, 0 Can't tell, 1 wrong
- Sightengine, AI at 0.5 or higher
- 8/9
- Sightengine at the checker's 0.8 cut-off
- 8/9
- Lowest Sightengine score
- 0.18
- Hive, AI at 0.9 or higher
- 6/9
- Whole test set
- 100 images: 50 real photos and 50 AI images
- Tested on
- 2026-10-13
- Sightengine on the other 5 families (AI at 0.5 or higher)
- 41/41
- Our checker's wrong answers on AI images, whole test
- 1 of 50, and it was this FLUX screenshot
How the FLUX AI image detector handles a FLUX picture
Add the picture to the FLUX AI image detector above. Images from Black Forest Labs' API carry Content Credentials signed by Black Forest Labs Inc., but that signer isn't on the C2PA trust lists our checker uses. So the checker treats the credential as a label it can't verify, lists it in the reasons and sends the picture to a detection model, which uses one of your free checks.
The model is Sightengine, with Hive as a backup if Sightengine fails, the same engines as the AI image detector on our home page. FLUX images made with open-weight models on someone's own computer carry no Black Forest Labs credential at all, so for those the model is the only signal from the start.
FLUX AI image detector results: the hardest family we tested
FLUX was the hardest family for both engines in our test. Sightengine caught 8 of 9 FLUX images and Hive 6 of 9, while Sightengine caught every image from the other five families. The checker got 8 right and 1 wrong, and that was its only wrong answer on any AI image in the whole test.
The miss was a screenshot. Sightengine scored it 0.18, below the checker's 0.2 line, so the checker called it Likely a real photo. The original file of the same picture was caught, as were the other screenshot and all 7 original files, FLUX.2 [pro] and FLUX.2 [max] alike. One miss in 9 isn't a rate you can rely on in either direction, but it is why we call FLUX the family to be most careful with.
Why signed FLUX credentials don't settle the answer
Black Forest Labs signs its API images, and all 5 originals we generated through its API (via a reseller that relays requests to it) carried credentials saying they were AI-generated. The checker still doesn't let them settle the answer, because the signer isn't on the C2PA trust lists we check, and a credential from an unlisted signer proves less than it seems: anyone can sign a record like that with their own certificate.
Trust lists are how a checker knows a signer is who it claims to be. The C2PA launched its official trust list in mid-2025 and froze the older interim list on January 1, 2026; our checker accepts signers on either. Black Forest Labs' own help page says verification depends on the verifier's trust list, and that an untrusted-signer result means the verifier doesn't recognize the signer yet. In our test this cost nothing in accuracy, because the model called all 5 signed originals AI. If the signer reaches a trust list we use, files like these could be settled in your browser instead.
FLUX images without any credentials
Two kinds of FLUX image reach the FLUX AI image detector with no credential at all: copies that lost it, and images from open-weight FLUX models run outside Black Forest Labs' service. For both, the detection model is the only signal.
The 2 FLUX.2 [pro] images we took from a public dataset had no credentials, and neither of our 2 screenshots kept them. Black Forest Labs says images made with self-hosted or open-weight models, such as FLUX.1 [dev] and FLUX.1 [schnell], are outside its signing service. We didn't test any FLUX.1 images or local runs, so we can't tell you how the engines do on them.
What to do with a FLUX AI image detector result
Because FLUX was the hardest family, give a FLUX picture a second look when the FLUX AI image detector surprises you. A Likely AI-generated answer was right every time in our test; the one miss went the other way, a FLUX screenshot called real.
- Get the original file if you can. Our only miss was a screenshot, and screenshots also lose the credentials.
- Read the reasons. If the credentials name Black Forest Labs API, that is a label worth noting, even though we can't verify the signer.
- Don't treat Likely a real photo as clearance on a picture that looks too polished or comes from an account that posts AI work. Use the visual checklist and look for the first post.
- Compare generators. The Midjourney and Stable Diffusion pages show families that were easier to catch, and the accuracy report has every result.
Frequently asked questions
Why was FLUX the hardest generator for the FLUX AI image detector?
We can't say why; we can only report what happened. Both engines missed more FLUX images than any other family: Sightengine 1 of 9 and Hive 3 of 9. With 9 images, that is a warning sign, not a precise rate.
Does the checker trust Black Forest Labs credentials?
It reads them and shows them, but it doesn't let them decide, because Black Forest Labs Inc. isn't on the C2PA trust lists we check. The detection model decides, and the credential is listed as a label we can't verify.
Was the wrong answer an original FLUX file?
No. It was a screenshot of a FLUX.2 [max] image, which Sightengine scored 0.18. The original file of the same picture was caught.
Does the FLUX AI image detector work on FLUX.1 images?
We didn't test FLUX.1 models or local runs, only FLUX.2 [pro] and FLUX.2 [max]. Sightengine lists Flux among the generators it aims to support, but that is the vendor's claim, not our measurement.