picview.org

You can cut most images to a fraction of their original file size without any visible quality loss by doing three things in the right order: resize the image to the dimensions it will actually display at, pick the right format for the content, then apply compression at a quality level that survives a side-by-side check. The single biggest mistake is skipping step one — an oversized image compressed at maximum quality is still far heavier than a correctly sized one.

Why file size and quality are a trade-off, not a fixed setting

Every compressed image is a negotiation between three variables: how many pixels you keep, how precisely each pixel is described, and how much the format is allowed to guess.

• Dimensions decide how many pixels exist at all. Halving width and height removes 75% of the pixel data before any compression happens.
• Quality level decides how aggressively the encoder discards detail it thinks you won't notice.
• Format decides the kind of discarding allowed — some formats throw away color precision, others only remove redundancy.

Because these interact, "quality 80" means something different on a 4000px photo than on a 600px thumbnail. Tune dimensions first, then quality.

Pick the format before you touch the quality slider

Practical rule: photos → JPEG or lossy WEBP; flat graphics and transparency → PNG or lossless WEBP; anything vector → SVG.

The four levers, in the order you should pull them

1. Resize to display size (biggest win, zero quality cost)

If your layout renders an image at 800px wide, serving a 2400px original wastes roughly 89% of the pixels. Resize to the largest size it will ever be displayed at, and add a 2× version only if you need retina sharpness.

2. Choose the format

Match the format to the content type using the table above. Converting a photographic PNG to JPEG or WEBP alone can shrink it by 80% or more.

3. Set the quality level

For JPEG and lossy WEBP, most photographs hold up well between quality 70 and 85. Below ~60, banding appears in skies and blur around text. Above ~90, file size climbs steeply for gains nobody can see.

4. Strip metadata

EXIF data, camera info, and embedded thumbnails can add tens of kilobytes. Remove them unless you specifically need copyright or orientation data — and note that stripping orientation can rotate an image, so verify after export.

When lossy compression is fine, and when it isn't

Lossy is acceptable when:

• The image is a photograph or has natural texture.
• It's decorative or below the fold.
• Slight softening won't be noticed at final display size.

Use lossless or vector instead when:

• The image contains text, UI elements, or thin lines (lossy creates ringing artifacts).
• It's a logo, icon, or diagram — SVG or PNG keeps edges clean.
• It will be edited again later; repeated lossy saves compound degradation.
• It's a screenshot of code or a chart where color accuracy matters.

Compressing vs. resizing: don't confuse them

Compressing reduces the bytes needed to describe the same pixels. Resizing reduces the number of pixels. They're independent, and resizing usually delivers the larger saving. A 3000×2000 photo at quality 95 might be 2 MB; the same photo resized to 1200×800 at quality 80 might be 180 KB. Doing only the quality reduction gets you maybe 40% off; doing both gets you over 90%.

A repeatable workflow

1. Determine the maximum display width in your layout (inspect the element or check your CSS).
2. Export at that width (plus a 2× variant if needed).
3. Convert to the right format — WEBP as a modern default, JPEG as a fallback, PNG/SVG for graphics.
4. Apply quality 75–85 for lossy formats and compare against the original.
5. Strip metadata and re-check orientation.
6. Verify before publishing (see below).
7. Serve the right file with srcset so small screens don't download the large variant.

How to verify quality before you publish

• View at 100% at final display size, not zoomed in — artifacts you can't see at real size don't matter.
• Toggle between original and compressed in a viewer or an online compressor's before/after preview.
• Check the worst-case areas: skies, smooth gradients, sharp edges, and any text.
• Compare file sizes and ask whether the extra kilobytes buy visible improvement. If not, go smaller.
• Test on a mid-range phone, where banding and blur are often more obvious than on a desktop monitor.

Common mistakes

• Compressing a full-resolution image and calling it optimized.
• Using PNG for photographs.
• Setting quality to 100 "to be safe" — it inflates size with no visible benefit.
• Re-saving a JPEG repeatedly, stacking artifacts each time.
• Forgetting that GIF animations are usually better as WEBP or video.
• Ignoring metadata, which can silently add weight.

Quick reference

The order matters more than any single setting: resize, then choose format, then tune quality, then strip metadata, then verify at real display size. Follow that sequence and you'll routinely land at 10–20% of the original file size with no quality your visitors can detect.

