An architect’s guide to sharing CAD drawings and renders (without broken links or missing Xrefs)

You are trying to get a CAD set and a few renders to a client or consultant, and email is either bouncing or stripping attachments. The real risk is not “file too big”, it is “file delivered but unusable”: missing Xrefs, broken texture paths, wrong plot style tables, or a consultant opening the wrong revision.

This step-by-step workflow helps you package CAD drawings and renders so they open correctly, stay organised, and download reliably. It is written for architects who need to finish the job tonight, not for IT people.

Step 1: Decide what you are actually delivering (so you do not overshare)

Before you export anything, answer one question: what does the recipient need to do with the files?

• Client review: usually PDF sheets + a few JPG/PNG renders. They do not need DWGs.
• Consultant coordination (MEP, structural): DWG/RVT/IFC plus Xrefs, plus a clear “read me”.
• Planning submission: a locked PDF set, sometimes specific naming rules, and often no editable CAD.
• Visualisation handoff: model + textures + proxies + HDRIs, or an “assets” package with paths preserved.

Sending the smallest viable deliverable reduces upload time, client confusion, and accidental disclosure (like your internal titleblock notes or proprietary families).

Step 2: Create a clean delivery folder with a revision you can defend

Make one parent folder that will become the transfer payload. Use a naming pattern that sorts cleanly in email threads and download folders.

• Recommended pattern: ProjectName_Issue_YYYY-MM-DD_Rev
• Example: OakMews_DD-Coord_2026-08-28_RevC

Inside it, keep a simple structure:

• 01_PDF (client-friendly sheets)
• 02_CAD (DWG/IFC/RVT package)
• 03_Renders (JPG/PNG/TIFF)
• 04_ReadMe (one text or PDF note with what changed)

This is boring on purpose. Boring is what opens correctly at 10pm on someone else’s laptop.

Step 3: Package your CAD so Xrefs and assets do not break

The most common failure mode we see is a recipient opening a DWG and getting a sea of missing references. Your goal is “self-contained”. How you do that depends on your tool.

If you are sending AutoCAD DWG files

1. Bind or eTransmit: Use eTransmit (or your firm’s equivalent) to collect the DWG and all Xrefs into one package. Set it to place files in a single folder (or a controlled folder structure) so relative paths work.
2. Use relative paths: If you keep Xrefs external, convert paths to relative, then keep the folder structure intact in the delivery folder.
3. Include plot styles: Add .CTB/.STB files if the recipient needs to plot. Missing plot styles is a classic “looks fine here” problem.
4. Fonts and SHX: If your drawings rely on non-standard fonts, include them or convert critical text to geometry for the deliverable (only if appropriate for the recipient’s workflow).
5. Run an audit: A quick AUDIT and purge can prevent opening errors on other machines.

If you are sending Revit models

1. Decide “editable” vs “for reference”: If the recipient only needs reference, consider IFC or DWG exports plus PDFs.
2. Package links: If sharing an editable model, include linked models and any shared coordinates notes in the ReadMe. A model that opens but is misaligned still wastes half a day.
3. Detach (when appropriate): If you are issuing a copy outside your team, you may need to detach from central. Follow your office BIM policy.

If you are sending IFC, DGN, or other coordination formats

1. Export a coordination view: Use a view/template intended for coordination, not your full internal model with every workset and annotation.
2. Spot-check in a viewer: Open the exported file in a neutral viewer before you send it. Catch missing elements now, not after the consultant replies “half the facade is gone”.

Step 4: Export PDFs and renders in client-proof formats

Clients rarely want the same thing your consultant wants. Keep it simple and predictable.

PDF sheet sets

1. Export as a single PDF set when possible. One file is harder to misplace and easier to reference in a meeting.
2. Use a clear sheet index on the first page.
3. Keep a reasonable resolution: For most review, clarity beats massive file size. If you are tempted to crank settings to the max, do a test export and check the file size first.

Renders

1. Send JPG/PNG for review, and reserve TIFF/EXR only for people who asked for them.
2. Name images like sheets: 001_LivingRoom_ViewA.jpg is easier than final_final3_reallyfinal.jpg.
3. Include a “selected” subfolder if you are sending lots of options, so they know which ones matter.

Step 5: Add a one-page ReadMe that prevents the back-and-forth

Most “can you resend?” messages happen because the recipient is unsure what they got. A tiny ReadMe saves you time and looks professional.

• What’s included: “PDF set + DWG background + bound Xrefs + 6 renders”.
• Issue purpose: “Coordination issue for MEP ceiling zones”.
• Revision note: 3 to 6 bullet points of what changed.
• How to open: “Open 02_CAD\SitePlan.dwg” (spell it out).
• Contact: one person, one email, one phone.

Dry humour allowed: “If anything is missing, it is almost certainly my fault, please tell me before you rebuild the facade.”

Step 6: Compress only when it helps (and do not re-compress already-compressed files)

Zipping a delivery folder is useful because it preserves your structure and relative paths. It is not magic for file size.

• ZIP helps: DWGs, RVTs (sometimes), lots of small PDFs, text files.
• ZIP barely helps: MP4 video, JPG renders, already-compressed archives.

One practical detail from experience: if you are uploading from a hotel or site office connection, a single ZIP is often more reliable than hundreds of tiny files that fail halfway through.

Step 7: Choose a sending method that matches your deadline and control needs

For architect-to-client delivery, you usually want three things: a single link, predictable expiry, and access control (password or download limits) when the content is sensitive.

If you need a quick, professional handoff with expiry, a transfer link is usually the fastest path.

Step 8: Send the package with an expiring link and a password (when it matters)

We build LetsSend, so we will be transparent: this is our own product. If you want a simple WeTransfer-style transfer link that is private by default, it fits this specific workflow well.

As of August 2026, LetsSend Free allows up to 5GB per transfer (and 5GB daily, up to 10 files per day) with links that expire after 7 days. LetsSend Pro allows up to 200GB per transfer with expiry up to 30 days, and costs $12/month. You can verify the current limits on the Free vs Pro pricing page.

1. Upload your delivery folder (or the ZIP) and wait for the upload to complete.
2. Set an expiry that matches the project tempo: short for client reviews, longer for consultant coordination. Expiry is your safety net when a link gets forwarded six months later.
3. Add a password for sensitive work: planning drawings, residential floor plans, or anything under NDA. (Send the password in a separate channel.) You can see the available link controls on the features page.
4. For Pro, consider a download limit when you want a link to behave more like a controlled handoff than an open invitation.
5. Send the link with a short message that mirrors your ReadMe: what it is, what changed, when it expires.

One detail we care about as a file transfer service: files upload straight from your browser to encrypted object storage (not via a middle server), which reduces moving parts and keeps the flow simple. Links expire automatically, and expired transfers are deleted rather than quietly archived. If you want to read the plain-English version of how we handle privacy and retention, see how we handle your data.

Step 9: Write the message that stops “can’t open” replies

Copy-paste this, then tweak:

• Subject: Oak Mews DD Coordination Issue, Rev C (expires 7 days)
• Body: “Here is Rev C for ceiling coordination. Open ReadMe first, then 02_CAD\CeilingZones.dwg. PDF set is in 01_PDF. Link expires on 2026-09-04. Password sent via SMS.”

Notice what is missing: apologies, long explanations, and twenty attachments.

Step 10: Verify like the recipient (the fastest quality check you can do)

Do this before you hit send, or immediately after you generate the link:

1. Download your own package to a different folder than your working files.
2. Open the DWG/RVT/IFC from the delivered folder, not from your project directory.
3. Check Xrefs, plot styles, and key views.
4. Open one PDF and one render on your phone. Clients do this all the time, even if you wish they did not.

This catches 90% of issues. The other 10% are usually “they used a different software version” or “their IT blocks downloads”, and no amount of optimism fixes those.

Step 11: If an upload fails, fix the cause (not just the symptom)

Large uploads fail for boring reasons: unstable Wi‑Fi, sleeping laptops, flaky VPNs, and giant folders with thousands of tiny files.

• Switch networks: if you are on site Wi‑Fi, try a wired connection or a more stable network.
• Keep the laptop awake: prevent sleep until the upload completes.
• Pause the VPN if your office policy allows it, VPNs can add dropouts.
• ZIP the folder to reduce “many small files” overhead.
• Try a smaller test transfer first if you suspect the recipient’s network policies are strict.

If you need troubleshooting steps specific to our service, the Help Center covers common upload and download problems.

Step 12: When a transfer link is not the right tool

Honest trade-offs:

• Long-running projects with constant updates: a shared Drive/Dropbox/OneDrive folder or a proper CDE can be better, because it is designed for versioned collaboration.
• Huge deliveries with strict chain-of-custody: consider a dedicated media delivery platform or your client’s portal requirements.
• Highly sensitive documents: you might need contractual controls, not just technical ones.

The goal is not “use a link for everything”. The goal is “get the right files to the right people, reliably, with minimal admin”.

A simple, repeatable architect checklist (save this)

1. Define deliverable (client review vs consultant coordination).
2. Create a dated, revisioned delivery folder.
3. Package CAD (Xrefs, plot styles, fonts).
4. Export client PDFs and named renders.
5. Add a one-page ReadMe.
6. ZIP if it preserves structure or reduces file chaos.
7. Send with an expiring link, add a password when needed.
8. Verify by downloading and opening from the delivered folder.

If you want the quickest path to sending a clean package today, you can send a file free. If you are curious who is behind this advice, see the team behind LetsSend. For anything unclear, you can contact us and a real person will respond.

Related reading (if you are comparing tools for other creative workflows): WeTransfer vs Dropbox for large files: sharing music stems and masters without the chaos.