Open-source project
mg-chao/snow-apps avatar
mg-chao/snow-apps

Snow Apps: one C++, Qt and Rust monorepo behind Snow Shot and Snow Image Viewer, with three install channels that behave differently

Snow Apps repository, providing source code for Snow Shot and Snow Image Viewer.

7,095 stars460 forksC++NOASSERTION

At a glance

What is it?
mg-chao/snow-apps holds the source for Snow Shot and Snow Image Viewer, built from CMake, vcpkg, Qt and Rust crates with an OCR engine pulled in as a submodule. Installing Snow Shot is easy on Windows x64 and Apple Silicon Macs; the catches are in which channel ships betas, which updater to trust and how the licences split.
Who is it for?
Install Snow Shot from WinGet if you are on Windows x64 and accept beta builds arriving through the same package, or from the Homebrew cask if you are on an Apple Silicon Mac with macOS 15 or later and can approve Keychain prompts. Look elsewhere if you need Linux packages, an Intel Mac build through Homebrew, or a project that will take a feature pull request.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • mg-chao/snow-apps7,095 ★ · +2,055
Star history
Repository2026-09-232026-11-15
mg-chao/snow-apps5k7.1k

2,055 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two desktop apps, one CMake and Cargo tree

Snow Apps is a source repository rather than a single app: it carries Snow Shot and Snow Image Viewer side by side, and the releases are tagged per app, as in v1.4.5_snow-shot. The three most recent tags all belong to Snow Shot, so that is the app most readers arrive for.

GitHub labels the repository C++, and the root confirms a native desktop build: CMakeLists.txt, CMakePresets.json, vcpkg.json and vcpkg-configuration.json, plus .clang-format and .clang-tidy. The UI layer leans on Qt, with ant_design_qt/ and snow_draw_engine_qt/ as separate components. Rust is the other half. snow-crates/ is a Cargo workspace, snow_rust_ffi/ is the FFI layer between Rust and C++, and snow-image-rs/ and snow-draw-engine-gpui/ sit alongside. snow_image/, snow_image_viewer/, snow_shot/ and snow_memory/ hold the app-level code.

The repository also carries AGENTS.md and a .cursor/ folder, so contributors working with coding agents get project instructions out of the box. A row of construction-site symbols near the top of the README is a fair signal that the layout is still moving.

WinGet ships the betas, the planned Scoop package does not

Windows x64 users have two working routes today: the installer on the GitHub releases page, or the WinGet community repository. The WinGet line installs the offline x64 package:

powershell
winget install --exact --id mg-chao.snow-shot --source winget

That package includes published beta versions and the default OCR resources. The consequence is that a WinGet user is on the beta track whether or not they meant to be. For a personal machine that is fine; for a team image where you want only stable builds, it is a reason to pin a version or use the releases page instead.

Scoop is the portable route, and it is not live yet. The commands only work once the submission to Scoop's Extras bucket, tracked as ScoopInstaller/Extras issue 18870, is accepted:

powershell
scoop bucket add extras
scoop install extras/snowshot

The Scoop package follows stable releases only and also carries the default OCR resources. Until the bucket entry lands, the second command has nothing to install.

Under Scoop, the built-in updater is the wrong one to use

Snow Shot has its own updater, and the project tells Scoop users not to use it. Quit Snow Shot, then run scoop update snowshot. Keep the two update paths apart: the package manager owns the install, so the in-app updater should stay unused on a Scoop machine.

Settings and history persist across upgrades and across an ordinary uninstall. That is convenient when you reinstall, and it also means uninstalling does not remove your data. If you are clearing a machine, docs/snow-shot-releases.md has the removal steps and the data locations for the Scoop package; the same file covers upgrades and removal for WinGet.

The Homebrew cask needs Apple Silicon, macOS 15 and a Keychain prompt

On macOS the supported route is a Homebrew cask from the project's own tap, and only for Apple Silicon Macs running macOS 15 or later. The four commands cover install, upgrade and removal:

sh
brew update
brew install --cask mg-chao/tap/snow-shot
brew upgrade --cask snow-shot
brew uninstall --cask snow-shot

Intel Macs and older macOS versions are outside that statement, so owners of those machines have no documented path through Homebrew.

Installation reuses Snow Shot's local signing identity and may ask for Keychain access and macOS privacy permissions. On a personal Mac that means a few dialogs. On a managed Mac where users cannot approve Keychain or privacy prompts, plan for an administrator to approve them, and read the Homebrew installation section of docs-macos-build.md, which covers existing installations, custom app directories and recovery. The repository also has a homebrew/ directory at its root.

