Community Raises $10,000 and Fine-Tunes Sulphur 3 Video Model in Three Months

The r/StableDiffusion community ran a rare experiment: users raised $10,000 themselves, rented compute capacity, and fine-tuned a large video model for a task that commercial developers usually restrict. Three months later, the Sulphur 3 project reached release on Hugging Face.

For engineers, the subject matter of the generated videos is less interesting than how the entire effort was structured. A small independent team took MiniMax H3, prepared a specialized dataset, and attempted to change the behavior of an already optimized model. The result is a vivid example of the friction between the promise of "we will take open weights and continue training them" and the realities of the work.

Why the finished model proved difficult to retrain

MiniMax H3 is distributed as a CFG-distilled variant. Put simply, the model has already been prepared for fast generation and trained to operate without some of the computations normally required to control prompt adherence. That is convenient at inference time, but it creates problems for full fine-tuning: changing the weights can disrupt the delicate balance achieved by the original model's developers.

Imagine a production car with carefully tuned electronics. Replacing the wheels is straightforward—small LoRA adapters work in roughly the same way. But if you rebuild the engine and transmission, the old settings no longer guarantee the same behavior. The car may perform better off-road but lose stability on the highway. Something similar happens with a video model: improving anatomy, motion, or interactions between characters can impair other generation scenarios.

Project participants warned in advance that full fine-tuning could break compatibility with existing LoRAs, change the optimal inference settings, and weaken some MiniMax H3 capabilities. During the work, there were also direct complaints that H3 was training worse than expected. The delay to almost three months therefore looks less like a simple organizational failure and more like the consequence of a technical risk the team underestimated at the outset.

What exactly the community released

Several Sulphur 3 variants have been published on Hugging Face. The full Base checkpoint is 40.2 GB, INT8 is 20.9 GB, and W4A8 is 11.4 GB. A separate correction module is 7.99 GB. Ref2VA variants for working with references and components for ComfyUI have also been announced.

This range matters in practice. A developer can begin with W4A8 on relatively affordable hardware, assess speed and quality, and then compare the result with INT8 or the full version. File size alone, however, does not indicate how much memory the entire pipeline will require: inference must also account for text encoders, the decoder, video length, resolution, and intermediate tensors.

The project was trained on a video dataset that was planned to be almost twice the size of Sulphur 2's collection of roughly 125,000 clips. According to participants, 60% of the material consisted of realistic footage, while 3D and hand-drawn animation each accounted for 20%. For now, these figures should be treated as claims by the team: the original announcement does not include an open audit of the dataset's composition, licenses, or annotation quality.

What to take into production

Sulphur 3 is useful as a case study in community-funded compute. The community quickly raised a substantial sum, weathered a delay, and received several checkpoints instead of a closed service. This is a workable model for niches that major labs do not want to serve.

However, it is too early to put the model into production solely because of the high-profile release. The repository is gated: users must sign in and accept the terms, and approval may take time. There are still too few independent quality comparisons. The provenance of all training data, the legal constraints, and the extent to which H3's baseline capabilities have degraded also remain unclear.

The practical conclusion is simple: treat Sulphur 3 as an experimental checkpoint. First, establish your own set of test prompts and compare it with the original H3 for motion quality, character consistency, and speed. Then separately test compatibility with the LoRAs and ComfyUI nodes you need. The project's history makes one point especially clear: money for GPUs can be raised quickly, but predictably fine-tuning a large distilled model remains a difficult engineering task.