PicView opens virtually all common image file types plus several specialized ones, and it can browse images stored inside archive and comic book files without extracting them first. It runs on Windows 10/11 and macOS, and is available in both portable and installable versions. The one catch: .7z and .cb7 archives require 7-Zip or WinRAR to be installed on your system.

Image formats

According to the PicView site, the viewer supports "virtually all image file types," including:

• (Animated) WEBP — both still and animated WebP files
• (Animated) GIF
• SVG — vector graphics
• AVIF
• HEIC
• PSD — Photoshop documents
• And many others beyond this list

The animated format support is worth noting: if you work with animated WebP or GIF files, PicView will play them rather than showing only the first frame.

Archive and comic book formats

PicView can load and display images directly inside compressed archives, so you don't need to unpack a file just to look at its contents. Supported archive types include:

• ZIP
• RAR
• CBR (comic book RAR)
• CBZ (comic book ZIP)
• .7z — requires 7-Zip or WinRAR installed
• .cb7 — requires 7-Zip or WinRAR installed

The .7z and .cb7 limitation is the main thing to check before you rely on PicView for those formats. If you already have 7-Zip or WinRAR on your machine, they'll work; if not, you'd need to install one of them first.

What this means in practice

If your image collection spans standard formats, animated files, design files like PSD, and comic book archives, PicView lets you browse them all from one tool instead of juggling a photo viewer, a comic reader, and an archive utility. The archive support is especially useful for comic readers (CBR/CBZ) and for anyone who receives images packaged in ZIP or RAR files.

For .7z and .cb7 specifically, confirm you have 7-Zip or WinRAR installed — otherwise those files won't open in PicView even though the other archive formats will.

Quick reference

If you want to verify a specific format before committing, the fastest check is to download the portable version and open a sample file — no installer or registry changes required.

PicView is a free, customizable picture viewer for Windows 10/11 and macOS. It fits you if you want a fast, lightweight image viewer that opens almost any format, reads images inside archives and comic books, and shows EXIF data without ads, pop-ups, or tracking. It ships in both portable and installable versions, so you can run it without installing anything or writing to the registry.

What PicView is

PicView is an image viewer built around speed and a clean interface. According to its own description, it starts up fast and uses a built-in preloader to switch to the next image instantly. The UI is compact and can be hidden when you just want to see the picture.

It is available for Windows 10/11 and macOS.

Supported formats

PicView supports "virtually all image file types," including:

• (Animated) WEBP
• (Animated) GIF
• SVG
• AVIF
• HEIC
• PSD
• Comic book archives: RAR, ZIP, CBR, CBZ
• Other archive types such as .7z and .cb7 — these require 7-Zip or WinRAR to be installed

Key features

Viewing and navigation

• Fast startup with a preloader for instant next-image switching
• Clean, customizable UI that can be hidden when not needed
• Image gallery with smooth animations that adapt to your screen

Image information

• An Image information window (opened with I by default) that updates as you browse
• Shows file information, printing size, megapixels, and EXIF data such as date taken and GPS location
• If GPS coordinates exist, you can click Google or Bing buttons to open maps at that location

Editing and file management

• Optimize Image button to losslessly compress the current image
• Click stars to save an EXIF image rating
• Rename or move files by editing the corresponding text boxes
• Resize by editing the Width or Height text boxes, or use the % keyboard button to resize by percentage

Batch and archive tools

• Batch resizing
• Image compression
• Image effects
• Viewing images inside archives and comic books

Interface and customization

• Switch between dark and light themes
• Toggle the UI on or off — press Alt + Z to show just the image with no UI
• Hold Shift to drag the window
• Hover buttons and the hover menu can be turned on or off in settings
• Press G to open or close the image gallery; navigate with arrow keys or W, A, S, D, and load a selection with Enter

Portable vs. installable

PicView comes in two forms:

Is it a good fit for you?

PicView is worth trying if you:

• Work with many image formats, including modern ones like AVIF and HEIC
• Need to look inside ZIP, RAR, CBR, or CBZ archives without extracting them
• Want quick access to EXIF data, including GPS locations
• Prefer a portable app that leaves no registry traces
• Want a viewer with no pop-ups and zero tracking

It may be less suited if you need advanced photo editing or a full digital asset management system — PicView is positioned as a viewer with lightweight tools (compression, resizing, effects), not a replacement for a full editor.

PicView's interface customization covers three things you can change without touching config files: the theme (dark or light), whether the UI is visible at all, and whether hover controls appear. The gallery is a separate overlay you toggle with a keyboard shortcut. All of this is documented on the PicView site and works the same way on Windows 10/11 and macOS.

