alt.freeweights.phi / Phi-4-mini-flash-reasoning
From: microsoft <huggingface.co/microsoft>Newsgroups: alt.freeweights.phiSubject:

Phi-4-mini-flash-reasoning

Date: 2026-11-15Commit: 1dff816Signed: 2DC28CC7B26A283B ✓

Text generation model with 3.9B parameters. Safetensors weights, 7.73 GB in all. Published by microsoft under MIT.

3.9B params7.73GBPhi-4-mini-flash-reasoningsafetensorspermissive
FactsParams3.9BSize7.73 GBFormatssafetensorsTasktext generationLicenseMITFrom sourcepermissive
$ fw get microsoft/Phi-4-mini-flash-reasoning
# manifest sha256 17970a9d5593… · 7.73 GB · 22 files
$ fw verify ./Phi-4-mini-flash-reasoning microsoft/Phi-4-mini-flash-reasoning
From sourceHosted (signed)microsoft/Phi-4-mini-flash-reasoningLast check: 2026-11-15 03:26 UTC

Get help: custom fine-tune or private deploy. We review your setup before we quote.

Works with

Overview

Size
7.73 GB
Weights
7.71 GB (safetensors)
Parameters
3.9B
Formats
safetensors
Task
text generation
License
MIT (permissive)
Files
22, each with a sha256
Publisher
microsoft
Added
2026-11-15
Section
alt.freeweights.phi
Lineage

Original release from the publisher.

Where these bytes come from
Publisher at the pinned commit→You

Sources are tried in order. A file counts only when its size and sha256 match the manifest. Sources are checked when you ask for them, not on a timer.

Sources
BadgeHostLast checkResult
From sourcehuggingface.co2026-11-15 03:26 UTCpassed

Model card

From the publisher at commit 1dff816. Shown as plain text with links; images open at the publisher.

Model Summary#

Phi-4-mini-flash-reasoning is a lightweight open model built upon synthetic data with a focus on high-quality, reasoning dense data further finetuned for more advanced math reasoning capabilities. The model belongs to the Phi-4 model family and supports 64K token context length.

📰 Phi-4-mini-flash-reasoning Blog

📖 Phi-4-mini-flash-reasoning Paper | HF Paper

📚 Training Codebase

👩‍🍳 Phi Cookbook

🏡 Phi Portal

🚀 vLLM Inference: V0: PR | Branch V1: PR

🖥️ Try It Azure Nvidia NIM

🎉Phi-4 models: [Phi-4-mini-reasoning] | [Phi-4-reasoning] | [multimodal-instruct | onnx]; [mini-instruct | onnx]

Abstract#

Recent advances in language modeling have demonstrated the effectiveness of State Space Models (SSMs) for efficient sequence modeling. While hybrid architectures such as Samba and the decoder-decoder architecture, YOCO, have shown promising performance gains over Transformers, prior works have not investigated the efficiency potential of representation sharing between SSM layers. In this paper, we introduce the Gated Memory Unit (GMU), a simple yet effective mechanism for efficient memory sharing across layers. We apply it to create SambaY, a decoder-hybrid-decoder architecture that incorporates GMUs in the cross-decoder to share memory readout states from a Samba-based self-decoder. SambaY significantly enhances decoding efficiency, preserves linear pre-filling time complexity, and boosts long-context performance, all while eliminating the need for explicit positional encoding. Through extensive scaling experiments, we demonstrate that our model exhibits a significantly lower irreducible loss compared to a strong YOCO baseline, indicating superior performance scalability under large-scale compute regimes. Our largest model enhanced with Differential Attention, Phi4-mini-Flash-Reasoning, achieves significantly better performance than Phi4-mini-Reasoning on reasoning tasks such as Math500, AIME24/25, and GPQA Diamond without any reinforcement learning, while delivering up to 10x higher decoding throughput on 2K-length prompts with 32K generation length under the vLLM inference framework. We release our training codebase on open-source data at this https URL.

Intended Uses#

Primary Use Cases#

Phi-4-mini-flash-reasoning is designed for multi-step, logic-intensive mathematical problem-solving tasks under memory/compute constrained environments and latency bound scenarios. Some of the use cases include formal proof generation, symbolic computation, advanced word problems, and a wide range of mathematical reasoning scenarios. These models excel at maintaining context across steps, applying structured logic, and delivering accurate, reliable solutions in domains that require deep analytical thinking.

Use Case Considerations#

