How Architects Share Blueprints and BIM Models Digitally

Blueprints used to ride to the job site in a cardboard tube. Today the same drawings are 200MB Revit models, 800MB BIM bundles and CAD packages with dozens of external references. The physical handoff is gone but the headaches multiplied. A wrong revision sent to a contractor turns into rework on poured concrete. A missing xref means an entire sheet renders blank when the structural engineer opens it. And every model contains intellectual property that the firm cannot afford to leak to a competitor pitching the same client.

This guide walks through how architects, engineers and contractors share blueprints and BIM models in 2026 without the file size, version control or xref pitfalls that plague CAD file sharing. It covers the major formats, the dependency problems that come with each and how EasySend handles the bundle delivery so nothing breaks when the file lands on the other end.

The Modern Architecture File Stack

Architecture is one of the most file format diverse industries on earth. A single project produces drawings in five or six formats before it reaches the contractor.

DWG (AutoCAD native)

DWG is the binary format AutoCAD writes to disk. It is the lingua franca of 2D construction documents and the reason every CAD viewer on the planet still ships a DWG importer. A modern DWG file is rarely standalone. It pulls in external references (xrefs), image attachments, custom fonts and SHX text styles from disk. If you zip up the .dwg file alone and email it, the recipient opens it and sees missing reference errors. AutoCAD ships a tool called eTransmit that bundles the DWG with every dependency into a single package. Use it.

DXF (Drawing Interchange Format)

DXF is the open ASCII or binary interchange format that lets non Autodesk tools read CAD geometry. Rhino, BricsCAD, FreeCAD and most laser cutters consume DXF natively. It is slightly larger than the equivalent DWG and does not carry the full Autodesk feature set but it is the safest format to send to a contractor whose CAD software you cannot confirm in advance.

RVT (Revit)

RVT is the parametric BIM model format produced by Autodesk Revit. A single RVT file frequently exceeds 500MB because it contains the entire geometric, parametric and metadata model of the building. Revit files also link to other Revit files (architectural model links to structural model links to MEP model) so a coordinated handoff is rarely one file. For external sharing you usually export to NWC (Navisworks) or IFC rather than handing over the raw RVT.

IFC (Industry Foundation Classes)

IFC is the open BIM exchange format defined by buildingSMART. It is the format you send when the recipient uses ArchiCAD, Vectorworks, Tekla, Allplan or any other BIM tool that is not Revit. IFC4 supports geometry, properties, classifications and relationships, which is enough for clash detection and quantity takeoff. File sizes range from 50MB for a small residential project to several gigabytes for a hospital. IFC is also the format most government clients require for deliverables because it is vendor neutral.

DGN (MicroStation)

DGN is the Bentley MicroStation native format used heavily in civil engineering, transportation and infrastructure work. If you are sharing a road alignment with a civil engineer there is a decent chance you are sharing DGN. Like DWG, DGN files can carry references to other DGN files and to raster underlays which need to ship together.

Supporting Formats

Beyond the BIM and CAD natives every project also moves PDF (sealed drawing sets for permitting), STL and OBJ (3D printed massing studies and clash visualization), SKP (SketchUp early design models), RFA (Revit family content) and PLN (ArchiCAD project files). EasySend treats all of these as opaque binaries so format does not matter. What matters is that all of the dependent files travel together.

The xref Problem

External references are the single most common reason an architect emails "I am missing your basement plan" twenty minutes after opening a package. An xref is a CAD entity that points to another CAD file on disk. A site plan xrefs the survey. The architectural plan xrefs the site plan. The structural plan xrefs the architectural. Mechanical xrefs structural. Send the wrong file alone and the recipient sees grey rectangles where geometry should be.

The fix is bundle delivery. Never send a single CAD file. Always send the eTransmit package, the IFC export or a zipped folder that contains every linked file plus the host file. The recipient opens the package and the xrefs resolve to the bundled files instead of asking for paths that exist only on your workstation.

How EasySend Handles Bundle Delivery

EasySend was designed around the bundle problem. When you drop multiple files onto the upload area they are kept together as a single delivery, not flattened into a zip. The recipient lands on a download page that lists every file in the bundle, can preview each one and downloads them as individual files or as a single archive. That preserves the folder structure your CAD tool expects when it goes looking for xrefs.

For the heaviest deliveries, drag the entire eTransmit folder onto easysend.co. The site uploads each file independently with retry on flaky job site connections so a 1.2GB Revit Cloud export does not have to restart from zero if your office WiFi drops. You can also set a custom URL like easysend.co/d/maple-st-rev-7 so the contractor remembers which revision the link points to.

If the project includes confidential design work, enable end to end encryption with a project specific password before uploading. The bundle is encrypted in your browser before any byte leaves your laptop. Even if a sub on the project list forwards the link to a competitor they cannot open the files without the password.

Step by Step: Sharing a Coordination Set

1. Run eTransmit (DWG) or export IFC (Revit). eTransmit lives in the Application menu under Publish. The IFC export options dialog in Revit lets you choose IFC4 Reference View for clash detection or Design Transfer for downstream model editing.
2. Stage every file in one folder. The host file at the top, xrefs in a /Xrefs subfolder, images in /Images and fonts in /Fonts. This is exactly the layout eTransmit produces by default.
3. Drag the folder to easysend.co. The site uploads every file as part of one delivery, not a flattened zip.
4. Add a description with the revision string, the discipline and the issued date. For example "ARCH Rev 7 - issued for construction 2026-06-03".
5. Enable encryption for confidential or unreleased designs and send the password through a different channel than the download link.
6. Set a custom URL like easysend.co/d/maple-st-arch-rev-7 so the link is self documenting in the contractor's inbox.
7. Share the link by email or text and check the download metrics later to confirm every stakeholder pulled the latest revision.

Job Site and Mobile Delivery

Contractors on a job site live on phones. Most office portals fail on mobile because they require a desktop login or a plugin to render drawings. EasySend renders cleanly on any mobile browser so the foreman can pull up the latest sheet next to the saw cut they are about to make. QR codes printed on the corner of physical job site documents give crews a fast path back to the live digital version when revisions change.

Coordinating Revisions

The other half of avoiding rework is making it impossible to send the wrong revision. Three habits help.

• Encode the revision in the filename and in the EasySend custom URL. Both surfaces a recipient sees should agree.
• Track downloads. EasySend records how many times each link was accessed. If your structural engineer never downloaded Rev 7, you know they are still working from Rev 6.
• Set an expiry on superseded revisions. When Rev 8 ships, retire the Rev 7 link with a short expiry so nobody accidentally pulls outdated geometry.

Confidentiality

Architecture firms compete on design language. Competition entries, unreleased renderings and proposal decks for new business cannot leak. Enable EasySend encryption for these shares. The recipient receives the link and a password through separate channels (the link by email, the password by text or phone). Without the password the file is a blob of ciphertext, even to the EasySend infrastructure.

Best Practices Checklist

• Always run eTransmit or its equivalent before sharing CAD files. Never send a bare DWG.
• Bundle DWG and PDF versions side by side so clients without AutoCAD can review.
• Include revision numbers and dates in every filename and in the share URL.
• Use IFC for handoff to consultants who do not run Revit. RVT for handoff to those who do.
• Encrypt confidential deliveries with a password sent on a different channel.
• Track downloads to confirm every stakeholder received the latest revision.
• Print QR codes on job site copies so crews always reach the latest digital version.

See the architect use case and the CAD file sharing guide for deeper coverage of large file workflows.