Install, configure, and learn what VERI-fy will not do.
Short and to the point. The product itself shows you most of what you need; this is the rest.
Install on Windows
Download, verify the SHA-256, get past SmartScreen, accept the consent dialog. Five minutes.
ReadGet a Gemini API key
Use Google AI Studio. Paid tier recommended for sensitive content. Paste it into the sidebar; it lives in RAM.
ReadmacOS Screen Recording (dev build)
TCC, Cmd+Q, relaunch. The honest walkthrough.
ReadTroubleshooting
Empty captures, rate limits, grounding fallbacks, blank verdicts.
ReadLimitations
What VERI-fy will get wrong, and how to use it anyway. Required reading.
Read
Install
Get VERI-fy on Windows.
- Download the installer from the Download page. Roughly 82 MB.
- Verify the SHA-256. Open PowerShell:
Compare to the SHA-256 published on the Download page.Get-FileHash .\VERI-fy-Setup-1.0.0-alpha.1.exe -Algorithm SHA256 - Open the installer. SmartScreen flags it as unrecognized; see the Download page for the one-time bypass. Code signing is on the v1.0 release blocker list.
- Accept the consent dialog on first launch. This is required and explains exactly what VERI-fy sends to Google.
Gemini key
Bring your own Google Gemini API key.
VERI-fy never holds a key for you. You get one from Google, paste it into the sidebar, and VERI-fy keeps it in process memory until the app closes.
- Create a key at aistudio.google.com/apikey. The string starts with
AIzaSy. - Choose a tier deliberately. Free tier permits Google to train on your screenshots. Paid tier does not, with a 55-day abuse-monitoring retention. We recommend paid for sensitive content. Read the full posture on the Trust page.
- Paste in the sidebar. VERI-fy validates it on first scan. Stored in RAM only; never written to disk.
Rate limits
macOS dev build
Screen Recording permission, the honest version.
macOS gates desktop capture behind the Screen Recording permission. It is keyed to the bundle identifier, which means a development build of VERI-fy needs the permission re-granted every time the underlying Electron build changes. Until the macOS public build ships, the flow is:
- When prompted, click Open System Settings in the in-app banner, then enable Screen and System Audio Recording for Electron.
- Quit VERI-fy with Cmd+Q. Closing the window is not enough.
- Relaunch. The banner clears. Click ACTIVATE VISION AI.
Stuck?
tccutil reset ScreenCapture com.github.Electron, then quit and relaunch. VERI-fy will trigger the permission prompt again on the next scan.Troubleshooting
A short list of things that go wrong, and what to do.
- The verdict is stuck on "Analyzing…"
- Most likely a network issue or an invalid API key. Check your key in the sidebar; a valid key starts with
AIzaSyand is at least 35 characters. If correct, check your network: the only domain VERI-fy hits isgenerativelanguage.googleapis.com. - "Web search context" never appears
- Web grounding is opt-in (toggle in the sidebar) and only runs when the model self-flags needs_grounding. If the toggle is on and grounding still does not run, your model/key combination may not support the tool, VERI-fy detects this on the first 400 and disables grounding for the session, falling back to verdict-only scans.
- Capture returns an empty frame
- On macOS, this almost always means the Screen Recording permission was granted but not yet applied. Quit with Cmd+Q and relaunch. On Windows, ensure VERI-fy is allowed by the active screen-capture policy if you are on a managed device.