Start by identifying the file you have. A Krea image can be used as a visual input in ComfyUI, but an image is not a node graph, and a model name alone is not an installable checkpoint.
Krea and ComfyUI serve different parts of a visual process. Compare the handoff before looking for an import button.
Krea output or reference
ComfyUI input
Krea output or reference
A visual result to inspect or reuse
ComfyUI input
Can be loaded as image input
Krea output or reference
Not established by an image export
ComfyUI input
Requires a compatible workflow file or graph
Krea output or reference
Not contained in a finished image
ComfyUI input
Must be available in a compatible format
Krea output or reference
Useful as a written reference
ComfyUI input
Can be entered into an appropriate text node
Krea output or reference
Visible in the resulting pixels
ComfyUI input
Need to be recreated with suitable nodes
Krea output or reference
Choose or develop a visual direction
ComfyUI input
Arrange and repeat a local node-based process
These starting points depend on whether you need the picture, its editing approach, or a reproducible graph. None assumes that Krea exports ComfyUI nodes.
You have a finished reference image and want to explore variations.
Load the image in ComfyUI, then choose compatible nodes and models for the next pass. The krea 2 image to-image guide explains the image-input distinction.
krea 2 image to-imageYou want to test different strengths or prompts against one source.
Keep the source image fixed while changing one graph setting at a time. The krea 2 i2i page covers that shorthand for image-to-image work.
krea 2 i2iYou found a model name but no weights or installation instructions.
Verify what is actually distributed before adding a loader node. The krea 2 model page separates a model label from a usable local file.
krea 2 modelYou need a targeted change rather than a repeatable generation graph.
Decide whether editing the image directly is simpler than rebuilding its look in nodes. The krea 2 image edit page focuses on that choice.
krea 2 image editFor an image, save a local copy, load it through a ComfyUI image-input node, connect a compatible graph, and inspect the output. For a workflow file, check its required nodes and models before running it.
If dragging in a picture does not create nodes, that is expected: pixels do not describe the process that made them. If a workflow file opens with missing-node warnings, identify the referenced node packages; if a model loader fails, check the required model file and compatibility. Save a working copy before replacing nodes. To explore a different creative starting point, continue to the linked tool.
Explore creative toolsYou can use an image saved on your device as image input in a ComfyUI graph. This transfers the pixels, not the settings, model weights, or steps used to produce them. Build the subsequent processing with nodes and models available in your own installation.
Do not assume it will. A finished image does not by itself provide a compatible node graph. If you need a repeatable graph, obtain a workflow file intended for ComfyUI and check what it requires.
An image-input workflow can use a compatible model you already have; it does not require the original image's model weights. Reproducing a particular model locally is a different question. First verify that compatible weights are actually available.
The graph may refer to custom nodes that your installation does not have. Read the missing-node names and verify their sources before installing anything. You may also need to replace nodes if the original graph depends on unavailable models.
A prompt and reference image are useful starting materials, but they do not specify every part of the original generation process. Different models, settings, and processing steps can produce different results. Treat a recreation as a new experiment, not an exact import.