Skip to content
checkaifree
AI image detector

Flux.2 image checker

Check if an image is AI-generated when the claim is Flux.2. The model card draws a hard line between the hosted Pro API and the open weights. This page follows that line.

Checking scope
Files
JPEG, PNG, WebP · up to 10 MB
Model check
General AI-image estimate, when available
On this page
Flux.2 API credentials or CLI EXIF
Signatures
Not verified by this site
Specimen plateAwaiting image

Drop an image here

or choose a file

Metadata demos (controlled fields):
JPEG · PNG · WebPUp to 10 MBNo sign-up
How the file travels

Two Flux.2 files are not the same file

The FLUX.2 model card says the API for FLUX.2 Pro applies signed C2PA metadata to mark that the image was produced with their model. It also says the open-weight inference code implements an example of pixel-layer watermarking and links the C2PA standard. Those are different mechanisms, and the example watermark is not the same thing as a manifest.

The published command-line tool writes EXIF Software as “AI generated;flux2” and Make as “Black Forest Labs”. In that CLI the example watermark call is not enabled. ComfyUI, diffusers and third-party hosts will not write that EXIF pair unless they copied it. They may write a workflow chunk, their own C2PA, or nothing.

Keep the original bytes if you care about the API credential. A JPEG re-save in an editor, or a chat app, can strip both EXIF and a manifest. Our checker can show source text it finds and can run a general model score. It will not confirm the signature, the model version string, or that a watermark example was present.

The drawings are original illustrations of file paths. They are not outputs from Flux.2.

Diagram contrasting a Flux.2 Pro API file and an open-weight CLI filePro APIDev CLIOther hosts
Pro API: signed credentials in the original bytes. Open-weight CLI: two EXIF fields, watermark example off.
Flux.2 metadata layers for API credentials versus CLI EXIFAPI — signed manifestCLI — EXIF Software and MakeComfyUI — workflow text or nothing
Read the layer that this export path actually writes. Don’t borrow the other path’s guarantee.
What the Flux.2 checker will reportReportsDoes notVisible textGeneral scoreVerify signatureName the host
A general score never becomes a Flux.2 label.
Metadata and credentials

Metadata and Content Credentials

BFL’s C2PA article describes the hosted signing flow: a hash of the pixels, a manifest, their certificate, embedded in the file. The Flux.2 Pro API is in that hosted class. The dev open weights are in the class they tell you not to assume. A self-hosted Flux.2 file without the CLI’s EXIF and without a manifest is an ordinary outcome, not a photograph.

If Software says “AI generated;flux2”, that is a strong editable clue that this CLI saved the file. It is not a signature. Change one byte of EXIF and the clue is gone or forged. We do not treat EXIF Make as a camera, and we do not treat it as proof when it names a lab.

This site can notice source text in the first part of a file. It does not verify C2PA signatures, asset bindings or certificate trust, and it has no SynthID decoder.

Look twice, then don’t conclude

Visual tells, treated cautiously

Flux.2 marketing stresses resolution and prompt adherence. Eye-balling either one will mislead you.

Large, clean frames

Default sizes in the CLI are wide and detailed. People also upscale photographs to the same dimensions.

Text in the scene

The model is prompted to paint words. Other current models do this. Misspelled text is not a Flux.2 test.

No SynthID

SynthID is Google’s system. It is not part of the Flux.2 release. Don’t look for it here.

How this check handles the file

Source clues are checked in your browser first. When needed, file-header data and a smaller image copy may be sent to our backend and detection provider. Model copies have embedded metadata removed. Image URLs are retrieved by our server; see the privacy policy for processing and provider retention. Privacy details

Sources for the generator notes

Frequently Asked Questions

Questions about Flux.2.

The answers below are about this generator’s files, not a promise to name the model.

How do I check a Flux.2 image?

Start with the original file. API bytes may contain the C2PA manifest Black Forest Labs describes. The official CLI may contain EXIF Software “AI generated;flux2”. A screenshot usually contains neither. The optional score stays a general AI-image estimate.

Is the open-weight watermark on?

The model card calls the pixel watermark an example. In the published CLI the call is not enabled. Assume a local Flux.2 image has no invisible watermark unless the person who ran it turned one on.

Does a missing manifest mean it is not Flux.2?

No. Open-weight and re-encoded files are expected to lack the API manifest. Missing credentials are not a camera result.

Is the check free?

No account is required. Provider limits apply.

Related reading

These notes explain what a file can and cannot show. They do not name Flux.2 from the pixels.

Explore Other Generators

Also inspect other generative models

All checking guides
Image review scenarios

Reviewing profile photos or art entries?

Review LinkedIn candidate photos or competition artwork with context, and read our method and limitations.

Method and limits