Why Are Microsoft's Mage-Flow Models Gone From Hugging Face?

July 30, 2026

Microsoft advertised six Mage-Flow checkpoints on Hugging Face, but all six stopped being publicly accessible within a week. Mirrors remain; Microsoft has not explained why.

Microsoft's six official Mage-Flow model repositories are no longer publicly accessible on Hugging Face, even though Microsoft's current GitHub documentation still advertises them. Community mirrors preserve copies of the weights, but Microsoft has not publicly explained whether the originals were deleted, made private, gated temporarily, or withdrawn for a specific reason. The disappearance is confirmed; the motive is not.

Checked July 30, 2026: OpenVeil tested all six official Mage-Flow repository links, Microsoft's current GitHub model table, the public Hugging Face API, the surviving Mage-VL repositories, and two independent preservation paths.

Who This Article Is For

This article is for:

• people searching why Microsoft Mage-Flow disappeared from Hugging Face
• creators who downloaded or planned to use Mage-Flow locally
• developers who built a workflow around a model repository name
• privacy-conscious users comparing self-hosted and hosted AI
• teams that need reproducible model artifacts, licenses, and checksums
• anyone who assumes "open weight" also means "permanently available"

The short answer is:

The six official Mage-Flow pages stopped being publicly readable less than a week after Microsoft announced their release. Public mirrors exist, but a mirror is not the same as an official repository, and no public evidence currently explains Microsoft's decision.

What Is Confirmed

Microsoft Announced Six Mage-Flow Checkpoints On July 22

Microsoft's current Mage repository says the Mage-Flow checkpoints were released on Hugging Face on July 22, 2026.

The model zoo still lists six official repositories:

• microsoft/Mage-Flow-Base
• microsoft/Mage-Flow
• microsoft/Mage-Flow-Turbo
• microsoft/Mage-Flow-Edit-Base
• microsoft/Mage-Flow-Edit
• microsoft/Mage-Flow-Edit-Turbo

The family covers three text-to-image variants and three image-editing variants: Base, RL-aligned, and four-step Turbo.

The associated Mage-Flow research paper describes a four-billion-parameter image-generation and editing stack designed for native resolutions from 512 to 2048 pixels. Microsoft's documentation reports 0.59 seconds per image for the Turbo checkpoint and 1.02 seconds per edit on a single A100 at 1024 by 1024 resolution.

Those are release and benchmark claims from Microsoft and the paper. They do not explain what happened to the public repositories afterward.

All Six Official Model Repositories Are No Longer Publicly Readable

OpenVeil checked each official Hugging Face API endpoint without authentication on July 30:

An HTTP 401 result establishes that an unauthenticated visitor cannot currently read the repository through the public model API. It does not distinguish among every possible backend state.

The repositories could have been:

• made private
• placed behind an access restriction
• disabled temporarily
• removed
• moved into an administrative state that is not publicly visible

The strongest defensible claim is therefore that all six official repositories are no longer publicly accessible.

Microsoft's Other Mage Repositories Remain Public

This is not a blanket disappearance of Microsoft's Mage organization or project.

During the same July 30 check:

• microsoft/Mage-VL remained public
• microsoft/Mage-ViT remained public
• Microsoft's Mage GitHub repository remained public
• the GitHub documentation continued linking to the six unavailable Mage-Flow pages

That narrower pattern matters. It points to the Mage-Flow checkpoints, not to a general Hugging Face outage or a total withdrawal of the Mage project.

Community Mirrors Preserve At Least Two Recovery Paths

The model family is not lost from the public internet.

The SceneWorks/Mage-Flow repository says it created a preservation snapshot on July 24, before the official links became unavailable. Its model card identifies the exact upstream revision for each of the six Microsoft repositories and says it verified every large-file object against upstream metadata.

The archived upstream revisions are:

The separate Comfy-Org/Mage-Flow repository also remained public on July 30. The public Hugging Face API showed more than 44,000 downloads for that repository during OpenVeil's check.

These mirrors make continued local use possible for people who trust and verify them. They do not restore Microsoft's official distribution channel or supply an official explanation.

The Published License Was MIT

Microsoft's current GitHub documentation lists Mage-Flow under the MIT license. The SceneWorks and Comfy-Org mirrors also identify the model as MIT-licensed.

That is relevant because an already granted permissive license can allow lawful copies and redistribution, subject to the license terms. It does not force Microsoft to keep hosting an official repository forever.

