Release desk

Download IrfanView with a clear integrity plan

This page is structured for teams who need more than a single button. You will see what a current line version looks like in public listings, how to think about hashes and signatures, and how to interpret antivirus chatter calmly.

Download Windows installer

Each button opens a fresh direct download link from the approved distribution endpoint.

Primary download actions

Each action opens a direct download link with a fresh token from the approved distribution endpoint.

Windows installer

Full setup package for standard deployments on approved mirrors.

Download installer

Plugin bundle

Codec and format extensions matched to your viewer build policy.

Download plugin bundle

Language pack

Localized UI resources when your rollout standardizes non-English desks.

Download language pack

Version snapshot

Latest version snapshot

4.73

Windows

Version numbers change over time. Confirm the current build and filename on the distribution channel you approve internally before you record a change ticket.

Installer naming pattern

iview473_setup.exe

style names appear in community mirrors

Exact filenames vary by mirror packaging. Match filename, size, and hash as a set.

Integrity

Source transparency

Portals often repackage files. Some add download managers. Others inject optional offers. That is why enterprises prefer a single approved origin, store the hash at release time, and compare after download. If two mirrors disagree on hash, treat the file as untrusted until reconciled.

SHA-256 and SHA-1 roles

A published hash is a fingerprint. When your tool computes the same hash on disk, you have strong evidence the bits are unchanged versus the publisher listing. SHA-256 is the modern default for new documentation. SHA-1 may still appear on older pages for backward compatibility, but it is weaker over the long term.

Authenticode signatures

Windows code signing binds an identity to an executable at release time. Signatures reduce tampering risk and help SmartScreen build reputation. Signing still does not replace reading release notes, because legitimate publishers can ship optional bundles you may not want.

Example hash fields copied from public listings

Use your own verification commands on the final file you keep.

SHA256: 0a43505ce79ae9401324af304f0bde22d1dd4d00f27dff0cccf62cb7022b770d
SHA1: 5fa7d765ea74ceed5809d745652973fd14287fde

These values appeared in third party security summaries for a specific packaged file name. Recompute on your own bytes before you trust the match.

Antivirus false positives

Compressed executables, self extracting stubs, and download wrapper technologies sometimes trip heuristic engines. A detection label that mentions generic packed behavior is not automatically malware. Escalate with hash evidence, multi scanner comparison, and an isolated lab machine rather than guessing from one flag.

Read the Defender workflow

Security and integrity checklist

Download from an approved internal mirror or vendor location only.
Store expected hash and filename in your change ticket.
Verify hash before deployment, not after installation.
Capture SmartScreen and antivirus responses for the ticket archive.
Install plugins from the same policy channel as the base app.

Trust and ethics statement