Drop a .vi, .ctl, .llb, or related LabVIEW file here
Everything runs locally in your browser. No file is uploaded. This MVP uses conservative parsing plus heuristic scanning because LabVIEW resource internals are not a normal public web format.
The resource table below is a scanner output. When a valid RSRC header is found, offsets are interpreted cautiously; otherwise, the scanner falls back to searching for known four-character LabVIEW resource codes.
Load a file to inspect metadata.
Dependency detection looks for embedded paths and file names ending in common LabVIEW extensions. It can catch useful hints even when the complete hierarchy is not parseable.
This graph is a best-effort dependency view. For a single VI, it shows likely outgoing references discovered from embedded strings. It does not prove that every listed VI is actually called on the block diagram.
LabVIEW VI icons are often stored in LabVIEW-specific resources, not always as browser-native PNG/JPEG/GIF/BMP. This tab shows any embedded standard images plus hints around icon-like resources.
No file loaded.