Skip to content
checkaifree
AI image detector

Flux image checker

Check if an image is AI-generated when it might be Flux. A local Flux.1 file, a Flux 1.1 Pro API image and a Flux.2 file do not carry the same clues. Flux.2 has its own page.

Checking scope
Files
JPEG, PNG, WebP · up to 10 MB
Model check
General AI-image estimate, when available
On this page
Flux family, including hosted 1.1 Pro
Signatures
Not verified by this site
Specimen plateAwaiting image

Drop an image here

choose a file

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

The export path decides the clues

Flux spread through local tools first. ComfyUI, Forge, and diffusers users often have a PNG that contains a workflow or a parameter chunk, or a JPEG that contains nothing. Those fields name whatever nodes the user saved. They can say “flux” and still be edited. They can be absent because the user turned metadata off.

Black Forest Labs says its hosted API, playground and integrations it controls embed C2PA Content Credentials after inference, for FLUX endpoints that return a final image. The open weights are the exception they document: running Flux.1 dev or schnell yourself does not guarantee those credentials. A file from fal, Replicate or another host follows that host’s pipeline, not automatically the BFL one.

Flux 1.1 Pro was a hosted model, not the open weights people run as Flux.1 dev or schnell. You got it from Black Forest Labs or from a host that called that API. BFL says hosted endpoints that return a final image get Content Credentials, and that you should keep the original response bytes. A gallery that recompresses the result can drop the manifest even though the picture was 1.1 Pro. We have not fetched a fresh 1.1 Pro sample; that follows their pipeline description, not a private corpus. A filename that says “Flux 1.1 Pro” is not inside the image. Flux.2 is the later family and has its own page. A visual similarity does not choose between 1.1 Pro, local Flux.1 and Flux.2.

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

Diagram of three Flux export paths: BFL API, ComfyUI PNG, and JPEGBFL APIComfyUI PNGPlain JPEG
Same family name, three evidence situations. Identify the path before you interpret a missing field.
Flux clue layers: C2PA on hosted output, workflow text locally, pixels either wayHosted C2PA — original bytesLocal PNG text — editablePixels — general score
Hosted credentials and local workflow text are different clues. We verify neither as a signature.
Flux family page covering hosted 1.1 Pro and local files, with Flux.2 on its own pageThis pageOther page1.1 Pro APILocal FluxFlux.2 CLIStyle as an ID
1.1 Pro stays on this page as a hosted-API case. Flux.2 has a separate export story.
Metadata and credentials

Metadata and Content Credentials

BFL’s help article describes a signed manifest with an AI-generation assertion, the claim generator, a created action, model name and version, and a binding to the image bytes. They also say re-encoding or stripping metadata can remove it, and that you should keep the original response bytes. This site does not verify that signature or that binding. 1.1 Pro outputs were typically the API’s image, often without an Automatic1111 parameter chunk. If you see a ComfyUI workflow, you are probably looking at a local Flux path, not a hosted 1.1 Pro response.

Local PNGs are a different system: tEXt-style workflow and prompt chunks, which the Stable Diffusion guide’s reader can show when the file is a PNG. Flux files that went through the same ComfyUI habits show up there. JPEG exports of the same render usually will not.

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.

Official check

How Black Forest Labs says to check a hosted file

BFL’s C2PA article says credentials are attached for the BFL API, the developer playground, and hosted integrations where BFL controls the output pipeline, on FLUX endpoints that return a final image. After inference they hash the pixels, sign a manifest with their certificate, and embed it. The manifest records an AI-generation assertion, the claim generator, a created action, and the model name and version. It does not record the prompt or the account.

They tell you to keep the original response bytes and open them in a C2PA validator. A validator has to check the signature, the binding to these pixels, and the trust list. This site does not. Self-hosted Flux.1 dev and schnell are outside that signing setup. A third-party host is not automatically the BFL pipeline. There is no Flux look that replaces that check.

Look twice, then don’t conclude

Visual tells, treated cautiously

Flux became a house style people claim to recognize. The style is not a checkpoint id, and it does not separate 1.1 Pro from Flux.2.

Sharp, dense detail

Fine texture is why people pick Flux. Phones and other models produce it too.

Prompt-perfect anatomy

Later Flux checkpoints fail less obviously. A good hand is not a camera, and a bad hand is not proof of Flux or of 1.1 Pro.

Host watermarks

Some websites stamp their own logo on a preview. That mark identifies the website, not the checkpoint, and it can be cropped.

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.

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

Is this image Flux?

Only the export can say so, and only as a claim. A BFL-hosted original may contain Content Credentials. A local PNG may contain a workflow name. A re-saved JPEG may contain neither. The optional model score does not name a Flux checkpoint.

Does every Flux image have C2PA?

No. Black Forest Labs documents credentials for pipelines it controls. Open weights run elsewhere do not inherit that guarantee. Third-party hosts vary. Flux 1.1 Pro was a hosted model, so the credential story is the hosted one, and only if you still have the original bytes.

How is Flux 1.1 Pro different from Flux.2?

1.1 Pro is the earlier hosted model and is covered here. Flux.2 is the later family: a Pro API credential story plus an open-weight CLI that writes EXIF Software “AI generated;flux2”. A visual similarity does not choose between them.

Can you recover a ComfyUI workflow?

If the PNG still has the text chunks, the reader on the Stable Diffusion guide can show them. It cannot invent a workflow that was not saved. It does not execute the workflow. A hosted 1.1 Pro JPEG usually will not have that chunk.

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