About ComfyDetective

A free ComfyUI workflow inspector that runs in your browser. Drop in a workflow and find out exactly what it needs before you try to run it.

The problem it solves

ComfyUI workflows get shared as .json files, or as images with the workflow baked into their metadata. Either way, opening one tells you almost nothing until you load it into ComfyUI — and if it depends on custom node packs you do not have installed, it does not load at all. You get a wall of red boxes and a "missing node types" error listing class names that mean nothing on their own.

ComfyDetective reads the file and answers the questions you actually have before you install anything or hunt through Reddit threads for the right repository.

What it tells you

• Required models — checkpoints, LoRAs, VAEs, ControlNets, IPAdapters, CLIP and upscale models, organised by the folder they belong in, with links to find them.
• Required custom node packs — which packs the workflow depends on and where to install each from, so the "missing node types" error becomes a shopping list.
• Prompts and settings — positive and negative prompts, seed, sampler, scheduler, CFG scale, step count, denoise, and output resolution.
• Pipeline shape — whether it is text-to-image, image-to-image, inpainting, ControlNet-driven, video, or a multi-stage combination.
• The node graph — an interactive map of the workflow you can pan, zoom and click through without opening ComfyUI.
• A model checklist — everything you need to download, with progress as you tick items off.

Supported files

Anything ComfyUI writes workflow metadata into:

• JSON — both the saved workflow format and the API prompt format
• Images — PNG, WebP, JPEG, AVIF, TIFF, BMP, GIF
• Video — MP4
• Audio — FLAC, MP3, WAV, OGG
• Latents — .latent files

Who it is for

• People who downloaded a workflow from Civitai, OpenArt, Reddit or Discord and want to know what it needs before committing to it.
• People reverse-engineering an image they liked, to see the prompt, model and settings behind it.
• Workflow authors checking what their own workflow depends on before sharing it, so other people can actually run it.
• Anyone comparing two versions of a workflow to see what actually changed between them.

Privacy

The analysis happens entirely in your browser. Your workflow file is read locally by JavaScript — it is not uploaded to a server in order to be analysed. Signing in is optional and only adds saving workflows to your account. See the Privacy Policy for exactly what is and is not recorded.

Common questions