What is the DEP file format?
A .dep file is a Visual Basic Setup Wizard Dependency File - a plain-text INI manifest consumed by the Microsoft Visual Basic 5.0 Setup Wizard and the VB6 Package and Deployment Wizard (PDW).
Each .dep file describes the run-time dependencies of a single Visual Basic component such as an .ocx or .dll. Sections are named after the component filename (e.g., [MyOCX.OCX]), and each section lists the files that component requires at run time, their minimum version numbers, how they should be registered (self-registration vs. explicit regsvr32), destination directory codes, and optional source CAB package information.
When the PDW packages a VB6 application for distribution, it reads the master dependency list VB6DEP.INI along with any per-component .dep files to build a complete dependency graph, ensuring every required file ends up in the installer's CAB archives.
.dep files are encoded in plain Windows-1252/ASCII text and typically range from 1 KB to 20 KB. Any text editor - including Notepad - can open them.
The format is completely obsolete. Visual Basic 6.0 extended support ended in April 2008, and the Setup Wizard and PDW are not supported on modern Windows. Microsoft has committed to keeping the VB6 runtime on Windows until at least 2031, but the IDE and packaging tools are no longer functional on current systems. Developers still maintaining legacy VB6 applications are the only people likely to encounter .dep files today; modern deployment uses MSI packages, WiX Toolset, or ClickOnce.
Security & safety
RISK: LOWPlain text INI file; cannot execute code. Lists file paths and registry keys - review contents before using to understand what components a legacy OCX declares as dependencies. No malware vector.
Format details
in a nutshell- Various deployment tools - generic dependency manifest - Some third-party Windows deployment tools historically used .dep as a dependency declaration file; unrelated to VB6 format.
Programs that open DEP files
Technical details
deep spec| Format type | Plain-text INI-style dependency manifest |
| Text encoding | Windows-1252 / ASCII |
| Typical file size | 1 KB - 20 KB |
| Section naming | Each INI section is named after the component file it describes (e.g., [MyOCX.OCX] or [MSVBVM60.DLL]) |
| Per-section keys | Required file name, minimum version, registration type, destination directory code, optional CAB source path |
| Registration modes | Self-registration flag or explicit regsvr32 path per dependency |
| Master dependency list | VB6DEP.INI (VB6 PDW) / VB5DEP.INI (VB5 Setup Wizard) - system-wide registry of known components |
| Consuming tools | Visual Basic 5.0 Setup Wizard; Visual Basic 6.0 Package and Deployment Wizard (PDW) |
| Companion formats | .vbp (VB project), .cab (distribution archive), .inf (setup script) |
| Target OS era | Windows 95 / 98 / NT 4.0 / 2000 / XP |
| Current status | Obsolete - VB6 IDE unsupported on Windows Vista+; VB6 runtime supported until at least 2031 per Microsoft commitment, but packaging tools are non-functional on modern Windows |
| Released | 1997 (Visual Basic 5.0 / VB Setup Wizard) |
| Latest version | Visual Basic 6.0 Package and Deployment Wizard (1998) - format unchanged |
| Specification | www.infania.net |
Community Q&A
asked by usersNo questions yet - be the first to ask about DEP files.