What is the OVR file format?
An .ovr file is an MS-DOS Program Overlay - a binary x86 code segment designed to be loaded into memory on demand by a host .exe program, rather than remaining resident at all times.
DOS overlay files solved the 640 KB conventional memory ceiling that constrained all MS-DOS applications. A large program split its code into a main .exe (always in memory) and a set of .ovr overlay modules containing infrequently used functions - menus, spell-checker, help screens, and similar features. An overlay manager stub linked into the host binary loaded the required .ovr module into a fixed shared memory region when needed, swapping it out when a different overlay was required. WordStar 4 and later shipped several overlay files including WSOVLY1.OVR and WSMSGS.OVR; dBase and Turbo Pascal applications commonly used the same technique.
.ovr files are raw x86 binary code with no universal header or magic bytes. The internal layout depends entirely on the compiler or linker that produced them. Turbo Pascal's {$O+} overlay directive generated .ovr files with a small per-unit fixup table prepended; Borland and other vendors used incompatible formats. An .ovr file from one toolchain cannot be loaded by another.
An .ovr file is entirely inert without its matching host executable - it cannot be run standalone. EMS/XMS extended memory support and 32-bit protected-mode runtimes (such as DOS/4GW) made overlays obsolete by the early 1990s. Today .ovr files appear only in abandonware archives and can be explored using DOSBox or DOSBox-X emulators.
Security & safety
RISK: LOWDOS OVR files contain x86 machine code but cannot execute on modern 64-bit Windows/macOS/Linux directly (real-mode x86 code, no PE/ELF header). Risk is effectively zero outside DOSBox, where the sandbox limits damage. The AbleNet variant is a data file, not executable.
Format details
in a nutshell- AbleNet Overlay Maker Board File - AbleNet's Overlay Maker (AAC/education tool for creating communication boards) saves overlay board layouts as .ovr files - completely unrelated to DOS overlays; XML or binary proprietary format.
- The Overlay Maker (GIS/military drawing) - A networked GIS drawing program for military planning also uses .ovr for its drawing overlay files; these reference map graphics and annotations but not the resource files themselves.
Programs that open OVR files
Technical details
deep spec| Format type | Binary x86 machine code overlay segment (raw, no container format) |
| Encoding | Binary, little-endian (x86 machine code or compiler p-code) |
| Typical file size | 2 KB - 256 KB (kept small by design to minimize disk I/O) |
| Memory model | Loaded into a fixed shared overlay area in conventional DOS memory (below 640 KB); multiple .ovr modules share the same address range |
| Toolchain dependency | Internal layout is entirely compiler/linker-specific - Turbo Pascal OVR is incompatible with Borland Linker OVR and other formats |
| Turbo Pascal specifics | Enabled by the {$O+} compiler directive; each unit's overlay segment is prepended with a fixup table for address patching |
| Notable users | WordStar 4+ (WSOVLY1.OVR, WSMSGS.OVR), dBase, Turbo Pascal applications |
| Standalone execution | Cannot be executed independently - inert without the matching host .exe and its linked overlay manager stub |
| Target platform | MS-DOS and PC-DOS (8086 through 80286 era programs) |
| Obsolescence cause | EMS/XMS extended memory support and 32-bit protected-mode runtimes (DOS/4GW, Windows PE) eliminated the need for overlays by the early 1990s |
| Discovery context | Found only in abandonware archives; functional only inside DOSBox or DOSBox-X emulators |
| Released | Early 1980s (DOS era, common practice by 1983-1985) |
| Latest version | N/A (format is defunct; no versioning) |
OVR conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about OVR files.