📑 On This Page
📦 What Is eTransmit?
eTransmit solves the most common problem in sharing AutoCAD drawings: the receiver opens your DWG and immediately sees broken xrefs, missing fonts, wrong lineweights, and blank underlay placeholders — because the supporting files that live on your computer or network were never sent.
The ETRANSMIT command scans your drawing, finds every file it depends on, and bundles everything into a single zip package — your DWG, all xrefs, all nested xrefs, fonts, plot style tables (CTB/STB), PDF underlays, DGN underlays, and raster images. The receiver extracts the zip and every reference resolves correctly from the first open.
Think of it as "Save As + all dependencies." Instead of hunting through network folders trying to remember what your drawing links to, ETRANSMIT does the inventory automatically. It also rewrites the file paths so the recipient's version works, regardless of where they extract the zip.
When you need eTransmit
📤 Sending to a client or authority
Client needs the native DWG for their records, BIM coordination, or further design. They won't have your network drives or font libraries.
🤝 Sending to a subcontractor
Structural engineer, services consultant, or contractor needs your base plan as DWG to overlay their own work.
🗄️ Archiving a project
End of project — archive a self-contained snapshot of the drawing set with all dependencies captured at that point in time.
💻 Moving to a different computer
Shifting work from office PC to laptop, or onboarding a new team member who doesn't have your server mapped.
📋 What Gets Included (and What Doesn't)
✓ Automatically Included
- The current DWG file
- All attached DWG xrefs (and nested xrefs, any depth)
- All attached PDF underlays
- All attached DGN underlays
- All attached raster images (JPG, PNG, TIFF, BMP)
- SHX font files used in the drawing
- Plot style tables (.ctb and .stb)
- Linetype definition files (.lin)
- Hatch pattern files (.pat)
- Data links (Excel spreadsheets linked to tables)
- The transmittal report (.txt or .html)
○ Not Included — Add Manually
- TrueType fonts (.ttf, .otf) — these are Windows system fonts
- Drawing template files (.dwt)
- Tool palette files (.atc)
- Action macro files (.actm)
- Drawing standards files (.dws)
- Sheet Set data files (.dst)
- Any files in the drawing but not referenced (PDFs you've detached)
- Password-protected xrefs (must be supplied separately)
- Files referenced by LISP routines or scripts
TrueType fonts: AutoCAD does not include TTF/OTF fonts in eTransmit packages because they are licensed Windows system fonts. If your drawing uses non-standard TTF fonts (e.g., a firm's branded typeface), you must send those separately and instruct the recipient to install them before opening.
Sheet Set files (.dst): If your drawing set is managed through Sheet Set Manager, the .dst file is not included automatically. You can add it manually using the "Add File" button in the eTransmit dialog, or send it separately.
▶️ Running ETRANSMIT
Command: ETRANSMIT
; The Create Transmittal dialog opens
; Save the drawing first if you have unsaved changes
You can also access it from the Application Menu (the big A) → Publish → eTransmit, or from the Quick Access Toolbar if you've added it there.
Save before transmitting. If your drawing has unsaved changes, AutoCAD will prompt you to save. Always save first — you want the transmittal to reflect the current state of the drawing, not a previous version.
The Create Transmittal dialog — step by step
Create Transmittal
✕
Files Tree
Files Table
Drawing files to transmit:
Site_Plan_Issue_D.dwg
SURVEY_Base.dwg xref
ARCH_Floor_Plan.dwg xref
ARCH_Grid.dwg nested xref
Client_Survey.pdf underlay
NV5_Standard.ctb plot style
Transmittal Setups:
Standard
For Client
Archive
Enter notes to include with this transmittal:
1
Review the Files TreeExpand the tree to confirm all expected xrefs, underlays, and CTB files are listed. Any file shown with a warning icon is missing — resolve it before transmitting.
2
Select a Transmittal SetupA setup stores your preferred packaging options (zip vs folder, path rewriting, etc.). Choose an existing setup or create a new one. See the Transmittal Setups section below.
3
Add any files not auto-detectedClick "Add File" to manually include extras — a sheet set .dst file, a cover sheet PDF, specs document, or DWS standards file.
4
Enter transmittal notesThe notes text box is included in the transmittal report. Use it to describe the issue: "Issue D — For Construction — July 2026". The recipient sees this when they open the report.
5
Click OKAutoCAD prompts you to choose a save location and filename for the zip. Save it to your desktop or a project Issued folder, then email or upload it.
⚙️ Transmittal Setups
A Transmittal Setup is a named collection of packaging options that you save and reuse. Create one for each common scenario — client issue, contractor send, internal archive — and you never have to reconfigure the options each time.
Access via: Create Transmittal dialog → Transmittal Setups panel → New or Modify.
Modify Transmittal Setup — key options
| Option | Recommended Setting | Notes |
|---|---|---|
| Transmittal package type | Zip (*.zip) | Single compressed file — easiest to email and extract. "Self-extracting executable" (.exe) is blocked by most corporate email filters. "Folder" is useful for FTP or shared drive uploads but leaves files unzipped. |
| File format | Keep existing drawing format or AutoCAD 2018 (.dwg) | "Keep existing" sends your current DWG version. If the recipient uses an older AutoCAD, select an older DWG format. AutoCAD 2018 format is widely compatible with 2018–2024. |
| Maintain visual fidelity for non-AutoCAD DWG | Off (leave unchecked) | This embeds extra data for non-AutoCAD viewers. Increases file size without benefit if the recipient uses AutoCAD. |
| Send email with transmittal | Off | Launches your email client to attach the zip. Convenient but bypasses the transmittal filename and forces a smaller email attachment — leave off and attach manually. |
| Transmittal file folder | Prompt for a location | Or set a default Issued\ folder. "Prompt" gives you control each time. |
| Path options | Place all files in one folder or Keep files and folders as is | See the Path & Folder Options section below — this is the most important setting. |
| Include fonts | On | Includes SHX font files. TTF fonts are still excluded (licensing). Turn on to capture custom SHX fonts the recipient may not have. |
| Include plot styles (CTB/STB) | On | Essential — without the CTB file the recipient's lineweights will be wrong. |
| Include linetype definition (.lin) | On | Include if you use custom linetypes. Standard AutoCAD linetypes (acad.lin) are already on the recipient's machine. |
| Include textures | Off (unless 3D) | Only relevant for 3D drawings with material textures. Leave off for 2D production drawings. |
| Report type | HTML (readable in browser) or TXT | The report lists all files included in the transmittal with their original paths. Useful for the recipient to understand the drawing structure. |
Create three setups once and reuse them forever:
• "Client Issue" — Zip, keep folder structure, all files included, HTML report
• "Contractor Send" — Zip, all files in one folder (flat), TXT report
• "Project Archive" — Zip, keep folder structure, include everything, HTML report, save to Archive\ folder
• "Client Issue" — Zip, keep folder structure, all files included, HTML report
• "Contractor Send" — Zip, all files in one folder (flat), TXT report
• "Project Archive" — Zip, keep folder structure, include everything, HTML report, save to Archive\ folder
🗂️ Files & File Tree
The Files Tree tab shows your DWG at the root, with all its dependencies branching below it. The Files Table tab shows the same information in a flat list with file size and path columns — useful for spotting unexpectedly large files or wrong paths.
Icons in the Files Tree
| Icon | Meaning |
|---|---|
| 📁 DWG icon | The main drawing or an xref DWG |
| 🔗 Link icon (blue) | An xref (attached or overlaid) |
| 📎 Paperclip / PDF icon | PDF underlay |
| 🖼 Image icon | Raster image reference (JPG, PNG, etc.) |
| 🖨 Printer icon | Plot style table (.ctb or .stb) |
| 🔡 Font icon | SHX font file |
| ⚠ Warning triangle | File is missing — cannot be included. Resolve before transmitting. |
Example file tree in a typical project
📁 CIVIL-Site-Plan-IssueD.dwg <-- main file you have open
├── 🔗 SURVEY-Base-2026.dwg <-- xref from surveyor
│ └── 🔗 SURVEY-Control-Points.dwg <-- nested xref
├── 🔗 ARCH-Floor-Plan-Level1.dwg <-- architect's base
│ ├── 🔗 ARCH-Grid.dwg
│ └── 🔗 ARCH-Column-Schedule.dwg
├── 📎 Client-Brief-Site-Plan.pdf <-- PDF underlay
├── 🖨 NV5_Standard.ctb <-- your CTB
├── 🔡 simplex.shx
├── 🔡 romans.shx
└── 📄 Transmittal_Report.html
Everything in this tree gets packaged. The recipient unzips and opens CIVIL-Site-Plan-IssueD.dwg — all references resolve to the files that came in the same zip.
📁 Path & Folder Options
The most important eTransmit setting is how file paths are handled inside the zip. This controls whether the recipient's DWG finds its xrefs after extraction.
| Path Option | What It Does | When to Use |
|---|---|---|
| Place all files in one folder | All DWG, xrefs, underlays, fonts land in a single flat folder inside the zip. The DWG's xref paths are rewritten to relative single-folder paths. | Best for simple projects and external sends. Everything in one place — easy to open, no nested folders to navigate. Most contractors prefer this. |
| Keep files and folders as is | Preserves your exact folder structure inside the zip (e.g., DWG\ and XREF\ and SURVEY\ subfolders). Paths in the DWG are not rewritten — they stay as-is. | Best for internal transfers and archives where you want to restore the original structure exactly. Also good when the recipient uses the same folder naming convention. |
| Place all files in one folder and remove paths from xrefs | Flat folder, and xref paths in the DWG are stripped to filename-only (no path). AutoCAD's search path then finds them. | Useful when sending to recipients who will re-link xrefs manually to their own folder structure. Less common. |
| Keep files and folders as is — use organized folder structure | Recreates your folder structure but reorganises it into a clean hierarchy (DWG at root, referenced files in subfolders). | Good for large projects where you want a clean structure in the archive zip. |
For most external sends: use "Place all files in one folder." The recipient extracts the zip, opens the DWG, and everything works. No path confusion, no nested folder navigation. Save the folder-structure option for your own archives.
Avoid "No path" option for cross-firm sends. If paths are stripped to filename-only, the recipient's AutoCAD will only find the xref if it happens to be in the same folder as the DWG, or in a configured search path. This breaks for most recipients.
📄 Transmittal Report
Every eTransmit package includes a transmittal report — an automatically generated document listing every file in the package, its original path, and the notes you entered. It's a record of what was sent and when.
The report includes:
- ▸ Date and time of transmittal creation
- ▸ AutoCAD version used
- ▸ Every file included, with original full path and file size
- ▸ Notes you typed in the transmittal dialog
- ▸ Path remapping information (old path → new path inside zip)
Always include the report. It tells the recipient exactly what's in the package and where everything came from. When something breaks months later, the report is the reference that proves what was sent and when. Keep a copy for your own project records too.
Set report type in the Transmittal Setup: HTML opens in any browser (recommended), TXT is plain text and always readable, None — avoid this option.
📥 Receiving an eTransmit Package
When a colleague or client sends you an eTransmit zip, here's the correct way to open it so all references resolve properly.
1
Extract the zip to a permanent folder — not the desktopExtract to a project folder on your hard drive or server: e.g.,
C:\Projects\Client_ABC\Received_2026-07-31\. Do not open the DWG directly from inside the zip (Windows lets you, but references won't resolve from inside a compressed archive).2
Read the transmittal report firstOpen the HTML or TXT report to understand what's in the package. Check the notes for issue description, DWG version, and any special instructions from the sender.
3
Open the main DWG fileOpen the primary DWG (not the xrefs). AutoCAD will find all references in the same extracted folder (or subfolder structure if the sender chose "Keep folder structure").
4
Check the Xref paletteRun
XREF and verify all xrefs show a green checkmark (loaded). If any show "Not Found", see the troubleshooting section.5
Save a copy before editingNever edit the extracted files directly. Save a copy to your working folder first. Keep the original transmittal zip intact for reference.
If the DWG asks you to install fonts: The sender may use SHX fonts you don't have, or non-standard TTF fonts. SHX fonts should be in the zip — copy them to your AutoCAD font folder (
C:\Program Files\Autodesk\AutoCAD 2024\Fonts\). TTF fonts need to be installed as Windows fonts via right-click → Install.📐 Multi-Sheet Projects
For a drawing set where you have multiple DWG sheet files (e.g., C01.dwg, C02.dwg, C03.dwg all xrefing a common base), you need to include all sheets in the transmittal — not just the one you have open.
Option A: Open each sheet and transmit individually
Run ETRANSMIT from each sheet DWG in turn, saving each transmittal. Then combine the zips manually. Tedious for large sets — only practical for 2–3 sheets.
Option B: Add files manually in the eTransmit dialog
1
Open the main sheet DWG and run ETRANSMIT
2
Click "Add File" in the Files panelBrowse to and select the other sheet DWG files (C02.dwg, C03.dwg, etc.).
3
AutoCAD scans the added DWGs for their dependenciesEach added sheet's xrefs and underlays are automatically discovered and added to the transmittal.
4
Verify the tree and transmitOne zip contains all sheets and all shared/unique references. Shared xrefs (like the common base plan) are included once, not duplicated.
Option C: Use Sheet Set Manager (recommended for large sets)
See the Sheet Set eTransmit section below — Sheet Set Manager has a built-in transmittal workflow that handles multi-sheet sets automatically.
📋 eTransmit with Sheet Sets
If your project uses Sheet Set Manager (.dst file), eTransmit integrates directly with it for a streamlined multi-sheet transmittal workflow.
1
Open Sheet Set ManagerType
SHEETSET or press Ctrl+4.2
Select the sheets to transmitClick a sheet subset or Ctrl+click individual sheets. Or right-click the sheet set name to select all.
3
Right-click → eTransmitThe Create Transmittal dialog opens with all selected sheets already added as root files. Their dependencies are automatically discovered.
4
Optionally add the .dst Sheet Set fileClick "Add File" and include the .dst if the recipient needs to work with the sheet set structure. Otherwise they can just open individual DWGs.
5
Select setup and transmitOne zip contains the entire sheet set — all sheets, all shared and unique xrefs, all underlays, fonts, and CTB files.
Sheet Set eTransmit is the most efficient way to package a large drawing set. 50-sheet civil set, single command, one zip. Compare this to the old workflow of manually copying dozens of DWGs and their dependencies from across a network.
🔧 Troubleshooting
| Problem | Likely Cause | Fix |
|---|---|---|
| Warning triangle on a file in the Files Tree | The file is referenced in the DWG but AutoCAD cannot find it (missing xref, moved PDF, etc.) | Resolve the missing reference before transmitting. Open XREF palette, right-click the missing file → Change Path → browse to it. Then run ETRANSMIT again. |
| CTB file not in the Files Tree | No plot style table is assigned to the layout, or the CTB file is not in AutoCAD's search path | Assign a CTB via Page Setup Manager. Confirm the CTB is in Options → Files → Plot Style Table Search Path. Then re-run ETRANSMIT. |
| Recipient opens DWG and xrefs are "Not Found" | Recipient opened the DWG directly from inside the zip (before extracting), or extracted to a temp folder that doesn't match the expected path | Instruct recipient to: extract the entire zip to a permanent folder first, then open the DWG from that extracted folder. If still broken, use XREF palette → Change Path to re-link. |
| eTransmit zip is unexpectedly huge | Raster images (aerial photos, scanned drawings) or large PDF underlays are included | In the Files Tree, identify large files. Consider whether they are necessary — if the recipient only needs geometry, detach the image underlays before transmitting. Or use "Keep files and folders" and compress separately. |
| Recipient's drawing has wrong lineweights | CTB was not included, or recipient's AutoCAD is not finding it after extraction | Confirm "Include plot styles" is ticked in the Transmittal Setup. Recipient: copy the .ctb file from the zip to their Plot Styles folder: %AppData%\Autodesk\AutoCAD 2024\R24.3\enu\Plotters\Plot Styles\ |
| Fonts show as question marks or wrong characters | SHX fonts were not included, or the recipient doesn't have the TTF fonts installed | SHX: confirm "Include fonts" is ticked. Recipient: copy .shx files to their AutoCAD Fonts folder. TTF: send TTF files separately with installation instructions. |
| ETRANSMIT command not available | Drawing is in a state that prevents transmittal (read-only, or AutoCAD LT) | ETRANSMIT is not available in AutoCAD LT — use manual file copying instead. For read-only files, close and reopen with write access. |
| Nested xrefs not included | Nested xref paths are broken (the xref's host DWG can't find the nested file) | Open the xref DWG separately, fix its broken reference path, save, and close. Then re-run ETRANSMIT from the main drawing — it will now find the nested file. |
✅ Best Practices
1. Always use eTransmit — never manually copy files. Manual copying means you have to know every file the drawing depends on. You will forget something. eTransmit's automated dependency scan catches files you didn't even know were referenced.
2. Resolve all missing references before transmitting. Run XREF and confirm zero "Not Found" entries. A transmittal with missing files is worse than useless — the recipient spends hours trying to fix it and calls you. Fix references first, transmit second.
3. Save the drawing immediately before transmitting. The transmittal captures the saved state. If you have unsaved edits, those won't be in the package. Save → ETRANSMIT, always in that order.
4. Create named Transmittal Setups and reuse them. Set up "Client Issue", "Contractor", and "Archive" setups once. Each subsequent transmittal is: ETRANSMIT → pick setup → add notes → OK. Under 30 seconds.
5. Include meaningful notes in every transmittal. The notes field in the dialog appears in the transmittal report. Write the issue number, date, purpose, and any special instructions: "Issue D — For Construction approval — July 2026. Recipient to use NV5_Standard.ctb included in zip." Months later, this note is the record of what was sent and why.
6. Keep a copy of every transmittal zip. Store zips in a project subfolder:
Issued\2026-07-31_IssueD_ForConstruction.zip. This is your proof of what was sent and when. Invaluable in disputes over drawing versions.7. Use "Place all files in one folder" for external sends. This is the most foolproof option for recipients. One folder, open the DWG, everything works. Reserve "Keep folder structure" for internal transfers where the recipient uses the same conventions.
8. Don't send proprietary information unintentionally. The Files Tree shows you exactly what's going in the zip. Review it before clicking OK. Make sure xrefs from other disciplines (structural, services) that you're not authorised to share are detached before transmitting to external parties.
9. For large sheet sets: use Sheet Set Manager's eTransmit. Right-click the sheet set in SSM → eTransmit. AutoCAD scans all sheets simultaneously and builds one comprehensive transmittal. Far faster than running ETRANSMIT sheet by sheet.
10. Check the transmittal report after creating it. Click "View Report" before clicking OK to confirm the file count, sizes, and paths look right. Spot a 300MB aerial image that shouldn't be there before you zip it, not after.