Not every PC lets you install software. Work machines, lab computers, a client’s laptop, a shared family PC — all places where you might need to check a Gerber file quickly but cannot (or should not) run an installer. Gerbv v2.13.0 has an answer built into the release itself: alongside the NSIS installer, the project publishes an MSYS2 UCRT64 ZIP build that runs from an extracted folder with no installation at all. This guide explains what that ZIP is, how it differs from the installer, how to verify and run it, and when each Windows build is the right choice. Both builds are official, free (GPL-2.0-or-later), and listed on the download page.
Two Windows builds, two build systems
The v2.13.0 release notes describe the pair plainly: the project now makes two Windows variants. One is cross-compiled on Fedora and packaged with the NSIS installer — that is gerbv-2.13.0-win64.exe, the build covered in our Windows installation guide. The other is built natively on Windows with MSYS2, using the UCRT64 toolchain, and shipped as a plain ZIP archive. MSYS2 is a Windows software-building environment, and UCRT64 refers to its build profile targeting the Universal C Runtime on 64-bit Windows. The practical consequence of the ZIP packaging is what matters here: no setup wizard, no registry-driven install step, no uninstaller — just a folder of files that includes the gerbv executable and the libraries it needs.
The file: name, size and checksum
The portable build’s asset name is long but exact: gerbv_v2.13.0_.Windows.MSYS2.UCRT64.zip, at 17,962,489 bytes (about 18 MB — slightly larger than the 15 MB installer, which is typical for a self-contained folder). Download it via /go/gerbv-win-zip, which redirects to the official v2.13.0 asset on GitHub Releases. Before extracting anything, verify the archive in PowerShell:
Get-FileHash .\gerbv_v2.13.0_.Windows.MSYS2.UCRT64.zip -Algorithm SHA256The result must match the published SHA-256:
bb77865da031df83482196a6f6e9fa98298433979d995c068c4533b9b5a9ee7dIf it does not match, delete the file and download it again from the official release. Verifying matters doubly for a portable build, because a folder that can be copied anywhere can also be copied from anywhere — the checksum is how you know your copy is the project’s build and not a repackaged one.
Extract and run
Right-click the ZIP and choose Extract All (or use your archiver of choice), putting the folder somewhere you can write to — your Documents folder, a tools folder on a second drive, or a USB stick. Then open the extracted folder and run the gerbv executable inside it. That is the whole setup. Gerbv opens with its layer list ready: load your Gerber RS-274X layers, Excellon drill file and CSV pick-and-place file from the File menu, and you are viewing the board. When you are done, closing the program leaves nothing running, and deleting the folder removes the “installation” completely.
One expectation to set: because the ZIP bypasses the installer, Windows SmartScreen may comment on the unsigned executable the first time you run it, just as it can with the installer. The checksum verification above is the step that lets you treat that prompt sensibly — as general guidance, with a verified file you can choose More info, then Run anyway. Both Windows builds are 64-bit and Windows 10 is the tested platform; on Windows 7, neither v2.13.0 build applies — upstream supports Windows 7 only up to v2.8.0, as the version history explains.
When portable beats the installer (and when it doesn’t)
Choose the ZIP build when you cannot install software (no administrator rights, a managed work PC), when you want Gerbv on a USB stick for the lab bench or a client visit, when you are evaluating the program and want a zero-commitment trial, or when you want two side-by-side copies — for example the release build and a fresh download — without them interfering. Choose the NSIS installer for your own main machine: it integrates with the Start menu, associates itself properly in the system, and can be removed through Windows’ normal app management. Feature-wise there is nothing to choose between them: same viewer, same RS-274X/Excellon/CSV support, same layer tools, measurement and report windows, same PNG/PDF/PS/SVG/DXF export, and the same honest limits — 2D only, no RS-274D, no design-rule checking.
Keeping a portable copy current
A portable folder does not update itself, so staying current is a manual habit: when a new release appears, download the new ZIP, verify its checksum, extract it to a fresh folder, and delete the old one once you are happy. The project’s pace makes this easy to follow — after years of quiet it shipped four releases in three weeks in early 2026, a story told in Gerbv 2.13.0: first native Windows and macOS builds. If you later move to a machine where installing is fine, the step-by-step installer guide covers the NSIS route, and the download page keeps every platform’s file, size and SHA-256 in one table.
Frequently asked questions
Is the Gerbv ZIP build really portable — no installation at all?
Yes. The MSYS2 UCRT64 ZIP from the official v2.13.0 release extracts to a self-contained folder; you run the executable from there, including from a USB stick, and deleting the folder removes it.
What is the difference between the ZIP and the .exe installer?
The .exe is an NSIS installer cross-compiled from Fedora that installs Gerbv system-wide with shortcuts and an uninstaller. The ZIP is built natively with MSYS2 and needs no install. The viewer itself is the same.
How do I verify the portable download?
Run Get-FileHash on the ZIP in PowerShell and compare it with the published SHA-256 bb77865da031df83482196a6f6e9fa98298433979d995c068c4533b9b5a9ee7d (17,962,489 bytes). Only extract and run it if they match exactly.