Install from Microsoft Store
Install directly from GitHub
1
Download the latest installer
Open the GitHub Releases page and download
VideoCull.Setup.<version>.exe from the latest release.2
Run the installer
Double-click the downloaded
.exe file and choose your install location and shortcut options.3
Handle the SmartScreen prompt
The direct installer is not code-signed yet, so Windows may show a SmartScreen warning. If you downloaded it from the official GitHub repository, click More info, then Run anyway to proceed.
4
Launch VideoCull
Start the app from the Start Menu or the desktop shortcut created by the installer.
System requirements
- VideoCull requires 64-bit Windows 10 version 22H2 (build 19045) or Windows 11. The Microsoft Store edition enforces this minimum.
- The direct installer installs per user, not system-wide, and does not require administrator rights.
- Windows is the primary supported platform.
- End users do not need Node.js.
- FFmpeg and FFprobe are bundled with the app.
Updates and shared data
- Microsoft Store installs and updates the Store edition.
- The direct-download edition checks GitHub Releases when automatic update checks are enabled. It asks before installing a downloaded update.
- Both editions use
%APPDATA%\VideoCullfor settings, review decisions, databases, and the default thumbnail cache. - Only run one edition at a time. VideoCull blocks a second packaged edition from opening the shared profile concurrently.
- Keep both editions updated before switching between them. After confirming the Store edition works, you can remove the direct installation without deleting the shared profile or cache.
- Updating from v2.2.0 renames the old
%APPDATA%\video-cullprofile to%APPDATA%\VideoCull. If Windows cannot rename it, VideoCull uses the old profile for that launch and tries again next time. If both folders already exist, VideoCull uses%APPDATA%\VideoCulland leaves both untouched. You may need to re-pin the renamed app on the taskbar.
Resetting or uninstalling the Store package does not remove the shared profile or default cache. Custom central, per-drive, and distributed caches also remain user-managed.