How to Share Large 3D Files Without Email Limits

The File Size Problem

3D files are big, and they're getting bigger. A detailed STL exported at high resolution can easily be 50-200 MB. Photogrammetry scans routinely produce files in the hundreds of megabytes. Textured GLB files with 4K maps can exceed a gigabyte. Meanwhile, the tools we use to send files to other people have strict limits that haven't kept pace.

Email is the most common way professionals send files, and it has the most restrictive limits. Gmail caps attachments at 25 MB. Outlook allows 20 MB. Corporate email systems often set even lower limits. A single STL file from a moderately detailed CAD model will exceed these limits, making direct email attachment impossible.

This creates a cascade of workaround behaviors that waste time for everyone involved. You can't just send the file, so you have to think about how to get it to the other person. That thought process, and the steps that follow, consume minutes or hours that could be spent on actual work.

The Common Workarounds (And Their Problems)

Cloud Storage Links (Google Drive, Dropbox, OneDrive)

The most common workaround is uploading the file to cloud storage and sending a download link. This technically solves the file size problem — Google Drive allows files up to 5 TB — but introduces new friction.

First, the recipient has to download the file. For a 100 MB STL, that means waiting for the download and then finding the file in their Downloads folder. On a phone, this is particularly painful — mobile browsers download the file but provide no useful way to open it.

Second, the recipient needs software to open the downloaded file. If they received an STL, they need a 3D viewer, slicer, or CAD tool. If they received an OBJ with textures, they need a tool that handles OBJ and knows how to find the associated MTL and texture files. For non-technical recipients — clients, managers, procurement people — this is a dead end. They download a file they can't open, and the sharing exercise fails.

Third, cloud storage links have permission and access issues. Google Drive links sometimes require the recipient to "request access." Dropbox links may require a Dropbox account. Corporate firewalls may block cloud storage domains entirely. What should be a simple "look at this model" becomes a support ticket.

WeTransfer

WeTransfer is designed specifically for sending large files. You upload, enter the recipient's email, and they get a download link. The free tier allows files up to 2 GB, which handles virtually any 3D file. The interface is clean and the process is simple.

The limitation is the same as cloud storage: the recipient still has to download the file and find software to open it. WeTransfer is a file delivery tool, not a file viewing tool. It solves the "how do I get this large file to you" problem but not the "how do you look at it" problem.

WeTransfer links also expire after 7 days on the free tier. If the recipient doesn't download in time, you have to re-upload and re-send. For ongoing projects with multiple revision rounds, this creates unnecessary re-work.

ZIP and Split Files

Some people compress 3D files into ZIP archives to reduce size, or split large files into multiple parts that each fit within email limits. Both approaches add complexity without solving the core problem. ZIP compression typically reduces STL file size by 60-80% (binary STL compresses well), which can bring a 50 MB file under the 25 MB email limit. But it adds a step for the recipient: download, extract, then find software to open. And for files above 60 MB, even compressed ZIPs won't fit in email.

Split files are worse. The recipient has to download multiple attachments, reassemble them using a tool like 7-Zip, and then open the result. This is such a terrible user experience that most people would rather use a different sharing method entirely.

A Different Approach: Share a Viewer Link Instead of a File

All of the workarounds above share a common assumption: the recipient needs the actual file. But in many cases, they don't. They need to see the model — to understand the geometry, check the design, and provide feedback. The file itself is a means to that end, not the end itself.

GeometryViewer flips the approach. Instead of figuring out how to get a large file to someone, you upload the file once and share a link. The recipient clicks the link and sees the model in an interactive 3D viewer in their browser. No download, no software, no file size dance.

This approach has several advantages beyond just avoiding email limits:

• Instant viewing. The recipient clicks the link and the model appears. There's no download-extract-open pipeline. On a fast connection, the model is interactive within seconds.
• Works on any device. The viewer runs in any modern browser — desktop, phone, tablet. The recipient doesn't need specific software or a specific platform.
• No file management for the recipient. There's no downloaded file to deal with — no finding it in the Downloads folder, no "Open With" dialog, no wondering which application handles STL files.
• Mobile works properly. On a phone, a viewer link opens in the browser with touch controls. Compare this to downloading an STL on a phone, where the file just sits in the file system with no useful way to open it.

When You Actually Need to Send the File

There are legitimate cases where the recipient needs the actual 3D file, not just a view of it:

• 3D printing. The print shop needs the STL or 3MF file to slice and print. A viewer link doesn't help them.
• CAD integration. An engineer importing your model into their assembly needs the file in a compatible format.
• Archiving. If the recipient is storing the file for records or future use, they need the actual file.
• Modification. If someone needs to edit or modify the model, they need the source file (or at least an editable mesh).

For these cases, a file delivery tool (Google Drive, Dropbox, WeTransfer) is the right approach. But notice that these are all cases where the recipient is a technical user with specific software. For the much more common case of "I need someone to look at this model and tell me what they think," a viewer link is faster, simpler, and works for everyone regardless of technical ability.

The Hybrid Approach

For maximum flexibility, use both. Send the viewer link for immediate visual inspection, and include a file download link (via Google Drive or Dropbox) for recipients who need the actual file. The message might look like:

"Here's the updated enclosure design. You can view it interactively here: [GeometryViewer link]. If you need the STL for printing or CAD import, download it here: [Google Drive link]."

This covers both use cases without forcing anyone into a workflow that doesn't fit their needs. The project manager clicks the viewer link. The manufacturing engineer downloads the file. Both get what they need from a single message.

File Size Comparison Across Methods

To put the file size problem in context, here are typical 3D file sizes and how they interact with common sharing methods:

• Simple mechanical part (STL): 2-10 MB. Fits in email. But the recipient still needs software to open it.
• Detailed CAD assembly (STL): 20-80 MB. Exceeds email limits. Google Drive or WeTransfer needed for file delivery.
• High-res sculpt (OBJ/STL): 50-300 MB. Requires dedicated file transfer. May be slow to download on mobile data.
• Photogrammetry scan (GLB with textures): 100 MB - 1 GB+. Only WeTransfer or cloud storage can handle this. Downloading on mobile is essentially impractical.
• Textured game asset (GLB): 10-50 MB. May or may not fit in email depending on texture resolution.

In every case above, a viewer link works regardless of file size, and provides an immediate visual experience that no file download can match for speed and convenience.

Reducing File Size When You Must Send the File

If you do need to send the actual file and size is an issue, here are the most effective techniques for 3D files specifically:

• Use binary STL instead of ASCII. Binary STL files are 5-10x smaller than ASCII equivalents. Most CAD tools default to binary, but check your export settings.
• Reduce mesh resolution. If the file is for visual review (not printing), decimate the mesh. Going from 1 million triangles to 200,000 often has minimal visual impact but reduces file size by 80%.
• Compress textures. For GLB/OBJ with textures, reduce texture resolution from 4K to 2K. The visual difference is often imperceptible at typical viewing distances.
• Use GLB instead of OBJ + MTL + textures. GLB compresses geometry data internally and bundles everything into a single file, which is typically smaller than the equivalent OBJ bundle.
• ZIP the file. Binary STL compresses well — expect 60-80% size reduction. OBJ text format compresses even better. This alone can bring many files under email limits.