Update:I've added some other fp8 versions of FLUX.1 [dev] that aren't hosted on Civitai anymore, specifically fp8_e4m3fn and fp8_e5m2, in addition to the scaled fp8 FLUX.1 [dev] version I had originally posted.The fp8_e4m3fn and fp8_e5m2 models were originally uploaded by Kijai <a target="_blank" rel="ugc" href="https://huggingface.co/Kijai/flux-fp8">here </a>on Hugging Face, where they note that E5M2 and E4M3 do give slightly different results, but it's hard/impossible to say which is better. E4M3 is what people are typically referring to when they say FP8.Here's some info from <a target="_blank" rel="ugc" href="https://www.reddit.com/r/FluxAI/comments/1ej3uga/comment/lgb1li5/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">this</a> Reddit post regarding fp8_e4m3fn and fp8_e5m2:FP stands for Floating Point. Any signed floating point number is stored as 3 parts:<ol><li>Sign bit</li><li>Mantissa</li><li>Exponent</li></ol>So number = sign * mantissa * 2^exponentE5M2 means that 2 bits represent mantissa and 5 bits represent exponent. E4M3 means that 3 bits represent mantissa and 4 bits represent exponent.E5M2 can represent wider range of numbers than E4M3 at cost of lower precision of the numbers. But the amount of different numbers that can be represented are the same: 256 distinct values. So if we need more precision around 0 then we use E4M3 and if we need more precision closer to min/max values then we use E5M2.The best way to choose what format to use is to analyze distribution of weight values in the model. If they tend to be closer to zero we use E4M3 or E5M2 otherwise.Original:I haven't seen this uploaded on here.This is the scaled fp8 FLUX.1 [dev] model uploaded to HuggingFace by <a target="_blank" rel="ugc" href="https://huggingface.co/comfyanonymous">comfyanonymous</a>. It should give better results than the regular fp8 model, much closer to fp16, but runs much faster than Q quants. Works with the TorchCompileModel node. Note: for whatever reason, this model does not work with Redux nor with some ControlNet models.The fp8 scaled checkpoint is a slightly experimental one that is specifically tuned to try to get the highest quality while using the fp8 matrix multiplication on the 40 series/ada/h100/etc... so it will very likely be lower quality than the Q8_0 but it will inference faster if your hardware supports fp8 ops.From <a target="_blank" rel="ugc" href="https://huggingface.co/comfyanonymous/flux_dev_scaled_fp8_test">HuggingFace</a> :Test scaled fp8 flux dev model, use with the newest version of ComfyUI with weight_dtype set to default. Put it in your ComfyUI/models/diffusion_models/ folder and load it with the "Load Diffusion Model" node.

FLUX.1 [dev] fp8 versions - Scaled fp8/fp8_e4m3fn/fp8_e5m2

I haven't seen this uploaded on here.Original v1 model was broken. Test v2 has been updated and fixed.This is the scaled fp8 FLUX.1 [dev] model uploaded to HuggingFace by <a target="_blank" rel="ugc" href="https://huggingface.co/comfyanonymous">comfyanonymous</a>. It should give better results than the regular fp8 model, much closer to fp16, but runs much faster than Q quants. Works with the TorchCompileModel node. Note: for whatever reason, this model does not work with Redux nor with some ControlNet models.The fp8 scaled checkpoint is a slightly experimental one that is specifically tuned to try to get the highest quality while using the fp8 matrix multiplication on the 40 series/ada/h100/etc... so it will very likely be lower quality than the Q8_0 but it will inference faster if your hardware supports fp8 ops.From <a target="_blank" rel="ugc" href="https://huggingface.co/comfyanonymous/flux_dev_scaled_fp8_test">HuggingFace</a> :Test scaled fp8 flux dev model, use with the newest version of ComfyUI with weight_dtype set to default. Put it in your ComfyUI/models/diffusion_models/ folder and load it with the "Load Diffusion Model" node.

Files with SHA256: 358fff9355c962532593898b10436f13e6f9bfb0389f36df03c6e55fe7c9cbfe