This model is designed and tested for math reasoning only. It is not specifically designed or evaluated for all downstream purposes. Developers should consider common limitations of language models, as well as performance difference across languages, as they select use cases, and evaluate and mitigate for accuracy, safety, and fairness before using within a specific downstream use case, particularly for high-risk scenarios. Developers should be aware of and adhere to applicable laws or regulations (including but not limited to privacy, trade compliance laws, etc.) that are relevant to their use case.

Nothing contained in this Model Card should be interpreted as or deemed a restriction or modification to the license the model is released under.

Release Notes#

This release of Phi-4-mini-flash-reasoning addresses user feedback and market demand for a compact reasoning model. It is a compact transformer-based language model optimized for mathematical reasoning, built to deliver high-quality, step-by-step problem solving in environments where computing or latency is constrained. The model is fine-tuned with synthetic math data from a more capable model (much larger, smarter, more accurate, and better at following instructions), which has resulted in enhanced reasoning performance. Phi-4-mini-flash-reasoning balances reasoning ability with efficiency, making it potentially suitable for educational applications, embedded tutoring, and lightweight deployment on edge or mobile systems. If a critical issue is identified with Phi-4-mini-flash-reasoning, it should be promptly reported through the MSRC Researcher Portal or secure@microsoft.com

Model Quality#

To understand the capabilities, the 3.8B parameters Phi-4-mini-flash-reasoning model was compared with a set of models over a variety of reasoning benchmarks. We use a more accurate evaluation where Pass@1 accuracy is averaged over 64 samples for AIME24/25 and 8 samples for Math500 and GPQA Diamond. A high-level overview of the model quality is as follows:

ModelAIME24AIME25Math500GPQA Diamond
DeepSeek-R1-Distill-Qwen-1.5B29.5820.7884.5037.69
DeepSeek-R1-Distill-Qwen-7B53.7035.9493.0347.85
DeepSeek-R1-Distill-Llama-8B43.9627.3487.4845.83
Bespoke-Stratos-7B21.5118.2880.7338.51
OpenThinker-7B29.6924.3287.2541.60
Phi4-mini-Reasoning (3.8B)48.1331.7791.2044.51
Phi4-mini-Flash-Reasoning (3.8B)52.2933.5992.4545.08

Overall, the model with only 3.8B-param achieves a similar level of math and science reasoning ability as much larger models. However, it is still fundamentally limited by its size for certain tasks. The model simply does not have the capacity to store too much factual knowledge, therefore, users may experience factual incorrectness. However, it may be possible to resolve such weakness by augmenting Phi-4-mini-flash-reasoning with a search engine, particularly when using the model under RAG settings.

Model Efficiency#

The two figures below compare the latency and throughput performance of the Phi-4-mini-reasoning and Phi-4-mini-flash-reasoning models under the vLLM inference framework. All evaluations were performed on a single NVIDIA A100-80GB GPU with tensor parallelism disabled (TP = 1). The Phi-4-mini-flash-reasoning model, which incorporates a decoder-hybrid-decoder architecture with attention and state space model (SSM), exhibits significantly greater computational efficiency—achieving up-to a 10× improvement in throughput when processing user requests with 2K prompt length and 32K generation length. Furthermore, Phi-4-mini-flash-reasoning demonstrates near-linear growth in latency with respect to the number of tokens generated (up to 32k), in contrast to the quadratic growth observed in Phi-4-mini-reasoning. These findings indicate that Phi-4-mini-flash-reasoning is more scalable and better suited for long-sequence generation tasks.

Image: image Image: image

Figure 1. The first plot shows average inference latency as a function of generation length, while the second plot illustrates how inference latency varies with throughput. Both experiments were conducted using the vLLM inference framework on a single A100-80GB GPU over varying concurrency levels of user requests.

Usage#

Tokenizer#

Phi-4-mini-flash-reasoning supports a vocabulary size of up to 200064 tokens. The tokenizer files already provide placeholder tokens that can be used for downstream fine-tuning, but they can also be extended up to the model's vocabulary size.

Input Formats#

Given the nature of the training data, the Phi-4-mini-flash-reasoning model is best suited for prompts using this specific chat format:

<|user|>How to solve 3*x^2+4*x+5=1?<|end|><|assistant|>
Inference with transformers#

List of required packages:

flash_attn==2.7.4.post1
torch==2.6.0
mamba-ssm==2.2.4 --no-build-isolation
causal-conv1d==1.5.0.post8
transformers==4.46.1
accelerate==1.4.0

