You are here: NI Home > Support > Product Reference > Manuals > LabVIEW 8.5 Help

The following table includes common file types that LabVIEW creates and uses to save data.

File Extension	Description
.aliases	File that maps targets to URLs. The URL varies by target. Usually, the URL for a target on a network is an IP address. Targets on serial ports display the URL as the serial port. LabVIEW creates the file automatically when you create a LabVIEW project. If you build an application, the .aliases file is copied into the application. LabVIEW creates a new .aliases file each time you open the project. You do not need to check the .aliases file into source control.
.bin3	File to include example VIs in NI Example Finder
.ctl	Control
.ctt	Control template
.llb	VI library. You can group several VIs together and save them in an LLB.
.lvlib	LabVIEW project library. LabVIEW project libraries are collections of VIs, type definitions, shared variables, palette menu files, and other files, including other project libraries.
.lvproj	LabVIEW project
.lvlps	File that stores project settings that are specific to the local machine. You should not check .lvlps files into source control because .lvlps files contain settings specific to the computer you are using; for example, .lvlps files contain the local source code control configuration. LabVIEW saves .lvlps files when you save a project, and correctly renames the file when you rename a project. You can remove or delete .lvlps files without affecting the performance or behavior of a project because .lvlps files only contain project settings specific to the local machine. If you build an application, LabVIEW does not copy the .lvlps file into the built application.
.mnu	Palette
.rc	Configuration file used to store Property Node information for IVI Instrument Drivers and define refnum data types for instrument drivers.
.rtm	Run-time menu
.vi	Virtual instrument
.vit	Virtual instrument template
.xctl	XControl
.xnode	File used internally by LabVIEW. If you create a LabVIEW project that includes VIs that require .xnode files, the .xnode files appear under Dependencies in the Project Explorer window. You cannot modify .xnode files, so .xnode files are locked in the Project Explorer window.