Your Revit files are too big for email. Now what?

Why architecture firms keep hitting the 25 MB wall, and how to move project files without the usual workarounds

The size problem is built into Revit

A Revit central model for a mid-size commercial project will sit somewhere between 150 MB and 500 MB. Add linked models for structural, MEP, and site, and the combined package can reach several gigabytes. This is normal. Revit files are large because they contain three-dimensional geometry, family definitions, material data, view configurations, and project metadata all in a single compound file. The more detailed the model, the bigger the file. A hospital or university campus model with fully coordinated MEP can push well past a gigabyte before anyone has done anything unusual.

Email services, meanwhile, impose a hard ceiling. Gmail and Outlook both cap attachments at 25 MB. Some enterprise mail servers set the limit even lower, at 10 MB or 15 MB. A single Revit file exceeds that limit by a factor of ten or more. This gap between what the tool produces and what the communication channel accepts is a daily friction point for architects, BIM managers, and project leads.

The usual workarounds and their limits

Most firms default to one of a handful of methods when email fails. Each solves the immediate problem of getting a file from point A to point B, but each introduces its own friction.

WeTransfer and similar transfer services let you upload a file and send a download link. The free tier caps file size at 2 GB and expires links after seven days. The paid tier raises both limits, but the recipient still has to download the entire file before they can do anything with it. For a 400 MB Revit file on a mediocre internet connection, that download takes time. If the recipient needs to pass the file along to a subconsultant, the process starts again. There is no persistent link, no version tracking, and no way to know whether the recipient opened the file or ignored it.

Dropbox and Google Drive links are more durable. You upload the file, generate a sharing link, and send that link by email. The file persists until you delete it. But Dropbox and Google Drive were designed for general-purpose file storage, and they handle large binary files awkwardly. Revit files cannot be previewed in a browser. The recipient clicks the link, waits for a download, and opens the file locally. If you update the file and re-upload, the link may or may not point to the new version, depending on how you managed the upload. Folder structures grow tangled over the course of a project, and finding the correct version of a model three months later becomes an exercise in scrolling through timestamps.

FTP servers still exist in some firms, particularly larger practices with dedicated IT staff. FTP is reliable for large files, but it requires the recipient to have FTP client software, login credentials, and some comfort with a file transfer interface that looks like it was designed in 1995. Sending FTP credentials to a client who expects a simple link is a conversation most project managers would rather avoid.

BIM 360 and Autodesk Construction Cloud offer a purpose-built solution within the Autodesk ecosystem. For firms fully committed to Autodesk's platform, these tools handle model hosting, version control, and access permissions. The trade-off is cost, complexity, and ecosystem lock-in. Licensing fees scale with the number of users, and bringing an external consultant into your BIM 360 project means adding them as a user, managing their permissions, and hoping they already know the interface. For a one-off file share with a client who just wants to review a model, this is heavy machinery for a simple task.

What the workarounds miss

All of these methods treat the symptom. The file is too big for email, so you find another pipe to push it through. But the underlying problem is broader than transmission. The real difficulty is that project files in AEC practices tend to be scattered across local machines, cloud storage accounts, email threads, and transfer service links. The file you sent to the structural engineer last Tuesday might be a different version from the one you uploaded to Dropbox on Wednesday, and neither matches the one sitting on the BIM manager's workstation right now.

Sharing a large file is one step in a longer workflow. Before you share it, you need to know where the current version is. After you share it, you need to know whether the recipient received it and opened it. If they send back comments, you need to connect those comments to the correct version of the file. None of the standard workarounds address this. They move bytes from one location to another, and everything else remains manual.

A different approach to large file management

Fabric's cloud drive takes a different approach to the storage and sharing problem. Files uploaded to Fabric live in the cloud and stream on demand. They appear in your file browser as though they were stored locally, but they occupy zero space on your hard drive. When you open a file, Fabric streams the data you need. When you close it, the local footprint disappears. This matters for Revit files because it removes the tension between keeping files accessible and keeping your local storage under control.

For a BIM manager maintaining a library of project models, this means every file is available from any device without manually syncing folders or wondering which laptop has the latest version. The canonical copy lives in Fabric's cloud, and everyone on the team accesses that same copy. There is no "I have it on my machine, let me upload it" delay. The file is already there.

You can read more about how the cloud drive works.

Sharing with clients and consultants

When you need to send a Revit file to a client or consultant, Fabric's publish feature lets you create a polished page with a direct link to the file. The recipient clicks the link and gets access. No accounts to create, no software to install, no seven-day expiry window. The link persists for as long as you want it to.

Fabric's publish pages also include link analytics, so you can see whether the recipient opened the link and when. For a project lead who sent a model to a client for review and needs to know whether they have looked at it before the next coordination meeting, this is a small but meaningful piece of information. It replaces the awkward "just checking you received the file" follow-up email.

Keeping linked models together

Revit projects rarely consist of a single file. A coordinated BIM project might include an architectural model, a structural model, one or more MEP models, a site model, and various family libraries. These files reference each other through linked models, and sharing one without the others can cause broken references and missing geometry on the recipient's end.