Repository availability and license permission are separate questions:

• License: What a recipient may do with a copy.
• Availability: Whether the publisher still offers that copy at the original location.
• Provenance: Whether a copy can be traced to a specific original artifact.
• Support: Whether the publisher will maintain, patch, explain, or stand behind it.

Calling a model "open weight" answers only part of that four-part test.

The Removal Drew Immediate Community Attention

The disappearance spread through both r/LocalLLaMA and r/StableDiffusion on July 29.

Those threads established current attention and surfaced working mirrors. They also contained speculation about quality, safety filters, internal approval, and prior Microsoft model removals.

Speculation can show what users are worried about. It cannot establish why Microsoft acted.

What Is Still Unclear

Microsoft Has Not Explained The Change

No Microsoft statement located in the July 30 review explained:

• why the six repositories stopped being public
• whether the change is temporary
• whether Microsoft intends to restore them
• whether a specific checkpoint, license, dataset, safety, or quality issue triggered the change
• whether current local users should stop using a downloaded copy
• whether the surviving GitHub links will be corrected

Until Microsoft speaks, headlines that assign a motive are guesses.

A 401 Response Does Not Prove Deletion

A public page that returns 401 may look "gone" to an ordinary visitor, but the status alone does not prove that the repository data was erased.

It may still exist in:

• a private repository
• an administrative quarantine
• an internal backup
• a publisher-controlled cache
• public or private copies held by previous downloaders

The status proves a present access boundary, not the complete lifecycle of the underlying files.

Mirrors Do Not Automatically Prove Every File Is Safe

SceneWorks provides unusually specific provenance information: full upstream commit hashes and a claim of byte-for-byte verification. That is stronger than an unlabeled re-upload.

Even so, a careful user should independently verify:

• the mirror owner
• the exact repository revision
• large-file hashes
• model configuration and custom code
• the original and mirrored licenses
• dependency versions
• whether the runtime executes remote or repository-supplied code
• whether an application makes network requests after the model loads

A familiar model name does not make every mirror trustworthy.

The Disappearance Does Not Prove A Privacy Incident

There is no current evidence that:

• user prompts or images leaked
• Microsoft discovered malicious model code
• Hugging Face suffered a breach involving Mage-Flow
• the model was used in an attack
• community mirrors contain compromised files
• Microsoft removed the model because of privacy law

Those possibilities may attract clicks, but they are not supported by the evidence now available.

What This Means For Local AI Privacy

Mage-Flow's disappearance exposes a tradeoff that "local versus cloud" comparisons often miss.

A local model can keep prompts and images on infrastructure you control after you possess a complete, working copy. But getting and preserving that copy creates a supply-chain and operations problem of its own.

Local privacy can depend on:

1. obtaining the correct weights
2. preserving the license and model card
3. pinning the runtime and dependencies
4. verifying hashes
5. controlling outbound network access
6. keeping the application around the model local
7. maintaining enough hardware to run it

If the upstream repository disappears before those steps are complete, the phrase "you can run it locally" may be technically true but operationally useless.

The reverse tradeoff also matters. A hosted AI service removes the need to preserve multi-gigabyte checkpoints and runtime dependencies, but users depend on the service operator for:

• model availability
• product changes
• retention and deletion rules
• request processing
• provider access
• account continuity

Local control and hosted convenience solve different problems. Neither creates permanent availability by itself.

A Five-Part Model Preservation Check

Before relying on any open-weight model for sensitive or production work, use this check.

1. Can You Name The Exact Revision?

Do not record only organization/model-name.

Record the full commit hash, release tag, model-card date, and license version. Hugging Face's official download guide supports downloading a specific commit with the revision parameter.

2. Do You Have A Complete Local Snapshot?

Hugging Face documents snapshot_download() for downloading an entire repository. A browser bookmark is not a backup.

Confirm that the snapshot includes:

• weights
• tokenizer or text encoder
• VAE or other required components
• scheduler and configuration files
• model card
• license
• required code

Mage-Flow's mirrors say each self-contained repository included a transformer, text encoder, VAE, scheduler, and model index.

3. Can You Verify The Files?

Preserve checksums outside the model directory. Compare them after transfers and before deployment.

For a mirror, verify against:

• a known upstream commit
• upstream large-file metadata
• more than one independent archival source where practical