Phi-4-mini-flash-reasoning is also available in Azure AI Foundry

Example#

After obtaining the Phi-4-mini-flash-reasoning model checkpoints, users can use this sample code for inference.

import torch
from transformers import AutoModelForCausalLM, AutoTokenizer, pipeline
torch.random.manual_seed(0)

model_id = "microsoft/Phi-4-mini-flash-reasoning"
model = AutoModelForCausalLM.from_pretrained(
    model_id,
    device_map="cuda",
    torch_dtype="auto",
    trust_remote_code=True,
)
tokenizer = AutoTokenizer.from_pretrained(model_id)

messages = [{
    "role": "user",
    "content": "How to solve 3*x^2+4*x+5=1?"
}]   
inputs = tokenizer.apply_chat_template(
    messages,
    add_generation_prompt=True,
    return_dict=True,
    return_tensors="pt",
)

outputs = model.generate(
    **inputs.to(model.device),
    max_new_tokens=32768,
    temperature=0.6,
    top_p=0.95,
    do_sample=True,
)
outputs = tokenizer.batch_decode(outputs[:, inputs["input_ids"].shape[-1]:])

print(outputs[0])

Training#

Model#
  • Architecture: Phi-4-mini-flash-reasoning adopts a hybrid SambaY architecture with Differential Attention, featuring 3.8 billion parameters and a 200K vocabulary. It incorporates state space models, grouped-query attention, a gated memory sharing mechanism, a shared key-value cache with a single global attention layer, and shared input-output embeddings.
  • Inputs: Text. It is best suited for prompts using the chat format.
  • Context length: 64K tokens
  • GPUs: Pre-training: 1024 A100-80G; Reasoning training: 128 H100-80G
  • Training time: Pre-training: 14 days; Reasoning training: 2days
  • Training data: Pre-training: 5T tokens; Reasoning training: 150B tokens
  • Outputs: Generated text
  • Dates: Trained in May 2025
  • Status: This is a static model trained on offline datasets with the cutoff date of February 2025 for publicly available data.
  • Supported languages: English
  • Release date: June 2025
Training Datasets#

The training data for Phi-4-mini-flash-reasoning consists exclusively of synthetic mathematical content generated by a stronger and more advanced reasoning model, Deepseek-R1. The objective is to distill knowledge from this model. This synthetic dataset comprises over one million diverse math problems spanning multiple levels of difficulty (from middle school to Ph.D. level). For each problem in the synthetic dataset, eight distinct solutions (rollouts) were sampled, and only those verified as correct were retained, resulting in approximately 30 billion tokens of math content. The dataset integrates three primary components:

  1. a curated selection of high-quality, publicly available math questions and a part of the SFT(Supervised Fine-Tuning) data that was used to train the base Phi-4-mini-flash model;
  2. an extensive collection of synthetic math data generated by the Deepseek-R1 model, designed specifically for high-quality supervised fine-tuning and model distillation; and
  3. a balanced set of correct and incorrect answers used to construct preference data aimed at enhancing Phi-4-mini-flash-reasoning's reasoning capabilities by learning more effective reasoning trajectories

Software#

Hardware#

Note that by default, the Phi-4-mini-flash-reasoning model uses flash attention, which requires certain types of GPU hardware to run. We have tested on the following GPU types:

  • NVIDIA A100
  • NVIDIA H100

Safety Evaluation and Red-Teaming#

The Phi-4 family of models has adopted a robust safety post-training approach. This approach leverages a variety of both open-source and in-house generated datasets. The overall technique employed to do the safety alignment is a combination of SFT, DPO (Direct Preference Optimization), and RLHF (Reinforcement Learning from Human Feedback) approaches by utilizing human-labeled and synthetic English-language datasets, including publicly available datasets focusing on helpfulness and harmlessness, as well as various questions and answers targeted to multiple safety categories.

Phi-4-Mini-Flash-Reasoning was developed in accordance with Microsoft's responsible AI principles. Potential safety risks in the model’s responses were assessed using the Azure AI Foundry’s Risk and Safety Evaluation framework, focusing on harmful content, direct jailbreak, and model groundedness. The Phi-4-Mini-Flash-Reasoning Model Card contains additional information about our approach to safety and responsible AI considerations that developers should be aware of when using this model.

Responsible AI Considerations#

