First CHToolsFree web tools

FIRST CH TOOLS / Images / 92 COMFYUI KEY LEAK CHECK

ComfyUI PNG API Key Leak Check

Drop one ComfyUI PNG you received or posted. It looks for API key formats (AIza, sk-, sk-ant-, hf_, r8_) in the embedded prompt and workflow and shows where they are by node ID and input. You can also copy a heads-up message for the key owner and save a copy without the embedded data.

The image is read on this device only — never uploaded or stored

Sample PNG: these are fictional keys. Nothing needs to be replaced.

PNG

Reading

Heads-up message for the key owner

No values and no file name. Only where it was found and what was not checked.

Save a copy without text chunks (for re-posting)

Removes tEXt, iTXt and zTXt (including prompt and workflow) and keeps every other chunk byte for byte. The copy is re-read and checked before saving. Your original file is not changed.

    How to Use

    1. Drop one PNGDrop a ComfyUI PNG you received or posted onto the box, or tap to choose one. “Try the sample PNG” shows what a result looks like (its keys are fictional).
    2. Read the state and the placesYou get one of four states: “Key format found”, “No key format found”, “Not checked” or “Could not process”. For a find, it shows the node ID, class_type and input name from prompt, or only the node ID and the widgets_values position when there is only a workflow. Everything but the first 4 characters is masked.
    3. Copy the message, or save a stripped copyCopy a message for the key owner (no values, no file name). If it is your own image, save a copy without the embedded text and post that instead. Disable the key itself in the provider’s dashboard.

    About This Tool

    A ComfyUI PNG carries its whole recipe

    A PNG saved by ComfyUI holds the nodes and settings used to make it, in two text chunks: prompt (what was run: class_type and inputs per node ID) and workflow (the node graph on screen, where input values sit in an unnamed array, widgets_values). If an API key was typed straight into a node that calls an external API, the key stays in the image too. When the image is posted or delivered, anyone can see the key just by loading the image into ComfyUI.

    This page reads the PNG chunk by chunk, checks each chunk’s CRC, and then searches the text of tEXt and uncompressed iTXt chunks for 5 key formats (Google AIza, OpenAI-style sk-, Anthropic sk-ant-, Hugging Face hf_, Replicate r8_). JSON is read by its own parser, so an earlier value hidden by a duplicate key is not lost. Bypassed nodes disappear from prompt but stay in workflow, so workflow is searched too. Node titles can be renamed, so places are given by ID and class_type.

    “No key format found” does not mean the image is clean. Only those 5 formats are searched; other kinds of secrets, text drawn in the picture, compressed chunks (zTXt, compressed iTXt), eXIf and caBX (C2PA provenance) are not read. Anything unreadable is reported as “Not checked”. Chunk handling follows the W3C PNG specification (Third Edition).

    What it does not do

    It does not check whether a key is valid (keys are never sent anywhere), fetch other people’s images by URL or collect them in bulk, process ZIPs, rewrite JPEG or WebP (use the EXIF Viewer & Remover), or write reports to node authors. The message avoids claiming that a node or its author is at fault. The image is read in this browser only and is never uploaded or stored. AI agents can run the same check with the MCP tool comfy_png_leak_scan (for AI agents).