Download and build status
No signed public installer has been published yet. NTFS Kit builds and runs locally, but the release gates for a public binary — a frozen commit, Developer ID signing, notarization and hardware read-write evidence — are not complete. This page states what exists instead of pointing at a file that does not.
| Item | Current state |
|---|---|
| Application version | 0.2.5 |
| Platform | macOS 12 or newer |
| Architecture | Apple silicon (arm64) development build; the release pipeline can produce a universal app |
| Signing | Ad-hoc for local testing; no Developer ID signature published |
| Notarization | Not yet submitted |
| Public installer | None |
| Write support | Requires separately installed macFUSE and NTFS-3G |
Build it yourself
The app is written in Go with MyGo Native UI. There is no webview, no JavaScript runtime and no cgo dependency.
# Repository root
go tool mygo doctor
make lang
make check
CGO_ENABLED=0 go tool mygo build -platform darwin/arm64Packaged output goes to build/darwin-arm64/. The app bundle is NTFS Kit.app; a DMG is produced next to it. Always build with CGO_ENABLED=0.
Requirements
- macOS 12 or newer, with Xcode Command Line Tools.
- Go 1.27.3 or newer (
GOTOOLCHAIN=autois set in the project). - A disposable NTFS volume if you intend to test read-write, repair or format. Do not use your only copy of important data.
Before you distribute a build
- Sign with a Developer ID Application certificate and notarize the DMG. Gatekeeper blocks unsigned builds downloaded from the internet.
- Verify the exact commit and artifact hash, not just the version string.
- Publish checksums next to the artifact and keep the previous manifest available for rollback.
- Do not bundle macFUSE or NTFS-3G. They are separate projects with their own installers, system extensions and licenses.
Driver components are separate
Read-only mounting uses Apple’s native NTFS driver and needs nothing else. Read-write, NTFS repair and NTFS formatting require:
The app detects both, explains missing pieces in Mounting & drivers, and refuses to unmount a volume for a write mount when the drivers are absent.
Verify what you downloaded
When a public build exists, this page will list its SHA-256 next to each file. Check it before opening:
shasum -a 256 NTFS-Kit-<version>-<arch>.dmgA matching checksum proves the file arrived intact; it does not replace notarization or a source review.
Next
- Quick start — build and open the app.
- Mounting and drivers — read-only, read-write and installation boundaries.
- Verify and repair — what ntfsfix can and cannot prove.