Browse 100,000 photos.
At the speed of thought.

It borrows techniques from game development to stay fast - not a classic document viewer. It only ever loads what you’re about to see - a beat before you see it - reuses memory instead of re-allocating it, and does the heavy decoding on background threads under a strict time budget so the interface never freezes. The grid is virtualized: only the tiles on screen actually exist. None of it is exotic - it’s ordinary game- and demoscene craft that most photo tools never applied, because they were never built for 100,000 files in one folder. And for all the game-engine internals, it stays a proper, well-behaved Windows app: it integrates cleanly with Explorer’s “Open with” and your file associations, and multitasks politely alongside Lightroom and everything else - no fullscreen takeover, no runaway memory.

Two hard limits: HDDs are not supported - FlashView works heavily in parallel and spinning-disk heads can’t keep up. And weak hardware: old CPU, low RAM. Large, high-resolution JPEGs on an underpowered machine will eventually feel sluggish - usually still faster than other tools, but at that point it’s physics.

FlashView works purely locally. Single network call: the update check, once per day - it lets you know in a friendly way when a new version is out.

Because you already own the compute. The trend is to offload work to the cloud - even though the machine on your desk is fast and mostly idle. FlashView goes the other way and puts that power back to work locally: no upload wait, no server round-trip, no monthly fee for processing that runs in milliseconds on hardware you’ve already paid for. The cloud is great for sharing; culling 100,000 frames is a job for the box in front of you.

Yes. The installer and portable ZIP are digitally signed by a verified publisher - Mathias Mischler, whose identity was verified by Microsoft (Trusted Signing). On brand-new versions Windows may still show a one-time “Windows protected your PC” notice until they build up download reputation; just click More info → Run anyway. You can verify the signature yourself: right-click the file → Properties → Digital Signatures.

As standard XMP. Inside the file for JPEGs, as an XMP sidecar next to the file for RAW. No proprietary database, nothing you can’t later get out of.

No. FlashView works on folders only - no database, no catalog, nothing to import. Ratings are stored as XMP: inside the file for JPEG, as an XMP sidecar next to the file for RAW. Readable in and out of any XMP-compatible tool (Lightroom, Bridge, Capture One).

For most of a shoot, yes. FlashView now covers the whole chain itself: import from the card (a folder per shooting day, renaming, checksum-verified copy), view, cull, edit non-destructively and export - no catalog, no database, nothing to import into. Viewing and culling are exactly where Lightroom’s Library is slowest, and that is what FlashView is built for. You hand off to Lightroom when you need its depth: lens profiles, masking, extreme recovery, catalog management. Thanks to standard XMP your stars, colors and flags are already there the moment you open the shoot. If a single frame needs Photoshop, it goes over as a PSD and comes back recognized automatically. And if you cull with models or external reviewers, StarRate (our Nextcloud plugin) folds their ratings back into the same XMP. The whole way, step by step →

Lightroom Classic stores color labels in the UI language: German Lightroom expects “Rot, Gelb, Grün …”, everything else (English Lightroom, Bridge, digiKam, Capture One, darktable) the English values. If FlashView writes the wrong variant, the tool doesn’t recognize the label - Lightroom shows a white flag, other tools show nothing or the wrong color. Fix: Settings → General → Metadata → Color labels compatible with - set this to your main tool. On first launch FlashView guesses based on UI language. Reading works either way. Rating and flagging in the manual →

RAW preview uses the embedded JPEG from the RAW file - not the full RAW resolution. Canon, Nikon and Sony are tested extensively and run nearly as fast as JPEG. Other formats (DNG, RAF, RW2, ORF, PEF, 3FR, FFF, SRW) work too. Deliberate choice: more than enough for viewing and review, and orders of magnitude faster than full RAW decoding. More on RAW vs JPEG →

Yes. Open a RAW in the edit mode and FlashView develops it with a real raw engine - demosaiced, 16-bit linear, as-shot white balance - and gives you white balance, exposure, tone curve and saturation on that data, plus looks, denoise and detail. A wide range of RAW formats is supported - Canon, Nikon, Sony, Fujifilm, Panasonic, Olympus, Pentax, Hasselblad, Samsung and Adobe DNG; the manual lists them in detail. The first open of a large RAW takes a moment (around a second on a fast machine, longer on a mini-PC); after that the sliders respond as you drag. Nothing is ever written into the RAW itself - the recipe lives beside it and stays reversible. For lens profiles, masking or extreme recovery, a dedicated converter still goes further. Developing RAW in the manual →

Two different things, often confused.

Recursion (key R): scans all subfolders, no depth cap. There’s no mode that limits this - deliberate, because a photo folder either contains the images you want or it doesn’t; nesting depth doesn’t change that.

Group depth (toolbar / settings): controls the visual grouping in the grid, not the scan. Only active when “Group images by folder hierarchy” is enabled in settings. Defines which folder level becomes the divider: at depth 1, all images from “2025/*” sit together in one block; at depth 2, each shoot gets its own group - all images from “Wedding-Mueller” land together in the grid, separated from the next shoot. Does not limit how deep the scan goes. Folders and groups in the manual →

Three levels. Standard (480 px) is the recommended default - sharp previews at a balanced cache size. Performance (320 px) is best for slower computers and uses the least disk space. Hi-Res (640 px) gives the sharpest, most detailed previews - ideal for high-resolution and 4K monitors, at the cost of more cache. Switch any time via Settings → Display → Thumbnail.

Yes, a thumbnail cache - otherwise previews would have to be re-decoded every time you switch view. The cache lives locally and holds only generated thumbnails, none of your images or data. Size is shown in Settings; you can clear it there anytime.

FlashView works purely in sRGB - no profile conversion, no color management pipeline. Above all, that’s a speed decision.

The cloud icon marks files that currently live only in your cloud storage (OneDrive, Nextcloud, Dropbox, iCloud …) and haven’t been downloaded locally yet. To build a thumbnail, FlashView would have to download the original first - so by default it skips them, otherwise opening a large folder would silently pull gigabytes from your cloud.

You control this under Settings → Cloud-Thumbnails with three modes:
Off - cloud-only files are never downloaded (default, safest).
Preview - loads thumbnails for a limited number of cloud files (2, 4, 6, 8 or 12, set via “Preview count”) so you get a feel without pulling everything.
Load all - fetches every cloud-only original to build thumbnails. Heads up: on big libraries that quickly turns into many GB of local disk and cloud traffic.

Windows - and for now Windows only. Windows is by far the most common desktop, and that’s where the powerful hardware sits - many cores, lots of RAM, capable GPUs - mostly idle. That’s exactly the power FlashView puts to work instead of offloading it to the cloud. So we focus there.