Release trust
Download Safety for VeloWrite Preview Builds
By KenRich · Last updated: August 15, 2026
VeloWrite preview installers are still unsigned. Use this checklist to download from the right place, confirm the version, and report anything that looks wrong.
Download only from the official page
Use velowrite.app/download. That page shows the current preview version, platform package names, release date, and notes before you install.
Avoid random mirrors, reuploaded installers, shortened links, and files shared in chat. While VeloWrite is unsigned, the safest habit is to start from the official download page every time.
Check the version before installing
The download card, file name, changelog entry, and desktop About panel should all point to the same version. If the website says v0.3.0, the installer file and About panel should also show v0.3.0.
If a fix is mentioned in the changelog but the installer version is older, wait for the next public release or use the web editor where website fixes are already live.
## Before installing
- Download page version: v0.3.0
- Installer file name: VeloWrite_0.3.0...
- Desktop About panel after install: 0.3.0Before installing
- Download page version: v0.3.0
- Installer file name: VeloWrite_0.3.0…
- Desktop About panel after install: 0.3.0
NoteA simple version match catches most stale-download confusion.
Unsigned installer warnings are expected for now
Windows SmartScreen and macOS Gatekeeper may warn because the current preview builds are not code-signed or notarized yet. That is a trust limitation of the preview, not a feature users should ignore forever.
The current workaround is to verify the source and version before installing. Paid signing and notarization remain release trust work for a later budget stage.
Test with a copy of a Markdown file first
Open a copied Markdown file, switch between Write, Split, and Preview, save once, export HTML or PDF, then reopen the file and check History. This tests the core desktop path without putting your only copy at risk.
Keep important files in a folder you already back up. VeloWrite local history helps with recent edits, but it is not a replacement for Git, Time Machine, Windows File History, Syncthing, or a normal cloud-drive backup.
Stop if anything looks inconsistent
Do not install if the file name, version, release page, or source link does not match what the download page says. Do not keep using a build if it cannot close, save, reopen, or export a simple test document reliably.
If you already installed an old VeloMD preview, uninstall it separately so old shortcuts do not make it look like VeloWrite installed twice.
Report download or install issues with the exact file name
When reporting a download issue, include your operating system, installer file name, version shown in About, where you downloaded it, and what warning or error appeared.
That information makes the issue actionable. It also helps keep the public download page honest when a build asset, release note, or platform package falls behind.