Where AutoCAD Stores LIN Files and Support Paths

AutoCAD can load a LIN file from any location you browse to, but a permanent library needs a predictable Support File Search Path. The same path system also helps AutoCAD locate SHX shapes, SHX fonts, and other support resources.

Folder names vary by product, release, operating system, and user profile. The reliable method is to inspect the active application settings rather than copying one fixed path from another computer.

Standard AutoCAD Linetype Files

The Imperial LIN Library

acad.lin is the conventional standard library associated with imperial-oriented definitions. It belongs to the installed product support files and should not be treated as the company customization file.

The Metric LIN Library

acadiso.lin contains ISO or metric-oriented definitions. The difference is not merely the filename: pattern values are designed for another unit convention, as explained in Metric vs. Imperial Linetype Scaling.

Product-Specific LIN Files

Vertical products and DWG alternatives may include additional libraries or use different default names. Always identify the file selected by the active product before editing or migrating anything.

How AutoCAD Finds LIN and SHX Files

Current Drawing Folder

Keeping a dependency beside the DWG can be useful for a portable project package, but it is not a complete company deployment strategy. Users can open the same drawing from different extracted folder structures.

Support File Search Paths

AutoCAD searches the ordered folders configured in the application. Put the approved custom library in a dedicated folder and avoid creating two searchable copies with the same filenames.

Default AutoCAD Support Folders

The installation and user profile contain default support locations. These folders may be replaced or migrated during upgrades. Use them to understand the product, not as the only repository for company-controlled source files.

Find the LIN Files Used by Your AutoCAD Installation

Search Through AutoCAD Options

On Windows, open Options > Files and expand Support File Search Path. Inspect the listed folders, then search those folders for *.lin and the required SHX resources.

Search Through the Operating System

Use File Explorer or Finder only after confirming which product and release is active. Search results often include archived, downloaded, and older-version copies that should not be edited.

Windows vs. macOS File Path Differences

Windows Support Folder Conventions

Windows commonly uses drive letters, backslashes, per-user AppData folders, and installation folders under Program Files. Scripts should not assume that every organization installs or redirects them identically.

AutoCAD for Mac Support Folder Conventions

On macOS, open Application Preferences and inspect the Application tab’s support paths. User Library folders and application package locations differ from Windows conventions.

Path Separators and User Library Locations

Cross-platform scripts must normalize separators and avoid copying a literal Windows path into a Mac routine. Use configurable roots, findfile, or deployed relative structures where appropriate.

Mixed Windows and Mac Deployment Considerations

Use the same logical library contents on both platforms while allowing a different local root. Keep filenames portable, avoid case-only differences, and test fonts and SHX files on both systems.

Add a Custom Folder to the Support Search Path

Create the Library Folder

Create a clear structure such as CAD/Support/Linetypes with subfolders only when the application and deployment method can resolve them consistently.

Add the Folder in AutoCAD Options

Add or browse to the folder in Support File Search Path. Place it in a deliberate search order so an outdated duplicate is not found before the approved copy.

Test the New Path

Restart or refresh the application as required, open a blank drawing, load a definition without browsing manually, and verify a shape-based pattern whose SHX lives in the same managed location.

Why You Should Not Edit the Default LIN Files

Software Updates and Reinstalls

Default files can be replaced during maintenance. A custom definition added directly to them may disappear without appearing in the drawing history.

Version Conflicts

Different AutoCAD releases can maintain separate support folders. Editing one release does not automatically update another and can leave users with several conflicting definitions.

Company Standardization

A company library needs ownership, review, version history, and a deployment method. Those controls are easier with a separate source file than with local edits to a vendor file.

Create a Central Company Linetype Library

Organize Files by Discipline

Use a core file for common patterns and separate files for architecture, MEP, civil, survey, or specific clients when the library becomes too large for one owner and review cycle.

Separate LIN, SHP, SHX, and Documentation Files

Keep editable sources and compiled outputs together in a documented structure. Users may need only LIN and SHX files, while maintainers also need SHP source, test DWGs, and release notes.

Control File Names and Versions

Avoid putting changing version numbers inside every dependency name unless the deployment process updates all references. Use release folders or a controlled manifest while keeping production filenames stable.

Store Linetypes in a DWT Template

Preload Approved Linetypes

Load only the definitions required by the template’s disciplines. A template is a drawing database, so it stores the loaded records even when the source file is elsewhere.

Assign Linetypes to Standard Layers

Create the approved layers and assign their patterns, colors, and lineweights. Users should normally draw ByLayer.

Keep the Template Clean

Purge unused experimental definitions before release. Maintain a separate laboratory drawing for pattern development and plotting tests.

Local, Network, and Cloud-Based Libraries

Advantages and Risks of Local Storage

Local files load quickly and work offline, but they can become outdated. Use a managed installer, synchronization process, or startup check to keep them aligned with the approved release.

Managing Network Paths

A network folder provides one source but depends on connectivity and permissions. Use a stable UNC or mounted location and define how users work when the network is unavailable.

Avoiding Broken Cloud-Synchronized Paths

OneDrive, Dropbox, and similar services may assign different local roots or leave files online-only. Confirm that the support file exists locally and that the path remains stable across user profiles.

Sharing Libraries Between Windows and macOS

Deploy identical contents to platform-specific local roots or mount a tested shared location. Keep names, case, and dependencies portable and avoid Windows-only font or ActiveX assumptions.

Move the Library to a New AutoCAD Version

Copy the controlled custom library, not the entire old support folder. Add the new path, load a test drawing, compare screen and plot output, and confirm startup routines and trusted paths. Do not overwrite newer Autodesk default files with older versions.

Troubleshoot LIN and SHX Files Not Found

Confirm the exact filename, including extension and case.
Use findfile or the application settings to verify the resolved location.
Remove or rename duplicate outdated copies.
Check whether the LIN references another SHX filename.
Test from a blank user profile or clean workstation.
Use the missing-SHX and LIN error guide when the file is found but the definition still fails.