Like other language models, the Phi family of models can potentially behave in ways that are unfair, unreliable, or offensive. Some of the limiting behaviors to be aware of include:

  • Quality of Service: The Phi models are trained primarily on English text and some additional multilingual text. Languages other than English will experience worse performance as well as performance disparities across non-English. English language varieties with less representation in the training data might experience worse performance than standard American English.
  • Multilingual performance and safety gaps: We believe it is important to make language models more widely available across different languages, but the Phi 4 models still exhibit challenges common across multilingual releases. As with any deployment of LLMs, developers will be better positioned to test for performance or safety gaps for their linguistic and cultural context and customize the model with additional fine-tuning and appropriate safeguards.
  • Representation of Harms & Perpetuation of Stereotypes: These models can over- or under-represent groups of people, erase representation of some groups, or reinforce demeaning or negative stereotypes. Despite safety post-training, these limitations may still be present due to differing levels of representation of different groups, cultural contexts, or prevalence of examples of negative stereotypes in training data that reflect real-world patterns and societal biases.
  • Inappropriate or Offensive Content: These models may produce other types of inappropriate or offensive content, which may make it inappropriate to deploy for sensitive contexts without additional mitigations that are specific to the case.
  • Information Reliability: Language models can generate nonsensical content or fabricate content that might sound reasonable but is inaccurate or outdated.
  • Election Information Reliability : The model has an elevated defect rate when responding to election-critical queries, which may result in incorrect or unauthoritative election critical information being presented. We are working to improve the model's performance in this area. Users should verify information related to elections with the election authority in their region.
  • Limited Scope for Code: The majority of Phi 4 training data is based in Python and uses common packages such as "typing, math, random, collections, datetime, itertools". If the model generates Python scripts that utilize other packages or scripts in other languages, it is strongly recommended that users manually verify all API uses.
  • Long Conversation: Phi 4 models, like other models, can in some cases generate responses that are repetitive, unhelpful, or inconsistent in very long chat sessions in both English and non-English languages. Developers are encouraged to place appropriate mitigations, like limiting conversation turns to account for the possible conversational drift.

Developers should apply responsible AI best practices, including mapping, measuring, and mitigating risks associated with their specific use case and cultural, linguistic context. Phi 4 family of models are general purpose models. As developers plan to deploy these models for specific use cases, they are encouraged to fine-tune the models for their use case and leverage the models as part of broader AI systems with language-specific safeguards in place. Important areas for consideration include:

  • Allocation: Models may not be suitable for scenarios that could have consequential impact on legal status or the allocation of resources or life opportunities (ex: housing, employment, credit, etc.) without further assessments and additional debiasing techniques.
  • High-Risk Scenarios: Developers should assess the suitability of using models in high-risk scenarios where unfair, unreliable or offensive outputs might be extremely costly or lead to harm. This includes providing advice in sensitive or expert domains where accuracy and reliability are critical (ex: legal or health advice). Additional safeguards should be implemented at the application level according to the deployment context.
  • Misinformation: Models may produce inaccurate information. Developers should follow transparency best practices and inform end-users they are interacting with an AI system. At the application level, developers can build feedback mechanisms and pipelines to ground responses in use-case specific, contextual information, a technique known as Retrieval Augmented Generation (RAG).
  • Generation of Harmful Content: Developers should assess outputs for their context and use available safety classifiers or custom solutions appropriate for their use case.
  • Misuse: Other forms of misuse such as fraud, spam, or malware production may be possible, and developers should ensure that their applications do not violate applicable laws and regulations.

License#

The model is licensed under the MIT license.

Trademarks#

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.

Appendix A: Benchmark Methodology#

We include a brief word on methodology here - and in particular, how we think about optimizing prompts. In an ideal world, we would never change any prompts in our benchmarks to ensure it is always an apples-to-apples comparison when comparing different models. Indeed, this is our default approach, and is the case in the vast majority of models we have run to date. For all benchmarks, we consider using the same generation configuration such as max sequence length (32768), the same temperature for the fair comparison. Benchmark datasets We evaluate the model with three of the most popular math benchmarks where the strongest reasoning models are competing together. Specifically:

  • Math-500: This benchmark consists of 500 challenging math problems designed to test the model's ability to perform complex mathematical reasoning and problem-solving.
  • AIME 2024/AIME 2025: The American Invitational Mathematics Examination (AIME) is a highly regarded math competition that features a series of difficult problems aimed at assessing advanced mathematical skills and logical reasoning. We evaluate the models on the problems from both 2024 and the year 2025 examinations.
  • GPQA Diamond: The Graduate-Level Google-Proof Q&A (GPQA) Diamond benchmark focuses on evaluating the model's ability to understand and solve a wide range of mathematical questions, including both straightforward calculations and more intricate problem-solving tasks.