Theme and UI visibility

PicView ships with a dark and a light theme, and you can switch between them. Beyond color, the entire interface can be hidden so only the image remains on screen.

• Toggle the UI: press Alt + Z. Pressing it again brings the interface back.
• Move the window while the UI is hidden: hold Shift and drag.
• Hover controls: the hover buttons and the hover menu can each be turned on or off in the settings window. If you find them distracting while browsing, this is where you disable them.

The practical effect is that PicView can behave like a bare image canvas when you want to look at a photo, and like a normal windowed app when you want to rename, resize, or read metadata.

What the interface gives you access to

Customization is mostly about getting controls out of the way, so it helps to know what you're hiding.

The image information window updates as you browse from one image to the next, so you don't have to close and reopen it between files.

The image gallery

The gallery is an overlay with animated transitions that adapt to your screen size.

• Open or close it: press G.
• Navigate: arrow keys, or W, A, S, D.
• Load the selected image: press Enter.

So the flow is: press G, move through thumbnails with the arrow keys or WASD, then press Enter to open the one you want. This is the fastest path when you're scanning a folder and only want to open a few files.

Where customization stops

Two limits are worth knowing before you commit:

• Archive support has a dependency. Viewing images inside archives works for ZIP, RAR, CBR, and similar formats, but .7z and .cb7 require 7-Zip or WinRAR to be installed. The other archive formats don't have that requirement.
• Portable vs installable is a separate decision. The portable version needs no installer, doesn't write to the registry, and doesn't need external libraries. If you want the app to leave no trace on a machine, that's the version to pick — but it's a different question from how the interface looks.

If your goal is simply a viewer that stays out of the way, the combination of Alt + Z for hiding the UI and disabling hover controls in settings gets you there. If your goal is fast folder browsing, G plus arrow keys or WASD is the workflow to learn.

PicView ships in two builds: a portable version and an installable version. Both run on Windows 10/11 and macOS, and both include the same core viewing and editing features. The practical difference is how they live on your machine: the portable build requires no installer, does not write to registries, and does not need external libraries, while the installable build is meant for a conventional setup on a system you control. Choose portable if you want to carry the app on a USB drive or run it on machines where you cannot install software; choose installable if you want PicView treated like a normal application on your own PC.

What the portable version actually means

According to PicView's own description, the portable build is "no installer required, does not write to registries, does not need external libraries." In practice that means:

• You launch it from wherever you put it — a folder, an external drive, a synced cloud folder.
• It leaves no registry entries behind, so removing it is just deleting the folder.
• It does not depend on separately installed runtime libraries to start.

This matters most in three situations: locked-down work computers where you lack admin rights, USB sticks you move between machines, and test environments you want to keep clean.

What the installable version is for

The installable build is the standard route when PicView is going to be your everyday viewer on a computer you own. It integrates into the normal Windows or macOS application flow, which is what most people expect from a program they use daily. The source material does not describe installer-specific extras such as file-association handling or auto-update behavior, so do not assume features beyond a normal installation.

Feature comparison

The feature set is identical in both builds: virtually all image types including animated WEBP, animated GIF, SVG, AVIF, HEIC, and PSD; comic book archives (RAR, ZIP, CBR, CBZ); EXIF metadata display; image compression; batch resizing; viewing images inside archives; image effects; and galleries. Note that .7z and .cb7 archive support requires 7-Zip or WinRAR to be installed — that dependency applies regardless of which build you pick.

How to decide

Ask one question: does this copy of PicView need to travel, or does it need to settle in?

• Travel → portable. You keep it on removable or synced storage, run it on any Windows 10/11 or macOS machine, and leave nothing behind.
• Settle in → installable. It becomes a regular part of your system on a computer you manage.

If you are unsure, start with portable. Because it writes nothing to the registry and needs no external libraries, trying it costs you nothing but a folder — and you can switch to the installable build later without losing anything, since the features are the same.

Common sticking points

• Archive formats beyond ZIP/RAR: .7z and .cb7 need 7-Zip or WinRAR present. This is true for both builds, so it is not a reason to prefer one over the other.
• Assuming portable means limited: it does not. The portable build carries the full feature set, including EXIF display, compression, batch resizing, and gallery view.
• Assuming installable adds features: the source describes no install-only capabilities. Pick based on deployment, not on a feature gap that is not documented.