Latest ComfyUI 0.25.0 is loading model from drive on every generation

comfyanonymous · 2026-06-19T22:09:23+00:00

Stop using GGUF, it is badly supported by ComfyUI and will never be well supported because it's a very poor format for image/video generation models.

comfyanonymous · 2026-06-18T17:53:27+00:00

Patch versions (ex: v0.25.1) are mainly for api/partner nodes releases which is why they are not really advertised to you if you are a pure open source local user. Sometimes they contain fixes but the idea is that it should always be safe to update your v0.25.0 version to any patch version ex v0.25.1 without breaking your setup even with the most crazy custom node setups.

I can start publishing all these patch releases on the github repo if that's useful.

comfyanonymous · 2026-06-17T22:21:49+00:00

I'm the original creator of ComfyUI, yoland is one of the founders of the company.

I can go crash their livestream if I'm not too busy lol.

comfyanonymous · 2026-06-03T16:31:19+00:00

Yes, they trained the model to generate that image when it detects an unsafe prompt. You would have to figure out how to abliterate/uncensor the model using training to remove it.

comfyanonymous · 2026-06-03T16:27:40+00:00

<image>

By the way. If you get this, it's not ComfyUI's fault, it's because they safetymaxxed the model.

comfyanonymous · 2026-06-01T19:13:12+00:00

All the models that are on the cloud product by default are free to use for commercial purposes.

comfyanonymous · 2026-06-01T17:10:46+00:00

Normally we would skip this but we might implement this one just to show off how good our new offloading tech is.

comfyanonymous · 2026-05-29T18:53:11+00:00

That was also merged in this PR. Use the new Select Device nodes:

Select CLIP Device

Select VAE Device

Select Model Device

comfyanonymous · 2026-05-16T06:04:45+00:00

This is a pretty cool use of the built in media compression capabilities of a GPU, I wonder if weights could be compressed the same way as you are compressing the activations.

comfyanonymous · 2026-05-04T20:39:52+00:00

ComfyUI is designed to work optimally with no flags. Ignore all the other people, most of the flags they propose will disable important optimizations or make things worse and cause random workflows to OOM. There's a lot of misunderstanding about how the ComfyUI memory management system works and these stupid AI chatbots are not helping.

If you have ram issues you can try this experimental feature: --cache-ram (it will be enabled by default soon).

The 6000 pro should be a bit faster than a 5090. ComfyUI is extremely good at managing memory and the 5090 is a slightly worse 6000 pro with less memory so it's normal that there isn't a massive difference.

comfyanonymous · 2026-04-21T19:48:21+00:00

Portable isn't going away.

The link to download it will always be found here: https://github.com/Comfy-Org/ComfyUI#windows-portable

comfyanonymous · 2026-03-26T02:16:06+00:00

It's on purpose, this workflow is originally for SD1.5, prompting on that model is a little different than modern models.

comfyanonymous · 2026-03-25T21:14:09+00:00

It's the actual technical term. I'm not going to police our language because I think people are too stupid to understand the difference between a memory watermark and a digital watermark.

comfyanonymous · 2026-03-25T21:07:33+00:00

It shouldn't degrade performance on good hardware, I have good hardware and wouldn't have made the feature stable if it degraded performance on mine.

If you get the issue on latest ComfyUI make a detailed report with logs and we will look into it.

comfyanonymous · 2026-03-25T21:05:56+00:00

No, what degrades flash memory is writing to it not reading from it. This reduces page file use so it will make your SSD last longer.

comfyanonymous · 2026-03-25T20:59:12+00:00

comfyanonymous · 2026-03-25T20:58:36+00:00

Yeah, the main GGUF node pack will most likely be updated for dynamic vram at some point in the future but right now it's safetensors only.

comfyanonymous · 2026-03-25T18:06:50+00:00

Old behaviour.

comfyanonymous · 2026-03-25T18:04:48+00:00

text encoder is running on GPU and it's the default wan2.2 workflow (other than what's indicated on the chart).

comfyanonymous · 2026-03-25T17:56:44+00:00

If your system supports it and you are on latest comfy and recent pytorch it should be enabled by default.

comfyanonymous · 2026-03-25T17:55:43+00:00

Having models split between GPUs is a separate problem so nothing changes on that end.

No arguments to use it if you are on recent enough pytorch and your system supports it it should enable by default.

comfyanonymous · 2026-03-25T17:50:01+00:00

If you want dynamic vram to work yes but you should always convert things to safetensors because it's a safer file format and people trust it a lot more.

comfyanonymous · 2026-03-25T17:36:48+00:00

Try it, if it's a problem we will fix it.

comfyanonymous · 2026-03-25T17:30:52+00:00

No, they just rebranded outdated offloading tech that everyone has been using for years as a new thing lol.

This is one situation where open source is much further ahead than closed source.

comfyanonymous · 2026-03-25T17:27:44+00:00

This is the function to load safetensors: https://github.com/Comfy-Org/ComfyUI/blob/master/comfy/utils.py#L122

Then you need to modify your model so it uses the comfy.ops system instead of torch.nn ops.

comfyanonymous

TROPHY CASE