Data Summary#

https://huggingface.co/microsoft/Phi-4-mini-flash-reasoning/blob/main/data_summary_card.md

Files

22 files · 7.73 GBWeights 7.71 GB (safetensors). Sizes and sha256 from the signed manifest.
Show all 22 files with their sha256
FileSizesha256
.gitattributes1.92 KBc8d8ba7f2e508149cae8644026e0c3ca58d506f075f7b31dc91af0d099a04ba7
CODE_OF_CONDUCT.md443 Bb1993cedc809d8d310eac55350d8e7043a694a6845611f7312cacd451ea1b5f9
Decoder_Hybrid_Decoder_Architecture_for_Efficient_Reasoning_with_Long_Generation.pdf5.66 MBc5d2a0272700c8b9140b231dab609bde095f605ee8cb9f75e27c914d092f1487
LICENSE1.08 KBfa8235e5b48faca34e3ca98cf4f694ef08bd216d28b58071a1f85b1d50cb814d
NOTICE.md1.77 KB6ac541192c253d21cd16a597ce69c515868e031db3f32f75d996b993b5aca216
README.md21.8 KB38ef838bc08bbfdba10c5144415f4a593ef4d2d85603b4ad366f64cd3c4e4bb5
SECURITY.md2.65 KB689051bc9fa1d207c595bde4ad5940b173638a005b54d709ab3e10cf721f1997
added_tokens.json249 Bd4f2aceb0f20b71dd1f4bcc7e052e4412946bf281840b8f83d39f259571af486
config.json1.03 KBe95d6e3bc4a249d291387cfb34f6e8d7a27e5cb19e8aa0f3842c3883cc1d874f
configuration_phi4flash.py7.57 KB8f0bf8b2eb5aca929354c79bc0f40a183a962a87b0cfb8de0abcffcc63ff4546
data_summary_card.md4.32 KB470514f8d8408e1254c9487401dc4d7d2edb4e08f0453f7bbfb5e01dbb976456
generation_config.json189 B691df727ec361769e2892a1fa77981ce2512e9d1d295db83baaaf18d7c14d5b0
lat.png115 KBf93d3d157e88edd34b9378c9f5dc11fcb2f53f4a61d5b34efbaa5ed9a249a2c4
model-00001-of-00002.safetensors4.95 GB40950ca25f351795db838b458d022d21fd4e92a6d8886a8288885bdd1d6647b0
model-00002-of-00002.safetensors2.75 GB4aa546ac7fcc19373fae0f7b1cc7cb5c289797cfa7a4fc025476613ed3f34440
model.safetensors.index.json35.3 KB582fdbd37d84014890195e32a86c9a9ae9a3ce4e4e16412b2975ebb5b8b5ce1d
modeling_phi4flash.py92.8 KBed32f40d3811ef30aa934783ce3040d8a0110ca0349f811f57504073470a7718
special_tokens_map.json587 Baff38493227d813e29fcf8406e8e90062f1f031aa47d589325e9c31d89ac7cc3
thr_lat.png126 KBed594fb5ebcebeb7649b3ff6493f5b78f28c83adac94334b73c2dbb473608ecd
tokenizer.json9.73 MBe7194c2957acf2c9850759cc635c1ea321024ce4dec55daad2dd12b2263a4521
tokenizer_config.json2.93 KB2d2edbe1a4dfa8d55592eb5504cd4dc059a8c52347551a73386f1d545f1181ce
vocab.json3.91 MB3b5d27b610cd3ad1e4c654b015f6143d24c05c4af6450e490e4540589920b54b
VersionsEach time the pinned upstream commit or file list changed in this repo. Newest first.
Upstream commitDateContents
1dff8163d2 pinned now2026-11-15 03:26 UTC22 files · 7.73 GB

Use it

