The inference company fal released H3 Max, a post-trained variant of MiniMax's open-weight H3 video model that renders a five-second 768p clip in under three seconds. fal says it added significant new training data aimed at prompt adherence and aesthetics, spent a large share of its post-training compute on reinforcement learning against verifiable tasks, and co-designed the architecture with its own inference engine. The weights are not published -- H3 Max exists only as a hosted API.
Key facts
- A five-second 768p clip in under three seconds; fal's own image-to-video API example reports an inference time of 2.76 seconds.
- Supports 480p and 768p, video lengths up to 15 seconds with a 5-second default, and a prompt expansion mode of disabled, balanced or quality.
- fal reports Artificial Analysis ranking it first on the image-to-video leaderboard at an Elo of 1,201 +/- 11 across 2,177 samples, priced at $3.60 per minute.
- Primary sources: fal H3 Max landing page, image-to-video page, text-to-video API docs.
The hook. Three seconds is roughly the length of the clip you are waiting for. That crosses a threshold: video generation stops being a job you submit and becomes something you iterate on.
Background. MiniMax released H3's weights earlier and kept the strongest configuration behind its own API, which we covered in MiniMax shipped H3 weights and kept the good part hosted. fal is an inference platform: its business is running other people's models fast. H3 Max is what happens when the company running the model decides to also finish training it.
What they did. In fal's own description, it added "significant new data ... aimed at adherence and aesthetics" and spent "a huge portion of our post-training compute" on "verifiable RL tasks" -- reinforcement learning where a program, not a human rater, can check whether the output satisfies the request. The landing page also says the architecture was co-designed with fal's inference engine, which is the part that explains the latency: the model was shaped around the serving stack rather than handed to it.
How it works. Post-training is the stage after a model has learned the general shape of its domain, where you push it toward the specific behaviour you want. Reinforcement learning with verifiable rewards works when success can be checked automatically -- for video, things like whether the requested object actually appears, whether the camera moves the way the prompt asked, whether the requested count of items is right. It is cheaper and more consistent than human preference rating, and it is why "prompt adherence" improves faster than "beauty" in these releases. Speed, separately, comes from distillation techniques that collapse many denoising steps into few.
Why it matters. This is a recurring shape in 2026's generative-video stack: an open-weight lab publishes a base model, and an inference company post-trains it into something better and closes it. Seven of fifteen hot r/StableDiffusion threads during the launch window were H3-related, which means the enthusiast community is doing the discovery and distribution work for a product it cannot itself run. The economics are straightforward -- fal's engine and its post-training compute are the moat, and open weights are the raw material.
The pricing tells you who this is for. At $3.60 per minute of generated video, a five-second clip costs about thirty cents -- trivial for an agency iterating on a storyboard, prohibitive for anyone generating at volume without a client attached. Combined with the fifteen-second maximum length, the product is shaped for short-form: social clips, product shots, animatics, the establishing beat in an ad. That is where the commercial demand for generated video actually sits right now, and fal has optimised for the latency that makes iterating on it feel like editing rather than rendering.
The prompt_expansion_mode setting is a small tell about the same thing. Set to balanced or quality, the service rewrites your prompt into something the model handles better before generating -- a convenience that raises the hit rate for casual users, and a source of nondeterminism for anyone trying to reproduce a specific result. It can be disabled, and for production work it probably should be.
The honest caveat. The speed number is a product latency, not a benchmark. fal discloses no GPU model, no server configuration, and no batch size behind the 2.76-second measurement, so it cannot be compared against anyone else's hardware-qualified figure. The leaderboard placement is fal reporting a third party's ranking on fal's own page rather than a directly citable Artificial Analysis result. And the community's more dramatic numbers -- a "nearly 50x" speedup, five seconds of 720p in 3.5 seconds -- do not appear in fal's material at all; the published claim is 768p in under three seconds, which is a better claim stated more modestly.
The structural caveat is the one to keep. H3 Max has no weight repository. If you build a pipeline on it, you are building on an endpoint whose price, availability and behaviour are one business decision away from changing -- which is exactly the tradeoff open-weight models exist to avoid.
Originally published on Ground Truth, where every claim is checked against the primary source.
