Phosphene 5 Runs H3 on a Mac, Offline. The Price Is Time.

Free, as in bring your own hardware

Start with what Phosphene actually removes. A cloud video bill is not just the per-second rate; it is the queue, the rejected takes billed anyway, the footage uploaded to someone else's server, and the subscription that keeps running in a quiet month. Phosphene removes all of that at once. Download the models once, and a Mac on your desk makes picture and sound together, offline, with nothing uploaded and no meter running. For anyone testing shots they would be embarrassed to pay cloud prices to iterate on, that changes the working method, not just the invoice.

Phosphene's homepage publishes render times alongside its sample videos. The H3 examples reviewed by the desk were produced on an M4 Max Mac with 64 GB of unified memory. Several took approximately 15 to 19 minutes, another took 36 minutes, and a 15-second one-take example took 103 minutes. These are developer-selected examples, not a controlled benchmark or a guarantee of performance on other Macs. Clip duration, settings and hardware configuration can substantially change rendering time.

An October 2026 arXiv deployment report describes producing 17 clips through Phosphene v4.19.0 on an M5 Pro Mac mini with 64 GB of memory, without cloud generation. The reported workflow took 26.49 hours, equivalent to approximately 94 minutes per completed clip when the total is divided by 17. That is a workflow average, not necessarily the model's average inference time per clip, and it was measured on an earlier Phosphene version.

None of this is hidden. The times sit printed next to the results, which is more than most cloud pricing pages do for their effective cost per usable take.

Memory is the other gate, and it is a hard one. A 16 GB Mac, which describes a large share of the Macs actually sold, gets LTX-2.5 at smaller sizes and little else. H3 starts at 36 GB, its full-precision engine at 60 GB, and the tier with no size limits at 128 GB. The free app, in other words, is free in proportion to a purchase many readers have not made. That does not make the offer hollow. It makes it specific: this is a tool for people who already own a heavy Mac, and for them the marginal cost of a render really is the electricity.

The license is the app's problem to show you, not to solve

Phosphene's application code is released under the MIT license. That does not extend MIT terms to the models it runs. MiniMax H3 is governed by its own Community License, which does not cover the United States, European Union, United Kingdom or South Korea. The project's FAQ says Phosphene displays the model license and asks users to accept it once, but does not check their location. That absence of enforcement is not permission to use H3 outside the license's geographic scope.

Canada is not among the territories excluded in the license description reviewed by the desk. Users still need to comply with the model's other terms and any applicable restrictions. LTX-2.5 provides a separate video-generation route, subject to its own model license.

ALFW has covered that H3 license since the model's release, including what it means for publishing locally generated work. The position has not changed, and Phosphene does not change it. Any coverage that calls Phosphene simply "free local H3 for your Mac" without the territory line is leaving out the fact most likely to matter to the largest group of readers.

Phosphene 5 introduces an optional Pro tier advertised at $15 per month or $120 per year, with a Founding option listed at $199 for three years. The developer says features previously available for free remain free. The version 5.0 notes also say that faster H3 image-to-video generation, a headline Pro feature, is not available yet and is not a reason to purchase Pro today.

There is an unresolved inconsistency in the published materials. The November 7 version 5.0.2 notes say Pro checkout is not open, while the homepage displays checkout buttons. Their presence does not establish that payment can be completed. Readers should verify the current checkout status and available benefits before paying. For the capabilities already included in the free version, there is no demonstrated reason to subscribe.

None of this diminishes what a single developer has shipped: more than 120 releases in under six months, a native app, honest render times, and release notes that tell you what is broken. In a category sold on cherry-picked demos, Phosphene's documentation reads like it expects to be checked. It survives the check, with the license line and the clock attached. That is the story.

Sources

[1] Phosphene homepage, phosphene.video, read in full for this article and re-read at publication. The engine list, memory gates, labelled sample render times, usage figures, pricing tiers, MIT license, offline behavior and the H3 license FAQ all come from this page.Read source
[2] Phosphene changelog, phosphene.video, read in full for this article. Release dates and contents for v5.0.0 (6 November 2026), v5.0.2, v5.0.3 and v5.0.4 (all 7 November 2026), including the 5.0.2 note that Pro checkout is still not open, the 5.0 notes calling faster H3 picture-to-video not a reason to buy Pro today, and the 5.0.3 still-image speed claim with its M4 Max baseline.Read source
[3] Mrbizarro, "Pika H3 Flex for Mac (MLX)", Hugging Face model card. Independent description of Phosphene as a free Mac app for local video, sound, image and music generation, and of the H3 Flex preview running inside it on MiniMax H3 base weights under the MiniMax H3 Community License.Read source
[4] Shi and Shi, "Running a 20B Video Diffusion Transformer on Consumer Hardware: A Deployment and Measurement Report for MiniMax H3 on Apple Silicon", arXiv:2611.00843, October 2026, PDF read first-hand for this article. Phosphene v4.19.0 used as the inference stack on an M5 Pro Mac mini with 64 GB; an unattended production run completed 17 clips in 26.49 hours with no cloud dependency.Read source
[5] Discovery: Instagram walkthrough reels presenting Phosphene's GitHub page and feature list, posted 2026-11-07 17:21 UTC (@nadd.exe) and 2026-11-07 20:12 UTC (@github_unpacked). Discovery only; no load-bearing figure rests on either reel.

THE ALFW VERDICT

Phosphene makes a credible case for local AI video by removing cloud uploads, account requirements and per-render charges while publishing hardware guidance and sample render times. Its limitations are substantial. MiniMax H3 requires at least 36 GB of unified memory under the project's guidance, some published examples take well over half an hour, and the H3 Community License does not cover the US, EU, UK or South Korea. An MIT-licensed interface does not remove those restrictions. For Mac owners with suitable hardware and model-license eligibility, the native application offers an alternative to more manual local-generation workflows. The developer's frequent releases and candid notes about unfinished features are encouraging, but they are not substitutes for independent reliability or performance testing. Phosphene removes the cloud bill; it does not remove the cost of hardware, rendering time or compliance with model licenses.