12 min read Updated Jun 2026

Transmit Documentation

Complete guide to installing, configuring, and using Transmit to produce clean, issue-ready RVT files alongside IFC / NWC / DWG exports — all without ever touching your source model.

Transmit is a Revit add-in that turns the model-handover process into a single repeatable operation. It opens your model detached, cleans it via a reusable profile of 40+ discrete cleanup steps run in dependency order, and exports any combination of RVT / IFC / NWC / DWG in one run — then closes the detached copy without ever touching the original.

The headline output is a clean, issue-ready RVT. Where most handover tools only emit a secondary export, Transmit always produces a properly stripped RVT alongside whatever else you need.

Supported Revit Versions

• Revit 2022
• Revit 2023
• Revit 2024
• Revit 2025
• Revit 2026
• Revit 2027

Installation

Transmit ships as an Autodesk ApplicationPlugins bundle. The installer deploys a version-specific copy of the add-in for each Revit release you select.

Install Locations

For Revit 2022–2026, Transmit deploys to the shared ProgramData plugins location, with a per-version subfolder:

For Revit 2027, Transmit deploys to the Program Files plugins location instead — administrator rights are required, because Revit 2027 no longer scans ProgramData:

After installation, find Transmit on the Add-Ins ribbon tab, in the AUTOM8LABS panel.

Quick Start Guide

Follow these steps to run your first transmittal with Transmit:

Model Sources

Transmit can process models from three sources. The currently-open document is detected and seeded into the matching tab automatically.

Local Files

Add local .rvt files by dragging them in or browsing to them. Each file becomes a queued row that you can process individually or together.

Revit Server

Point Transmit at models hosted on Revit Server using RSN:// paths. The model opens detached straight from the server.

ACC / Forma Cloud

Transmit can process cloud-workshared models from ACC / Forma. Two conditions must be met:

• The model must have been opened from the cloud at least once so it is cached locally.
• You must be signed into ACC inside Revit for the current session.

Only genuine cloud-workshared models are listed.

Open & Close Behaviour

Transmit always opens detached and always closes without saving. The original is never modified, checked out, or synced. Within that guarantee, a handful of options tune how each model is opened for processing.

Model Cleanup

Cleanup is the heart of Transmit. A profile enables any subset of 40+ discrete strip steps, grouped below into six categories. Two principles govern how they run:

• Transactional isolation — each step runs in its own transaction, so a failure in one step doesn't stop the rest.
• Fixed dependency order — steps run in a deterministic order. Sheets are stripped before views (views placed on sheets can't otherwise be deleted), the family purge runs last, and purge is multi-pass so nested unused families are caught across successive passes.

Views & Sheets

• Keep only sheeted views — remove every view that isn't placed on a sheet
• Remove all views/sheets with keep-lists — strip views and sheets, protecting named exceptions
• Remove schedules
• Name-pattern view removal — defaults target drafting/section/3D views, "Copy" views, "WIP" views, and empty drafting views
• Remove unused view templates & filters
• Clear empty elevation markers
• Set a starting view
• Create a coordination 3D view

Rooms, Areas & Spatial

• Remove unplaced rooms/areas
• Remove all rooms / all areas
• Remove room & area separation lines
• Remove areas + boundaries when no area plans exist
• Remove unused scope boxes

Links & CAD

• Remove Revit links and place types on their instance workset
• Workset placement for RVT links — common / separate / no change
• RVT link path type — relative / absolute / no change
• Remove 2D-only / hidden / all CAD imports
• Move CAD to a common workset
• Purge imported CAD categories
• Remove point clouds
• Remove images — all / linked / imported

Constraints, Datums & Materials

• Remove all constraints (or view-specific only)
• Remove unnamed reference planes — keeping planes-of-record
• Remove leftover render materials and unused materials & fill patterns
• Pin Revit links, CAD, grids and levels
• Move levels & grids to a shared workset

Bulk Hygiene

• Purge unused (multi-pass)
• Explode array groups
• Clean revision clouds
• Remove imported IMPORT- line patterns
• Remove non-primary design options
• Remove 2D elements hidden in their views
• Remove elements on worksets not visible in all views
• Flatten worksets

Output Validation

• File size alert — warn if the output exceeds a configurable MB threshold (warning only; never blocks the run)
• Site coordinates check — compare each model's shared site coordinates against a reference file and flag drift

Export Formats

Transmit can emit any combination of four formats in a single run. Each has its own settings panel.

RVT

The cleaned RVT is written via a detached SaveAs. Optionally enable Compact to shrink the file and Audit to verify and repair model integrity as part of the save.

IFC

Configure the IFC export inline: IFC version, setup, property sets, level of detail, and the full set of advanced toggles. The configuration round-trips as XML that is compatible with Revit's native IFC export dialog, so settings carry across cleanly.

NWC

Emit Navisworks cache files using the standard NWC export options for downstream coordination.

DWG

Export a single 3D view to DWG with control over layer mapping, colour mode, units & coordinates, and the target CAD version.

Profiles

A profile is a reusable JSON preset covering every cleanup and export setting. Profiles let you define a handover recipe once — per recipient or per discipline — and reapply it consistently across models and over time.

Profile Operations

• New — start a fresh profile
• Save — update the current profile
• Save As — copy the current settings to a new profile
• Rename
• Delete
• Import — bring in a profile JSON from elsewhere
• Export — share a profile JSON with colleagues

Built-in Templates

Transmit ships with a set of built-in starter templates so you can get going immediately. Built-in templates cannot be overwritten — use Save As to make your own editable copy.

Settings

The Settings area controls defaults and how Transmit handles Revit's own warnings and errors during a run.

Queue Defaults

• Default output folder — where new queue rows write their output
• Default profile — the profile pre-selected for new queue rows

Revit Failure Handling

• Log + dismiss all warnings
• Log + dismiss all errors
• Allow deleting elements to dismiss some errors — lets Transmit clear errors that can only be resolved by removing the offending element
• Max errors per file — the threshold above which a file is skipped

Logging

Set the logging verbosity to control how much detail Transmit records. Logs are written to:

Troubleshooting & Support

Cloud models won't process

The most common issue with cloud models is the two prerequisites for ACC / Forma access:

• Sign into ACC inside your Revit session.
• Open the cloud model once from the cloud so it is cached locally.

If a cloud build fails, it almost always traces back to one of these two. Confirm both, then try again.

Log Files

Transmit writes detailed logs for every run — each strip step, each export, and any warnings or errors it dismissed. Find them at: