Download

Get Flint

One portable executable for Windows 10/11 (64-bit). No installer, no dependencies, no telemetry. Just download, run and flash.

Latest release

Flint v1.0.4 — grab flint.exe from the releases page. Every release includes the executable plus its SHA-256 checksum.

Download flint.exe All releases

Requirements

OS	Windows 10 or Windows 11, 64-bit
Format	Single portable `flint.exe` — no installation
Privileges	Administrator rights required for flashing, wiping, backup and clone
Install steps	Download → run → done. Everything is stored in your app-data folder; uninstall by deleting the file.

Install from the command line

Prefer your terminal over the browser? Both one-liners download flint.exe from the latest release, verify its SHA-256 checksum, and only keep the file if it matches. PowerShell is the native option on Windows; the curl | bash form is for bash users (Git-Bash / MSYS2 / WSL).

irm https://flintweb.vercel.app/install.ps1 | iex

curl -fsSL https://flintweb.vercel.app/install.sh | bash

Read before you pipe. Running a remote script executes it on your machine — that is true of every irm | iex and curl | bash. The script itself only downloads and checksums the executable, but you should review install.ps1 / install.sh (in the flint-web repository) before trusting it the first time.

Requires public releases. The asset URLs point at github.com/gowthvm/Flint/releases/latest. If that repository is private, the download returns 404 and the installer aborts with a clear message — make the app repo (or a mirror feed) public for this to work.

Verify the download

The release notes publish a SHA-256 checksum for flint.exe. After downloading, verify the file matches before you run it:

certutil -hashfile flint.exe SHA256

Compare the output with the checksum listed on the release page. If they match, the download is intact and untampered.

Windows SmartScreen warning. The executable is currently unsigned, so Windows may show a “Windows protected your PC” dialog when you run it for the first time. This is expected for unsigned open-source tools. Click More info → Run anyway. Verifying the checksum above is the best way to confirm the file is legitimate.

Updating

Flint checks the GitHub release feed about once a week in the background. New releases offer a one-click download that is SHA-256 verified against the published checksum before it's kept, and saved to ~/Downloads/flint-<version>.exe. You can also check manually from the ⋮ menu anytime. See Updates in the manual for details.

Nightly builds

Want the latest commits? Check the CI artifacts on the Actions page or build from source — see the repo README for build instructions. Nightly builds are less tested than releases; don't use them for imaging production hardware.

Report a problem

Found a bug or a fake USB drive that beats verification? Open an issue on GitHub Issues and attach the Export diagnostics file from the History page — it bundles version info, drive list, history and logs into one text file.