Share Custom Linetypes with eTransmit, LIN and SHX

A recipient can open a DWG and still see missing symbols, substituted text, or different complex linetypes. The drawing stores loaded definitions, but custom SHX shapes and font resources can remain external dependencies.

eTransmit is the safest starting point because it gathers recognized drawing dependencies into one package. A controlled review is still required to include source LIN files and internal documentation.

Why Custom Linetypes Can Look Different on Another Computer

The author’s workstation may already contain fonts, SHX files, and support paths that hide missing-package problems. The recipient’s system may also have a different text style with the same name or a different definition with the same linetype name.

Understand What the DWG Stores

Loaded Linetype Definition

The drawing stores the loaded pattern record. A simple dash-gap definition can therefore survive without the original LIN file.

External Shape and Font Dependencies

A complex pattern can reference an SHX shape, an SHX font, or a TrueType font through its text style. Those resources must be available or substituted.

Source LIN File

The source is needed when the recipient must reload, inspect, edit, or deploy the definition in another drawing. Include the approved source even if the current DWG displays correctly.

Identify All Files Required by the Drawing

DWG Files

Include the host and all required drawing references. Confirm that the correct revisions are being transmitted.

LIN Files

Include the custom source libraries used by the project. Do not send modified Autodesk default files when a separate custom file can be provided.

SHX Shape Files

Include compiled shape files referenced by complex linetypes. The shape filename can be found in the LIN descriptor or support warning.

SHX Font Files

Include required custom SHX fonts. Verify that the recipient’s text-style names map to the intended files.

Xrefs and Other References

Review Xrefs, images, data links, plot styles, and other resources that affect the sheet. Linetype success alone does not make the transmittal complete.

Prepare the Drawing Before Transmission

Audit the Drawing

Run AUDIT on a backup and resolve database errors. Open every relevant layout and verify that references are found.

Purge Unused Definitions

Remove abandoned experimental content without purging intentionally preloaded project standards. Use the linetype cleanup guide for dependencies.

Verify Custom Linetypes

Create a small test area or sheet showing each custom pattern, its name, and expected scale. This gives the recipient a visual acceptance reference.

Create an eTransmit Package

Open the eTransmit Dialog

Run ETRANSMIT from the completed host drawing. Save first so the package represents the current file state.

Review the File Tree

Expand the listed dependencies and look for missing paths, duplicate revisions, or files outside the intended project structure.

Select a Transmittal Setup

Use an approved setup that defines package type, path handling, Xref treatment, and included support files. Do not reuse an unknown setup without reviewing its options.

Configure the eTransmit Package

Include Fonts and Support Files

Include required SHX resources. Review licensing before distributing TrueType fonts; when a font cannot be sent, document the approved substitute and test it.

Bind or Retain Xrefs

Retain Xrefs when the recipient must preserve the project structure. Bind only when the delivery specification requires a self-contained drawing and the effects on layers and dependent names have been tested.

Organize Files into One Folder

A flat folder is easy to open but can create duplicate-name collisions. A preserved or organized folder structure can be safer for large projects. Choose one method deliberately.

Create a ZIP Package

A ZIP preserves the package as one delivery item and prevents casual omission during email or upload. Use a clear revision and date in the archive name.

Add Custom LIN and SHX Files Manually

Review whether eTransmit included the source LIN file used to create the definition. If it did not, add the approved LIN, SHX, and a short readme manually. Do not add every file from the author’s support folder.

Test the Package on a Clean Computer

Extract the Package

Extract it to a new temporary folder, not over the original project. This confirms that relative paths and duplicate filenames behave as expected.

Open the Drawing Without Existing Support Paths

Use a clean workstation, virtual machine, or fresh user profile that does not already have the private library installed. Existing support paths can hide a missing dependency.

Check Every Complex Linetype

Inspect straight, reversed, curved, and short examples, then produce the expected PDF. Confirm text font, shape symbol, orientation, scale, and lineweight.

Instructions to Provide to the Recipient

Temporary File Placement

Explain whether the recipient can keep support files beside the DWG for project use. This is often the easiest approach for a one-time review package.

Permanent Support Path Installation

For long-term reuse, specify the folder to add in Options or Application Preferences. Use the Windows and macOS support-path instructions.

Reloading Definitions When Necessary

Explain that an edited source LIN file must be deliberately reloaded into a drawing. Include the exact approved names and avoid duplicate libraries.

Common Sharing Problems

Problem	Cause	Fix
Symbol missing	Required SHX shape not found.	Install or place the correct SHX in a support location.
Wrong font	Font unavailable or style name maps differently.	Install the approved font or documented substitute.
Old pattern	Recipient drawing already stores another definition with the same name.	Use unique names or deliberately reload.
Xref pattern differs	Host layer override or missing dependency.	Review Xref linetype behavior.
PDF differs	Plot setup, lineweight, or font handling.	Use the PDF and print guide.

Final Custom Linetype Transmission Checklist

The host and required Xrefs are current.
The custom LIN source is included.
Required SHX shapes and fonts are included or documented.
The package contains a visual linetype test sheet.
The ZIP was opened on a clean system.
The recipient received installation and reloading instructions.
The final PDF was compared with the author’s approved output.

How to Share Drawings with Custom Linetypes Using eTransmit, LIN, and SHX Files