The latest release information could not be retrieved. This is usually the network, or a temporary limit on GitHub's side. What is listed below is v1.0.0, which may no longer be the newest. Check the releases page if you want to be sure.
Windows 10 / 11 (x64)
Recommended for Windows
Installed from the Microsoft Store, it shows no first-launch warning and the Store keeps it updated. On a PC without the Store, use the installer.
macOS 11+ (Apple Silicon)
Recommended for Mac
Apple Silicon only — Intel Macs are not supported. Unzip it and move pictkura.app wherever you keep your apps. The first launch requires an additional step. See the required steps →
All the files
Microsoft Store Recommended
Windows 10 / 11. The Store installs and updates it. If you have used another version of pictkura in the same Windows account, the Store version uses the same library and settings. Moving from the installer version (setup.exe or MSI)? Uninstall it first. The Store version cannot remove the AutoPlay entry the installer version left, so two entries with the same name would appear.
From a terminal: winget install 9N5H2QBMK9NB. This also goes through the Store, so it does not work on a PC where the Store is unavailable.
Windows installer
No administrator rights are needed. It is installed for the current user only (%LOCALAPPDATA%\pictkura), and the installer lets you pick English or Japanese (the app itself follows your OS language, or the one chosen in Settings).
pictkura_1.0.0_x64-setup.exe
Portable ZIP for Windows
Nothing is installed. Unzip it and run pictkura.exe — from a USB stick if you like.
pictkura_1.0.0_x64-portable.zip
Windows, machine-wide (English installer)
To install it for all users of the machine. Asks for administrator rights. If the machine is yours alone, the installer above is enough.
pictkura_1.0.0_x64_en-US.msi
Windows, machine-wide (Japanese installer)
The same build, with the installer in Japanese. The MSI comes as one file per language. The app itself is available in 7 languages either way.
pictkura_1.0.0_x64_ja-JP.msi
Older versions and release notes on GitHub →
Opening it the first time
Apart from the Microsoft Store version, Windows and macOS both warn you the first time, as the application is not digitally signed. The warning means the publisher could not be verified — it is not the result of anything inspecting the contents. Every prompt, screen by screen, is written out in the installation guide, and the material you can check for yourself is under how these files are built. If anything still leaves you unsure after reading it, stop the installation.
On Windows it is "Windows protected your PC" → "More info" → "Run anyway". On macOS it refuses once, and you then allow it under System Settings → Privacy & Security → "Open Anyway".
Windows is 64-bit (x64) only, and the Mac build is Apple Silicon only
Importing relies on Windows and macOS features that have no Linux counterpart here
Already present on Windows 11 and up-to-date Windows 10; where it is missing, the installer downloads it. The Microsoft Store version does not, so use the installer or install the WebView2 runtime first
Installing or removing pictkura never rewrites a photo file. Where they are kept is in the specification
How these files are built
The files here carry no signing certificate, so us telling you it is safe gives you nothing you can check. Here is what you can check instead. The point is not to claim it is safe — it is to leave you able to find out.
Every build is made from the source at its tag. The repository is MIT licensed
The five files come out of a GitHub Actions workflow, and every run of it is on the record
The SHA-256 the command below returns is computed by GitHub from the bytes it stores. It is not a number we typed in
Whether the file you hold is byte for byte what is published here. It is not evidence that the contents are safe
Ask GitHub for the digests it holds. Name the tag you actually downloaded — a copy from somewhere else is not necessarily the newest release, and comparing it against latest would differ for that reason alone:
# v0.2.4 is an example — use the tag of the version you have (it is in the filename) # macOS curl -s https://api.github.com/repos/Harusame64/pictkura/releases/tags/v0.2.4 | grep -E '"name"|"digest"' # Windows (PowerShell) (Invoke-RestMethod https://api.github.com/repos/Harusame64/pictkura/releases/tags/v0.2.4).assets | Select-Object name, digest
Then hash the file you downloaded and compare:
# macOS cd ~/Downloads shasum -a 256 pictkura_*_arm64.zip # Windows (PowerShell) cd ~\Downloads Get-FileHash .\pictkura_*_x64-setup.exe -Algorithm SHA256
Get-FileHash prints the digest in upper case. Drop GitHub's sha256: prefix and compare ignoring case. If nothing at all is printed on Windows, the file is not in that folder — Get-FileHash exits silently, without an error, when the pattern matches nothing (measured on PowerShell 7.6.5).
This comparison earns its keep when the file came from somewhere other than here — a mirror such as Softpedia. If the digest differs, you are holding a file the author has never seen.