Image editingComfyUI-ready repository

Comfy-Org

Run flux1-kontext-dev_ComfyUI

Edit source images with a validated ComfyUI workflow family. Estimated setup is about 20 minutes, with no local installation. From $0.25/hour.

Review live offers See what it costs

Validated runtime

Architecture and task checked

Immutable revision

aa3dd3c4bf

Dedicated workload

Isolated model endpoint

You control runtime

Runs until you stop it

The outcome

What it does

flux1-kontext-dev_ComfyUI is a validated image editing model.

GPU Vault admits only generated-registry repositories whose exact component paths and hashes match a pinned official ComfyUI core-node workflow.

The model launches in a persistent authenticated ComfyUI workspace. Download outputs before stopping the workload because workspace files are deleted during teardown.

Example workflows

What you can build

Creative production

Build and refine media with an editable node graph.

Workflow iteration

Adjust the bundled starter workflow for your project.

Direct API

Queue prompts through the authenticated ComfyUI API.

Results depend on the model, prompt, sampling settings, and publisher guidance.

Recommended hardware

Your setup

We run this on

1× GPU · 24 GB VRAM

This is the smallest supported topology with enough memory for the model weights, runtime overhead, and the validated context window. GPU Vault also reserves 42 GB for the immutable model files and engine data.

Why this setup?

The compatibility classifier uses safetensors metadata, engine overhead, context memory, and tensor-parallel divisibility. It rejects unsupported architectures and models that need more than eight GPUs.

GPUs: 1
VRAM each: 24 GB
Disk: 42 GB
Tensor parallel: 1
Weight memory: 16.4 GB
Setup estimate: ~20 min

Transparent usage

What will it cost?

Current public starting rate

$0.25/hour

The dashboard shows your exact role-based rate and live offer before approval.

Runs until you stop it

There is no fixed serving duration. Billing follows active compute time from instance creation through teardown.

Approve before launch

Review the exact GPU, base compute rate, setup estimate, and initial wallet hold. No credits are reserved from this public page.

Choose your workflow

Two ways to use it

Open the ComfyUI workspace

Start from the GPU Vault core-node workflow and keep full graph control.

Launch for the console

Available after the model passes its readiness check.

Connect your application

Use the short-lived direct ComfyUI API credential from the workload page.

Launch for API access

Rotate or revoke the workload key at any time.

Exact profile

Model facts

Show details

Publisher: Comfy-Org
Category: image editing
Architecture: ComfyUI:flux_kontext_dev_basic
Parameters: Not declared
Context window: Not applicable
Weight memory: 16.4 GB
Repository storage: 16.4 GB
Tensor parallelism: 1
License: other
Exact revision: aa3dd3c4bf31e466dd343107b2af67c472b948bc

View original repository on Hugging Face

Keep exploring

Find another model

More image editing models

Compare other launchable models with the same serving task.

Explore

More from Comfy-Org

Search validated models published by the same organization.

Explore

Browse every launchable model

Explore text generation and pinned ComfyUI image, editing, and video models.

Explore

From Comfy-Org

Publisher documentation

Read model card

FLUX.1-Kontext-dev

Repackaged model files for ComfyUI.

Original model repository: https://huggingface.co/black-forest-labs/FLUX.1-Kontext-dev

Place the files in the following folders:

📂 ComfyUI/
├── 📂 models/
│   ├── 📂 diffusion_models/
│   │   └── flux1-dev-kontext_fp8_scaled.safetensors

Original version (the license on the original flux1 kontext dev repo applies to all the flux kontext dev model files in this repo).

Examples

https://comfyanonymous.github.io/ComfyUI_examples/flux/#flux-kontext-image-editing-model

https://docs.comfy.org/tutorials/flux/flux-1-kontext-dev

Workflows

Common questions

Before you launch

What happens to image editing outputs?+

Outputs stay on the GPU instance. Download anything you need before Stop or teardown; GPU Vault does not copy catalog workspace files into Supabase storage.

Do I need to install or configure the model?+

No. GPU Vault uses a fixed server-owned runtime configuration and the model’s immutable revision. Select a live GPU offer, explicitly approve the launch, and wait for the readiness check.

How does billing work?+

The workspace runs until you stop it, with the approved rate protected by your initial and rolling wallet holds. If the runtime image cannot download before ComfyUI becomes ready, GPU Vault records zero customer usage and returns the complete hold after confirmed teardown.

Can the model or price change after I approve?+

Approval revalidates the exact model profile, GPU offer, rate, wallet, and operational gates. If a customer-visible model or offer changes before launch, GPU Vault requires a fresh review.

Are my prompts and outputs stored?+

GPU Vault records only endpoint, status, latency, and byte-count metrics for inference requests. Prompt content, documents, embeddings, and generated output are not persisted by the inference proxy.

Ready when you are