$ fw get microsoft/Phi-4-mini-flash-reasoning
# manifest sha256 17970a9d5593… · 7.73 GB · 22 files
$ fw verify ./Phi-4-mini-flash-reasoning microsoft/Phi-4-mini-flash-reasoning
fw.pyChecks the signature and every sha256, tries each source in order, resumes.
$ python3 fw.py get https://freeweights.allternit.com/manifests/microsoft/Phi-4-mini-flash-reasoning.json --dir ./Phi-4-mini-flash-reasoning $ python3 fw.py verify ./Phi-4-mini-flash-reasoning ./microsoft__Phi-4-mini-flash-reasoning.json
hfThe Hugging Face CLI with one setting. Same repo id.
$ HF_ENDPOINT=https://freeweights.allternit.com hf download microsoft/Phi-4-mini-flash-reasoning --revision 1dff8163d28ec880ca2411c474ddc0a927792810 --local-dir ./Phi-4-mini-flash-reasoning
transformersLoad the weights in Python.
import os os.environ["HF_ENDPOINT"] = "https://freeweights.allternit.com" from transformers import AutoModelForCausalLM, AutoTokenizer tok = AutoTokenizer.from_pretrained("microsoft/Phi-4-mini-flash-reasoning", revision="1dff8163d28ec880ca2411c474ddc0a927792810") model = AutoModelForCausalLM.from_pretrained("microsoft/Phi-4-mini-flash-reasoning", revision="1dff8163d28ec880ca2411c474ddc0a927792810", device_map="auto")
vLLMServe an OpenAI-compatible API.
$ HF_ENDPOINT=https://freeweights.allternit.com vllm serve microsoft/Phi-4-mini-flash-reasoning --revision 1dff8163d28ec880ca2411c474ddc0a927792810

License

Name
MIT License
Id
MIT
Class
Permissive
Redistribution
yes
Listing
Hosted (signed)
Decided
License as declared by the publisher. No person read it. 2026-11-15
Text in
LICENSE
Text sha256
fa8235e5b48faca34e3ca98cf4f694ef08bd216d28b58071a1f85b1d50cb814d
Terms gate
No extra terms beyond the license.

Read the license text

Licenses are checked against the license table. A custom license passes only after a person reads it.

Provenance

From: microsoft <huggingface.co/microsoft>Newsgroups: alt.freeweights.phiSubject: Phi-4-mini-flash-reasoningDate: 2026-11-15Commit: 1dff816Signed: 2DC28CC7B26A283B ✓
Upstream
microsoft/Phi-4-mini-flash-reasoning
Pinned commit
1dff8163d28ec880ca2411c474ddc0a927792810
Manifest
Phi-4-mini-flash-reasoning.json · .minisig
Manifest sha256
17970a9d5593a81140ec9d90e381ccc4c4f0ded5a426bcce074a3daaefd25fe0
Signature
minisign, Ed25519, key 2DC28CC7B26A283B
Created
2026-11-15 03:26 UTC
Generator
freeweights-manifest/0.1.0
Takedowns
None.

How to verify

$ curl -O https://freeweights.allternit.com/manifests/microsoft/Phi-4-mini-flash-reasoning.json $ curl -O https://freeweights.allternit.com/manifests/microsoft/Phi-4-mini-flash-reasoning.json.minisig $ minisign -Vm Phi-4-mini-flash-reasoning.json -P RWQ7KGqyx4zCLXtUFOqvfv8L3g+8fpKJ1FsuxPyOYMF+4KufbUxKq1Oq $ shasum -a 256 <file> # compare with the Files tab

A manifest whose signature fails must be rejected. A file whose size or sha256 does not match must be discarded. Verify a download

Model tree

No related models in this catalog.Nothing here lists this model as its parent, and it names no parent.
Get it
Download
$ HF_ENDPOINT=https://freeweights.allternit.com hf download microsoft/Phi-4-mini-flash-reasoning
Open in Freeweights Studio

Pull, verify and run it in the Allternit app on Desktop, web or phone.

Signed manifest
minisign, key 2DC28CC7B26A283B. Phi-4-mini-flash-reasoning.json. Provenance. Takedown history: none.
From: BAAI <huggingface.co/BAAI>Subject: bunny-phi-2-siglip-lora
From: microsoft <huggingface.co/microsoft>Subject: MediPhi
From: microsoft <huggingface.co/microsoft>Subject: MediPhi-Clinical
From: microsoft <huggingface.co/microsoft>Subject: MediPhi-Guidelines
From: microsoft <huggingface.co/microsoft>Subject: MediPhi-Instruct
From: microsoft <huggingface.co/microsoft>Subject: MediPhi-MedCode