PhotoCraft Windows releases provide both an MSI installer and a portable ZIP. The v0.8.2 release documentation lists x64, arm64 and x86 variants. Choose the architecture first, then the packaging format. You do not need Rust or Visual Studio to run a packaged release; those prerequisites apply when compiling source.
Use the download page for official package links or open GitHub Releases directly. This guide explains the choice and the first checks after installation. It does not promise that every Windows configuration or managed-device policy will allow the application.
Match the processor architecture
Check your device's system information before downloading. A typical 64-bit Intel or AMD computer uses x64. An ARM-based Windows PC uses arm64. The x86 package is the 32-bit variant. If you are unsure, inspect the processor and system type in Windows Settings rather than guessing from the laptop's brand.
| Windows system | Release filename pattern |
|---|---|
| 64-bit Intel or AMD | photocraft-VERSION-windows-x64.msi or corresponding portable ZIP |
| ARM64 PC | photocraft-VERSION-windows-arm64.msi or corresponding portable ZIP |
| 32-bit x86 system | photocraft-VERSION-windows-x86.msi or corresponding portable ZIP |
Replace VERSION with the actual release label when recognizing a filename. The release notes remain the authority for requirements. A package's presence does not establish compatibility with an older Windows version or every graphics driver, so check those notes when your environment differs from a current desktop installation.
MSI installer or portable ZIP?
Use the MSI when you want a conventional installed application and your device permits software installation. Complete the installer, then launch PhotoCraft through the installed entry. On a managed computer, installation may require an administrator-approved process.
Use the portable ZIP when you want an extracted application folder. Extract the entire archive to a location you can write to and launch the executable from that folder. Do not run it while browsing inside the compressed archive, and do not move just the executable away from the files packaged with it.
Portable packaging does not mean the application has no settings, needs no graphics support or bypasses application-control policies. It describes how the program is delivered. If you need a controlled configuration, test its behavior in that environment rather than inferring it from the word “portable.”
Check the download and installation
Confirm the release tag and filename before opening the package. When SHA256SUMS is supplied, compare the downloaded file's hash with its matching entry. PowerShell can calculate a local SHA256:
Get-FileHash -Algorithm SHA256 -LiteralPath '.photocraft-0.8.2-windows-x64.msi'
Change that path to the file you actually downloaded. The command only computes a hash; you must still compare it with the official release entry. The versioned README states that Windows installers and executables are code-signed. If Windows presents a publisher or integrity warning, inspect the file's provenance and the displayed details before proceeding.
Complete a first-launch check
Open a small image copy, make one simple change and save under a new filename. Reopen the saved document and inspect a separate exported PNG or JPEG in another viewer. This checks installation, document loading and the output path without putting your only copy of an important project at risk.
Next, follow the PhotoCraft tutorial to create a layered caption card. Keep the installed release version with your test notes. If your main task involves PSD handoff, add the document checks in PhotoCraft vs Photoshop before adopting it for that task.
Troubleshoot a blocked launch or blank canvas
For an installation or launch error, record the exact message, package architecture and Windows version. Check the official issue tracker for that message. If an application-control policy blocks execution, use the organization's approved software process or development environment. A portable build and a relocated folder do not prove that a blocked file is trusted.
For a graphics problem, distinguish an empty document from a renderer failure. The versioned development guide describes graphics backends and diagnostic information; check Help › System Info when available and include the adapter and backend in a report. Test a small ordinary image before concluding that a complex PSD is the cause.
PhotoCraft is early alpha. Preserve originals and keep an alternative application available for a task that fails your checks. For compilation requirements, use PhotoCraft Rust. For download navigation or a useful bug report, use PhotoCraft GitHub.