Fabric's folder structure lets you organise linked models in a logical hierarchy and share the entire folder, preserving the relationships between files. When a consultant downloads or accesses the folder, the linked models remain intact relative to each other. This is a practical consideration that transfer services and email attachments handle poorly; sending five separate WeTransfer links for five linked models and hoping the recipient reassembles them correctly is a recipe for missing references.

Fabric also supports smart organisation features that help keep project files sorted and findable. Over the life of a project, the number of files grows substantially, and maintaining a coherent folder structure becomes a task in itself.

Search across file types

AEC projects generate files in dozens of formats: RVT, DWG, DXF, PDF, IFC, NWD, DOCX, XLSX, and more. Finding a specific file, or finding information within a file, often means opening files one by one and scanning their contents. Fabric's semantic search indexes files by meaning rather than just filename, so a search for "second floor reflected ceiling plan" can surface the relevant file even if it is named something unhelpful like "A201_RCP_v3_final_FINAL.rvt".

This is particularly useful when project archives grow large and naming conventions drift over time, as they do in every firm.

Backup and sync across devices

For architects who work from a studio desktop, a laptop at home, and occasionally a tablet on site, keeping Revit files synchronised across devices is a persistent annoyance. Fabric's cloud drive handles this by keeping the canonical file in the cloud and streaming it to whichever device requests it. There is no manual sync step, no USB drive to carry between machines, and no risk of editing an outdated local copy.

The backup aspect is equally important. Local hard drives fail. Laptops get stolen. A single-point-of-failure storage setup, where the only copy of a project model lives on one machine, is a risk that most firms acknowledge but few address systematically. Fabric's secure cloud storage provides automatic backup without requiring the user to remember to run a backup routine.

Practical considerations for BIM managers

BIM managers spend a disproportionate amount of their time on file logistics: uploading, downloading, renaming, organising, and chasing people who forgot to save to the right folder. Any tool that reduces this overhead frees up time for the coordination and quality-control work that BIM managers are meant to be doing.

Fabric connects to dozens of existing tools, including Google Drive and Dropbox, so migrating does not require abandoning your current storage setup overnight. You can connect existing cloud storage accounts and bring those files into Fabric's unified interface.

It is worth noting that Fabric is a cloud workspace and file management platform. It does not replace Revit, and it is not a BIM authoring or model-checking tool. It handles the storage, organisation, sharing, and retrieval layer that sits around your authoring tools. Think of it as the infrastructure that keeps your files findable and shareable, while Revit, AutoCAD, and Navisworks remain where you do the design and coordination work.

Frequently asked questions

What is the maximum file size Fabric supports?

Fabric's cloud drive is designed for large files and does not impose the restrictive limits you encounter with email or free-tier transfer services. Revit models of several gigabytes can be stored and streamed without issue.

Can my client access the Revit file without a Fabric account?

Yes. When you publish a file through Fabric's publish feature, the recipient receives a link they can open in their browser. They do not need to create a Fabric account or install any software to access the shared content.

Does Fabric replace BIM 360 or Autodesk Construction Cloud?

Fabric is a file management and cloud storage platform, not a BIM coordination tool. It handles storage, sharing, and organisation of project files. If your firm relies on BIM 360 for model coordination, clash detection, and issue tracking, Fabric sits alongside it as a complementary layer for broader file management.

Can I share an entire folder of linked Revit models?

Yes. Fabric supports folder-level sharing, which preserves the relative structure of linked models. This is important for Revit projects where architectural, structural, and MEP models reference each other.

How does Fabric's cloud streaming work with large Revit files?

Files stored in Fabric appear in your file system as local files but occupy zero local storage. When you open a file, Fabric streams the necessary data on demand. This means you can browse and access large Revit files without waiting for a full download or consuming hard drive space.

Can I see whether my client opened the file I shared?

Yes. Fabric's publish feature includes link analytics that show when a recipient accessed your shared link. This replaces the need for follow-up emails asking whether they received the file.

Does Fabric work with other AEC file types like DWG, IFC, and PDF?

Fabric is file-type agnostic. It stores, organises, and shares any file format, including DWG, DXF, IFC, NWD, PDF, and all common document and spreadsheet formats.

Can I connect Fabric to Google Drive or Dropbox where I already store files?

Yes. Fabric connects to dozens of cloud storage services, including Google Drive and Dropbox. You can bring existing files into Fabric's unified workspace without migrating everything at once. See the full list of connections.

Does Fabric provide version control for Revit files?

Fabric keeps files backed up and synchronised across devices. For Revit-specific version control with worksharing and central model management, you would continue using Revit's built-in tools or Autodesk's cloud services. Fabric complements these by providing reliable cloud storage and easy sharing.

Is Fabric suitable for firms without dedicated IT staff?

Yes. Fabric requires no server setup, no FTP configuration, and no IT infrastructure. It works as a cloud service accessible through a desktop app, mobile app, or web browser, making it suitable for small and mid-size firms that lack dedicated IT support.

Related pages

• Cloud drive

• Semantic search

• AI assistant

• Connections

• Publish and share

• Smart organisation

• Annotations

• Architecture studios

• Security and privacy

• Desktop app