Windows ARM64 is a separate build document

Native Windows ARM64 builds and packages get their own guide, docs-windows-arm64-build.md, covering cross compilation, OCR preparation and release validation prerequisites. Read it before assuming the x64 WinGet package is what an ARM64 laptop should run. The OCR preparation step is called out by name, so budget time for it when packaging an ARM64 build.

Linux has no install section in the README. The build system is CMake and Cargo, so building from source is conceivable, but nothing in the repository's install instructions promises it works.

The OCR engine is a submodule with its own nightly toolchain

OCR lives in snow-crates/crates/simd-paddle-ocr-rs/, a Git submodule with its own repository, history, branches and releases. Snow Apps records the exact OCR commit to check out. The submodule is deliberately excluded from the Snow Crates Cargo workspace so it keeps its own pinned nightly toolchain and lockfile, which means its Cargo commands must be run from inside the submodule directory, not from snow-crates/.

A plain clone leaves the OCR directory empty. Initialize it from the repository root:

sh
git submodule update --init --recursive

A fresh clone with git clone --recurse-submodules does this automatically. Submodule updates check out a detached HEAD, so before editing OCR code switch to a branch inside it:

sh
git -C snow-crates/crates/simd-paddle-ocr-rs switch main

OCR changes go to the submodule's own repository first, and only then is the new revision recorded in Snow Apps. Contributors who forget the order end up with a parent commit that points at a revision nobody else can fetch.

GPL-3.0 apps on top of Apache 2.0 components, and no feature PRs

GitHub reports NOASSERTION because the repository is multi-licensed, with scope rules in LICENSE.md. snow_shot/, snow_image_viewer/, snow_image/, snow_rust_ffi/ and snow-crates/ are GPL v3.0 or later. ant_design_qt/, snow_draw_engine_qt/ and the simd-paddle-ocr-rs submodule are Apache License 2.0. Bundled third-party material keeps its upstream licence, with notices in ant_design_qt/THIRD_PARTY_NOTICES.md and snow_shot/THIRD_PARTY_NOTICES.md.

The practical split: you can lift the Qt component kit or the OCR crate into your own project under Apache 2.0 terms, while anything that ships the Snow Shot app itself carries GPL obligations.

Contribution rules are narrow. Only bug-fix pull requests are reviewed; feature PRs are not accepted directly, and feature requests are meant to start as a community discussion. If you need a capability Snow Shot lacks, plan on asking or forking rather than upstreaming it. Releases have been frequent: Snow Shot 1.4.3 on 2026-10-28, 1.4.4 on 2026-10-30 and 1.4.5 on 2026-11-03, with the last push to main on 2026-11-02.

Editorial conclusion

Install Snow Shot from WinGet if you are on Windows x64 and accept beta builds arriving through the same package, or from the Homebrew cask if you are on an Apple Silicon Mac with macOS 15 or later and can approve Keychain prompts. Look elsewhere if you need Linux packages, an Intel Mac build through Homebrew, or a project that will take a feature pull request. Anyone redistributing builds should read LICENSE.md first, since snow_shot/ is GPL-3.0-or-later while the Qt UI kit and the OCR crate are Apache 2.0.

Frequently asked questions

How do I install Snow Shot from Snow Apps on Windows?

Download the installer from the Snow Shot releases page, or install the offline x64 package with WinGet using the id mg-chao.snow-shot. The WinGet package includes published beta versions and the default OCR resources.

Can Snow Shot be installed with Homebrew on any Mac?

The Homebrew cask mg-chao/tap/snow-shot is documented for Apple Silicon Macs running macOS 15 or later. Installation may request Keychain access and macOS privacy permissions.

What licence does the Snow Apps repository use?

It is multi-licensed. snow_shot/, snow_image_viewer/ and snow-crates/ are GPL v3.0 or later, while ant_design_qt/, snow_draw_engine_qt/ and the simd-paddle-ocr-rs submodule are Apache License 2.0.

How should Snow Shot be updated when installed through Scoop?

Quit Snow Shot and run scoop update snowshot, rather than using the app's built-in updater. Settings and history persist across upgrades.

Official sources

  1. Issues
  2. mg-chao/snow-apps on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/mg-chao-snow-apps.svg)](https://hysenlabs.com/projects/mg-chao-snow-apps)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/mg-chao-snow-apps.svg)](https://hysenlabs.com/projects/mg-chao-snow-apps)

Was this useful?