What is the PIF file format?
The .pif file format takes its name from Program Information File. This file extension is related to MS-DOS as well as the Windows operating system, specifically the settings needed to run a 16-bit DOS program inside a Windows multitasking environment.
.pif files are mainly used as a shortcut or configuration wrapper pointing to an original .exe, .com, or .bat file. They store settings such as the window title, path to the executable, start directory, memory allocation (minimum and maximum kilobytes), screen mode, and - in later versions - DPMI memory and font preferences. The .pif format itself contains no executable code and is not a program.
The format originated with IBM TopView in 1984 and was adopted by Windows 1.0 (1985). It evolved through Windows 3.x and Windows 9x/NT/2000/XP, gaining extended blocks for 32-bit and NTVDM settings. Windows Vista and later no longer support .pif as a native shortcut type; the .lnk shortcut format introduced in Windows 95 is its effective successor.
Security note: Windows XP and earlier treated .pif files as executable - double-clicking one would launch the target program. Explorer also hid the .pif extension by default, so a file named photo.jpg.pif appeared as photo.jpg, a technique exploited by malware. This attack vector no longer applies on Windows Vista and later.
Security & safety
RISK: MEDIUMOn Windows Vista and later, PIF files are essentially inert and pose minimal risk. On Windows XP and earlier, PIF files were a known malware delivery vector: malicious EXE payloads were distributed as .pif files which Explorer would execute on double-click while hiding the .pif extension (showing only the fake .jpg/.pdf name). If you receive a .pif file via email or download from the internet, treat it with caution - it may be a legacy attack artifact. Modern antivirus software flags suspicious PIF files.
Format details
in a nutshellPrograms that open PIF files
Windows2 apps
Microsoft Windows (XP and earlier)
Paid On Windows XP/2000: double-click launches the target DOS EXE with stored settings. Right-click → Properties opens the PIF editor to modify settings. NOT supported on Windows Vista+.
Any text/hex editor (inspection only)
Free Open PIF in a hex editor (HxD) to inspect the binary structure and identify the embedded EXE path. The EXE path starts at byte offset 30 in the first block. Technical details
deep spec| Encoding | Binary (fixed-size block structure) |
| Byte order | Little-endian |
| Base block size | 960 bytes (original TopView-compatible block) |
| Extended format size | 1 KB - 2 KB with Windows-specific extension blocks (font, screen, DPMI, environment settings) |
| Executable code | None - PIF contains configuration data only; no MZ executable header present |
| Stored parameters | Window title (30-byte ASCII), EXE path, start directory, min/max memory (KB), screen/video mode flags |
| Format origin | IBM TopView (1984); adopted by Microsoft Windows 1.0 (November 1985) |
| OS compatibility | Windows 1.0 through Windows XP; not recognized as a shortcut type in Windows Vista and later |
| Successor format | .lnk shell shortcut (Windows 95+) |
| MIME type | application/x-msdos-program |
| Magic bytes | No universal signature; ~15% of files start with 0x00 0x78; MZ (4D 5A) executable header is absent |
| Legacy security risk | Windows XP and earlier executed PIF on double-click; Explorer hid the extension, enabling malware disguised as image files |
| Released | 1984 (IBM TopView; inherited by Windows 1.0, 1985) |
| Latest version | Extended PIF format used through Windows XP/2003 (Windows 7+ no longer use PIF) |
PIF conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about PIF files.
