The following table includes common file types that LabVIEW creates and uses to save data.
File Extension Description
.aliases File that maps computer names to IP addresses. For example, My Computer typically maps to localhost or the actual IP address of the host computer running LabVIEW. LabVIEW creates the .aliases file automatically when you create a LabVIEW project. LabVIEW creates a new .aliases file each time you open the project. If you build an application, the .aliases file is copied into the same directory as the application. You do not need to check the .aliases file into source control unless you extend the mappings in the file. For more information, refer to Using Source Control in LabVIEW.
Note Deleting the .aliases file does not affect the project.
.bin3 File to include example VIs in NI Example Finder

For more information, refer to Preparing Example VIs to Appear in the NI Example Finder.
.ctl Control
.ctt Control template
.llb File that groups multiple VIs, controls, or libraries together in a specialized and compressed format. You can group several VIs together and save them in an LLB. Unlike a packed project library (.lvlibp) in which the files are not editable, the files in an LLB are editable.

For more information, refer to Creating LLBs.
.lvclass LabVIEW Class library. When you create and save a LabVIEW class, LabVIEW creates a class library file that defines a new data type.

For more information, refer to Creating LabVIEW Classes.
.lvlib LabVIEW project library. LabVIEW project libraries are collections of VIs, type definitions, shared variables, palette files, and other files, including other project libraries.

For more information, refer to Using Libraries in LabVIEW Projects and Understanding Shared Variable Technology.
.lvlibp LabVIEW packed project library. LabVIEW packed project libraries are project libraries that package multiple files into a single file. The top-level file of a packed library is a project library.

For more information, refer to Using Packed Project Libraries in LabVIEW Projects.
.lvm The text-based measurement file is a tab-delimited text file you can open with a spreadsheet application or a text-editing application.
.lvproj LabVIEW project

For more information, refer to Managing a Project in LabVIEW.
.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.
Note Deleting the .lvlps file does not affect the project.
.mnu Palette

For more information, refer to Creating Subpalettes in a Palette Set.
.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

For more information, refer to Customizing Menus.
.tdm/.tdms TDM/TDMS file

For more information, refer to TDM/TDMS Files.
.vi Virtual instrument

For more information, refer to Anatomy of a VI and Common VI Objects.
.vim Malleable VI

For more information, refer to Malleable VIs.
.vit Virtual instrument template

For more information, refer to Creating Template VIs.
.xctl XControl

For more information, refer to Using XControls.
.xnode File used internally by LabVIEW. You cannot modify .xnode files, so .xnode files are locked in the Project Explorer window.