If the official source is already unavailable and no trustworthy hashes exist, uncertainty becomes part of the risk decision.

4. Can The Runtime Work Without The Original Repository?

Test an offline start from a clean environment.

Look for:

• hard-coded upstream repository names
• packages downloaded at runtime
• license checks
• telemetry
• automatic updates
• hosted prompt enhancement
• remote safety or moderation services

Local weights do not make a surrounding application local if it still sends prompts, images, metadata, or generated outputs elsewhere.

5. What Is Your Replacement Plan?

Decide what happens if:

• the model disappears
• a license changes for future releases
• a security issue is disclosed
• a required package breaks
• your hardware fails
• a better-supported model replaces it

The safest production plan treats a public model repository as a dependency, not as permanent infrastructure.

Where OpenVeil Fits

OpenVeil does not provide Mage-Flow, preserve removed model repositories, or guarantee that any third-party model will remain available.

OpenVeil is a different tradeoff: a paid privacy-focused AI chat workspace with browser-local chat history, no server-side chat-history record for private chat sessions, and web search, uploads, voice, and image tools where enabled.

That hosted convenience means users do not need to download and maintain model checkpoints. It does not mean OpenVeil is fully offline or that data never leaves the device. Active requests may still be processed by OpenVeil and necessary AI, hosting, routing, search, upload, security, billing, and infrastructure providers.

Choose local AI when possessing the exact model artifact and controlling inference infrastructure are requirements. Consider OpenVeil when you want a hosted private AI workspace without managing local weights, while accepting the active-processing boundary described in the OpenVeil privacy policy.

For the broader decision, compare private AI chat versus local AI, the hardware reality behind large open-weight models, and what to check before trusting an AI privacy claim.

Frequently Asked Questions

Did Microsoft delete Mage-Flow?

The six official Mage-Flow repositories were not publicly accessible during OpenVeil's July 30 check, but the observed HTTP 401 responses do not prove permanent deletion. Microsoft has not publicly explained the repository state.

Can You Still Download Mage-Flow?

Community copies remain available, including SceneWorks preservation snapshots and a Comfy-Org repository. Verify the repository owner, license, full revision, file hashes, configuration, and runtime before using a mirror.

Why Did Microsoft Remove Mage-Flow From Hugging Face?

The reason is unknown. Community theories about quality, safety, legal review, or internal approval are not confirmed by Microsoft.

Is Mage-Flow Open Source?

Microsoft describes Mage-Flow as MIT-licensed and released the model weights, paper, and code. "Open source" can carry different definitions for models, training data, and software, so the more precise description is an MIT-licensed open-weight model family with public code and a research paper. The training dataset itself was not released as a complete reproducible corpus.

Does A Community Mirror Have The Same Privacy Benefits As The Original?

Not automatically. Local inference can keep prompts and images on your own hardware, but only if the mirrored files are authentic and the surrounding runtime does not send data elsewhere. Provenance, custom code, dependencies, telemetry, and network behavior still matter.

Can A Downloaded Open-Weight Model Stop Working After The Official Page Disappears?

A complete local copy can continue working, but only if you preserved all required files and dependencies. Workflows that download components on demand, check an upstream repository, or rely on uncached packages may fail.

Does OpenVeil Use Mage-Flow?

OpenVeil's current product documentation does not claim that it uses or offers Mage-Flow. OpenVeil supports image tools where enabled, but its documented privacy promise is about browser-local private-chat history and no server-side chat-history record, not permanent access to a particular third-party model.

The Bottom Line

Microsoft released six Mage-Flow checkpoints, kept public documentation pointing to them, and then all six official Hugging Face repositories stopped being publicly readable within a week. Mirrors preserve usable copies, but Microsoft has not explained the change.

The practical lesson is larger than Mage-Flow: open weights create the possibility of local control, not a guarantee of permanent availability, verified provenance, or a durable application. If a model matters, pin the exact revision, preserve a complete snapshot, verify hashes, test offline, and keep a replacement plan.

Sources

• Microsoft Mage repository and model zoo
• Microsoft Mage-Flow implementation guide
• Mage-Flow research paper
• SceneWorks Mage-Flow preservation snapshot
• Comfy-Org Mage-Flow repository
• Hugging Face guide to downloading repositories and pinned revisions
• r/LocalLLaMA discussion of the unavailable Microsoft repositories
• r/StableDiffusion discussion of the Mage-Flow removal