PicView is a fast local image viewer that also edits and batches files

Opening images fast, then quietly doing more than that

PicView describes itself as a fast, free and fully customizable picture viewer for macOS and Windows 10/11, and the emphasis on speed comes from the architecture rather than a claim. It is written in C# on Avalonia with MVVM and reactive programming, which is what lets one codebase ship as a native Windows x64 and arm64 binary and a macOS arm64 and x64 disk image. Avalonia is a cross platform UI framework, so the macOS build is a first class target rather than a port.

The format list is the other thing that separates it from the Windows Photos app it is usually compared against. The README names animated WEBP and animated GIF, plus SVG, AVIF, HEIC, PSD, and the CBZ and CBR comic archive containers. Animated formats and comic archives are the two entries that matter most in practice, because both are things a general purpose image viewer tends to hand off to another application.

The interface is keyboard driven once you know the keys. G opens and closes the image gallery, arrow keys or W A S D move through it, Enter or E loads the selection, and C crops. The UI can be hidden entirely, and there is a dark and a light theme. For a tool whose whole pitch is that it opens instantly, the keyboard model is the right one.

Installing from a package manager or a portable archive

The README gives four routes and they differ in a way that matters. First, downloadable builds for four targets: a portable Windows x64 zip, a Windows arm64 setup executable, a macOS arm64 disk image and a macOS x64 disk image, all currently pinned to release 5.1.2. PicView.org carries the same downloads plus later releases.

Then the three package managers. Windows users have Scoop and WinGet, and macOS users have Homebrew:

winget install picview

scoop bucket add extras;
scoop install extras/picview

brew install picview

The Scoop route takes two lines because the package lives in the extras bucket rather than the main one, which is the normal convention for apps that are not among the command line tools. The README also lists mirrors on Uptodown, FossHub, SourceForge and Major Geeks. The choice between the zip and the setup executable is a real one: the zip is portable and leaves nothing behind, which suits a portable tools drive, while the installer handles file associations and is what you want if you double-click images in Explorer and expect PicView to be there.

One licensing wrinkle is worth naming. The README badge reads GPLv3 and the tree contains a LICENSE.txt, but the repository metadata reports no recognised licence identifier. Treat the LICENSE.txt file as the authoritative document.

Editing from the info window instead of a second application

The Image Info window is where PicView stops being a viewer. From it you can rename a file, convert it, copy it, compress it, resize it, send it to the recycle bin and set its EXIF rating. Resizing takes width and height as typed values, and appending a percent sign switches that field to percentage scaling.

If an image carries GPS coordinates, the window offers Google and Bing buttons that open those maps at the coordinates. That is a small feature and it is the kind of detail that tells you the author builds from their own photo library rather than from a feature checklist.

EXIF editing is the part that matters most to a photo library, because rating and naming from inside the viewer means you do not have to keep a second tool open to decide whether a shot is worth keeping. The metadata handling is described in terms of what the window exposes rather than how the values are written, so the README does not say which EXIF fields are editable beyond the rating.

Batch resize, convert and thumbnail generation across folders

Batch processing works on every selected file and sends the results to an output folder, which is named with the localized translation of the batch resize label by default. Four dropdowns drive it. Convert to changes the format. Compression either keeps quality or trades some of it for a smaller file. Quality sets how much detail survives. Resize works by height, width or percentage while preserving the aspect ratio.

The thumbnail tab is the more unusual half. It generates up to seven sizes, each resized by height, width or percentage with the aspect ratio kept, and each written to its own folder with a suggested name ordered from small to medium to large. That is aimed at people publishing images at several sizes and who would otherwise script the same pipeline themselves.

Given that the topic list includes batch-processing and convert-images, batch work is a first class feature rather than a side mode. What the README does not document is whether batch operations can be scripted or triggered from the command line, which matters if you want this inside a pipeline rather than beside you.

Version 5.1 spent its effort on motion photos and gallery speed

Three releases are published in September 2026 and they show a project in a bug fix phase rather than a feature sprint. PicView 5.1.0 on 2026-09-12 added native playback for Motion Photos, also called Live Photos, with no third party dependencies, batched archive extraction in groups of ten with a progress indicator, and gallery UI virtualization so folders with hundreds or thousands of images load quickly. It also overhauled the light theme.

The gallery virtualization change is the one with the widest effect. Loading cost in a thumbnail gallery is dominated by decoding images that are off screen, and not decoding them is why browsing a large folder stops stuttering.

PicView 5.1.1 on 2026-09-17 fixed thumbnail rendering when the gallery is docked to the side, and on Windows it added a `picview-ffmpeg.dll` file in a new plugin directory, while the macOS build fixed an unresponsive update button and moved that same DLL. PicView 5.1.2 on 2026-09-22 fixed the application shortcuts not working, the gallery not hiding when an image loaded through a URL, and erratic horizontal gallery scrolling, and updated Avalonia to 12.1.2.

The last two releases being almost entirely corrections is a fair signal about the current state: nothing in them suggests a broken foundation, and quite a lot of small papercuts. The repository is not archived and the last push was on 2026-09-22, the same day as 5.1.2.

The parts the README leaves out, and where to check them

Two gaps are worth naming rather than papering over. First, Linux is not mentioned anywhere. The topics list a macos-app and the README names Windows 10/11 and macOS, and while Avalonia is cross platform by design, there is no Linux build offered or linked, so a Linux user has no documented path.

Second, the README's file support section and the screenshots are cut off partway through in the copy available for review, so the full format list and the renaming options are not something to take on trust. The fix is the same either way: the README links to PicView.org for the complete format table, and the repository tree is small enough to read in one sitting, with `src/` holding the C# sources, `Native/` the native components, `Build/` the build definitions, `agents.md`, `CONTRIBUTING.md` and a `nuget.config` at the root.

A third detail is a mismatch rather than a gap. The repository metadata reports `dev` as the default branch while README links point at `master` paths, including the licence file and the rename screenshot. Both branches can exist, but if you are reading documentation or building from source, check which branch your checkout is actually on before assuming a link resolves to what you expect.

Editorial conclusion

PicView suits someone with a folder of images who wants opening files to be instant and who also wants to rename, crop and batch convert without leaving the same window. It is a poor choice for catalogue browsing at scale, for RAW development, or on Linux, which the README does not list. Before adopting it, download the x64 archive for your platform rather than the installer, since the README offers both a portable zip and a setup executable, and check whether the features you actually want sit behind the Plus naming or in the free build, since version 5.1.0 and 5.1.1 shipped fixes to the free reader while macOS work such as the plugin directory move landed alongside them. The gallery is bound to G and crop to C, so the fastest way to judge it is those two keys.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. Ruben2776/PicView on GitHub