Accelerate Model Deployment on WinML
38
stars
579
commits
Python
primary language
Sep 8, 2026
updated
Windows ML CLI is a command line tool for building portable, performant, and high-quality AI models for Windows ML. It takes you from a source model — whether from Hugging Face or your own pipeline — to a hardware-optimized artifact in a reproducible workflow.
Purpose-built for Windows hardware diversity, the CLI handles conversion, graph optimization, and compilation across AMD, Intel, NVIDIA, and Qualcomm targets. The CLI fits naturally into CI/CD pipelines so teams can validate and ship models easily.
export, analyze, optimize, quantize, compile), or use an auto-generated config with winml build - both produce portable models that run across hardware.<org>/<repo>/<path/to/file>.onnx (e.g. onnx-community/sam3-tracker-ONNX/onnx/vision_encoder_int8.onnx). Supported by winml config, winml build, winml run, winml serve, winml perf, and winml eval.| Component | Details |
|---|---|
| Windows | Windows 11 24H2 or later (required for NPU support; earlier versions work for CPU/GPU) |
| Python | 3.11 |
| Package manager | uv |
| WinML CLI | PyPI |
WinML CLI requires Python 3.11 and is distributed as a Python wheel. We recommend uv for fast, reproducible environment setup.
Windows on Arm: winml-cli supports x64 (AMD64) Python only. On an Arm64 device, install an x64 build of Python 3.11 so
uvresolves thewin_amd64wheels — PyTorch and the Windows ML runtime packages publish nowin_arm64wheels, so native Arm64 Python fails during setup. The x64 interpreter runs under Windows emulation and works normally. Create the environment with an explicit x64 interpreter:uv python install cpython-3.11-windows-x86_64-none uv venv --python cpython-3.11-windows-x86_64-none
1. Create an environment
uv venv --python 3.11
Activate it:
# Windows (PowerShell)
.venv\Scripts\activate
# Windows (Git Bash / WSL)
source .venv/Scripts/activate
2. Install winml-cli
uv pip install winml-cli
3. Verify your environment
uv run winml sys --list-device --list-ep
This command enumerates available compute devices and execution providers on your machine. If an expected device or execution provider is missing, winml sys is the right place to diagnose it. See winml sys for the full flag reference and troubleshooting tips.
Before downloading any models, confirm that winml-cli recognises the model:
uv run winml inspect -m microsoft/resnet-50
💡 Tip: Always inspect before build to catch unsupported architectures early.
uv run winml build -m microsoft/resnet-50 -o resnet_out/ --no-quant
winml build runs all pipeline steps in sequence — export, optimize, quantize. You can start a model build without a config file, or provide one to configure each step in the sequence (see winml config to customize). All intermediate artifacts land in resnet_out/. For more details, see Output Layout - Windows ML CLI.
uv run winml perf -m resnet_out/model.onnx --device auto --iterations 50 --monitor
--device auto lets the CLI resolve the best available device on your machine — NPU first, then GPU, then CPU.
Official WinML CLI releases can collect unlinked pseudonymized usage telemetry
to help improve the product. Telemetry is classified as Optional. A one-time
prompt on your first run asks for consent (default: accept — press Enter to
enable, type n to decline).
Control — edit %USERPROFILE%\.winml\config.json:
telemetry.consent to "disabled" to opt outtelemetry.consent to "enabled" to opt inSee docs/Privacy.md for the full list of what is and is not collected, event schemas, CI auto-disable behavior, and storage locations.
We welcome contributions! Please see the contribution guidelines.
For feature requests or bug reports, please file a GitHub Issue.
See CODE_OF_CONDUCT.md.
This project is licensed under the MIT License.
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.
Python
98.1%
HTML
1.8%
Accelerate Model Deployment on WinML
38
stars
579
commits
Python
primary language
Sep 8, 2026
updated
Windows ML CLI is a command line tool for building portable, performant, and high-quality AI models for Windows ML. It takes you from a source model — whether from Hugging Face or your own pipeline — to a hardware-optimized artifact in a reproducible workflow.
Purpose-built for Windows hardware diversity, the CLI handles conversion, graph optimization, and compilation across AMD, Intel, NVIDIA, and Qualcomm targets. The CLI fits naturally into CI/CD pipelines so teams can validate and ship models easily.
export, analyze, optimize, quantize, compile), or use an auto-generated config with winml build - both produce portable models that run across hardware.<org>/<repo>/<path/to/file>.onnx (e.g. onnx-community/sam3-tracker-ONNX/onnx/vision_encoder_int8.onnx). Supported by winml config, winml build, winml run, winml serve, winml perf, and winml eval.| Component | Details |
|---|---|
| Windows | Windows 11 24H2 or later (required for NPU support; earlier versions work for CPU/GPU) |
| Python | 3.11 |
| Package manager | uv |
| WinML CLI | PyPI |
WinML CLI requires Python 3.11 and is distributed as a Python wheel. We recommend uv for fast, reproducible environment setup.
Windows on Arm: winml-cli supports x64 (AMD64) Python only. On an Arm64 device, install an x64 build of Python 3.11 so
uvresolves thewin_amd64wheels — PyTorch and the Windows ML runtime packages publish nowin_arm64wheels, so native Arm64 Python fails during setup. The x64 interpreter runs under Windows emulation and works normally. Create the environment with an explicit x64 interpreter:uv python install cpython-3.11-windows-x86_64-none uv venv --python cpython-3.11-windows-x86_64-none
1. Create an environment
uv venv --python 3.11
Activate it:
# Windows (PowerShell)
.venv\Scripts\activate
# Windows (Git Bash / WSL)
source .venv/Scripts/activate
2. Install winml-cli
uv pip install winml-cli
3. Verify your environment
uv run winml sys --list-device --list-ep
This command enumerates available compute devices and execution providers on your machine. If an expected device or execution provider is missing, winml sys is the right place to diagnose it. See winml sys for the full flag reference and troubleshooting tips.
Before downloading any models, confirm that winml-cli recognises the model:
uv run winml inspect -m microsoft/resnet-50
💡 Tip: Always inspect before build to catch unsupported architectures early.
uv run winml build -m microsoft/resnet-50 -o resnet_out/ --no-quant
winml build runs all pipeline steps in sequence — export, optimize, quantize. You can start a model build without a config file, or provide one to configure each step in the sequence (see winml config to customize). All intermediate artifacts land in resnet_out/. For more details, see Output Layout - Windows ML CLI.
uv run winml perf -m resnet_out/model.onnx --device auto --iterations 50 --monitor
--device auto lets the CLI resolve the best available device on your machine — NPU first, then GPU, then CPU.
Official WinML CLI releases can collect unlinked pseudonymized usage telemetry
to help improve the product. Telemetry is classified as Optional. A one-time
prompt on your first run asks for consent (default: accept — press Enter to
enable, type n to decline).
Control — edit %USERPROFILE%\.winml\config.json:
telemetry.consent to "disabled" to opt outtelemetry.consent to "enabled" to opt inSee docs/Privacy.md for the full list of what is and is not collected, event schemas, CI auto-disable behavior, and storage locations.
We welcome contributions! Please see the contribution guidelines.
For feature requests or bug reports, please file a GitHub Issue.
See CODE_OF_CONDUCT.md.
This project is licensed under the MIT License.
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.
Python
98.1%
HTML
1.8%