Your lab receives STL scans via email, CBCT images on WhatsApp, clinical photos through WeTransfer, and prescriptions by text message. Nothing is linked to anything. Files expire, versions conflict, and cases get delayed. This guide explains how to fix that — permanently.
A dental lab is not a design studio that receives one file per project. A single implant case can involve an STL scan from the intraoral scanner, a CBCT DICOM dataset from the radiologist, six clinical photographs from the dentist, a shade reference image taken under calibrated lighting, a PDF prescription with margin notes, and a corrected STL uploaded three days later when the first scan had a void in the margin area.
Now multiply that by 30 cases per day. That is the reality of dental lab file management: a constant flow of large, mission-critical files arriving from multiple clinics through multiple channels, with no standard format, no standard naming convention, and no guarantee that the file you are looking at is the current version.
The consequences are predictable and expensive. A technician designs a crown from the wrong STL version. A case is delayed because the CBCT link expired over the weekend. A remake happens because the corrected shade photo was in a WhatsApp thread that nobody checked. According to industry data, approximately 23% of dental lab remakes trace back to file-related errors — wrong version, missing file, corrupted transfer, or misattributed image.
This is not a technology problem. Labs have plenty of technology. The problem is that files are disconnected from cases. An STL sitting in an email inbox is just a file. The same STL linked to case #4721, tagged as “v2 — corrected margin,” timestamped, and visible to everyone on the case — that is information. The difference between those two things is the difference between chaos and control.
Six categories of files flow through a dental lab daily. Each has different size characteristics, different vulnerability to corruption, and different compliance implications. Understanding them is the foundation of any file management strategy.
The workhorse of dental CAD/CAM. Triangulated surface mesh from intraoral scanners. Contains geometry only — no color, no texture, no metadata. Binary format is standard; ASCII is larger and slower.
Three-dimensional radiographic data from cone beam CT scanners. Contains patient metadata in headers (HIPAA/GDPR sensitive). Essential for implant planning, sinus lifts, and bone density assessment.
Polygon mesh with per-vertex color data. Used by face scanners and some intraoral scanners. Preserves tissue color information critical for shade matching and soft tissue modeling.
3D geometry with material and texture mapping support. Often paired with .mtl (material) and .jpg (texture) files. Used in complex aesthetic cases and digital smile design workflows.
Intraoral photographs, shade references, preparation photos, and try-in documentation. Often the most numerous files per case. Quality depends entirely on the photographer’s protocol and equipment.
Lab prescriptions, treatment plans, consent forms, and design approval documents. Often contain handwritten annotations. The legal record of what was requested versus what was delivered.
The hidden cost of file diversity: A single full-arch implant case can generate 800 MB to 3 GB of files across all categories. That is why email’s 25 MB limit forces labs to split files across multiple channels — creating the fragmentation that causes errors.
These are the practices that cause remakes, delays, and compliance violations in dental labs. Most labs commit at least three of them daily.
WeTransfer free links expire in 7 days. Google Drive links can be revoked. A clinic sends a CBCT on Friday, the lab opens the case Monday — and the link is dead. The case is delayed by a full business day while the file is re-requested. With WeTransfer, there is no notification when a link expires.
Gmail caps attachments at 25 MB. Outlook at 20 MB. A single full-arch STL scan can be 200 MB. Labs receive truncated files, split archives, or “the file was too big so I compressed it” messages — and compressed STL files are corrupted STL files. Email was never designed for dental file sharing.
WhatsApp compresses images to under 1 MB — destroying the resolution needed for shade matching. Some email clients silently downscale attached photos. Binary STL mesh data altered by even one byte can produce thousands of invalid triangles. The sender thinks the file was delivered; the lab receives garbage.
The clinic sends a corrected STL. It arrives in a separate email, a different WhatsApp thread, or a new WeTransfer link. The technician who started the case does not see it. The original file gets used. The remake costs €200+ and adds three days. There is no timestamp trail, so the dispute is unresolvable.
The STL is in email. The photos are on WhatsApp. The prescription PDF is in a shared Drive folder. The CBCT is on a USB stick. Five files for one case, scattered across five systems, with no connection between them. When a new technician picks up the case, they spend 15 minutes just finding the files — if they find them all.
These are not aspirational. They are the minimum standard for a lab that wants to eliminate file-related errors and comply with data protection regulations.
Every file belongs to a case. Not to a folder, not to an email thread, not to a chat. When you open a case, every file associated with it is visible in one place — STLs, DICOMs, photos, prescriptions, design files, all of them.
Every upload creates a new version. Previous versions are preserved, not overwritten. The full history — who uploaded what, when, and which version is current — is visible to everyone on the case, eliminating “which STL is the right one?” disputes.
Files do not expire. No 7-day links, no “please re-send,” no storage caps that force deletion. Once uploaded, a file is retrievable for the life of the case — and beyond, for warranty claims, insurance disputes, and audit requests.
Find any file by case number, patient name, clinic, date, file type, or technician. A lab processing 30 cases per day generates hundreds of files per week. Without search, files are effectively lost even if they technically exist somewhere in the system.
Encrypted in transit (TLS 1.3) and at rest (AES-256). Role-based access control — the front-desk coordinator does not need access to CBCT data. Audit trail for every file access. Compliant with GDPR and HIPAA where applicable.
Any authorized team member can access the file from any device — desktop in the design room, tablet on the bench, phone on the go. No VPN required, no special software, no IT department needed to set up access. Cloud-native, browser-based.
Every channel has limits. Most of those limits were not designed with dental files in mind. This table shows what each platform can handle and where it breaks down for typical dental lab file types.
| Channel | Max File Size | Single STL (Full Arch) | CBCT Dataset | Case-Linked | Version Control | Permanent |
|---|---|---|---|---|---|---|
| Email (Gmail/Outlook) | 20–25 MB | × Too large | × Impossible | × | × | Inbox-dependent |
| 100 MB | Partial (small scans) | × Too large | × | × | Compresses files | |
| WeTransfer (Free) | 2 GB | ✓ | ✓ | × | × | × Expires 7 days |
| Google Drive (Free) | 15 GB total | ✓ | ✓ | × | Basic | Until storage full |
| Dropbox (Free) | 2 GB total | Limited | × Fills storage | × | 14 days | Until storage full |
| TrazaLab | 5 GB per file | ✓ | ✓ | ✓ | ✓ | ✓ |
The real bottleneck is not file size — it is context. Google Drive can store your files. WeTransfer can transfer them. But neither links them to a case, tracks versions, or creates an audit trail. That is why labs end up with 50 GB of files and no idea which version of which scan belongs to which patient.
Dental files are not ordinary business documents. DICOM headers contain patient names, dates of birth, and medical record numbers. Clinical photographs show identifiable faces. Prescription PDFs contain protected health information. Every file channel your lab uses must meet the security standards required by HIPAA (United States), GDPR (European Union), and local data protection laws.
Using personal WhatsApp, free email accounts, or consumer cloud storage for patient files is not a grey area. It is a compliance violation that exposes your lab to fines, lawsuits, and reputational damage. Here are the four pillars of compliant dental file management.
Files must be encrypted during transfer (TLS 1.2 minimum, TLS 1.3 preferred) and while stored (AES-256 at rest). This means that even if a server is breached, the files are unreadable without the decryption keys. Consumer-grade tools like WhatsApp encrypt messages but not file metadata or storage.
Every file access, download, and modification must be logged with a timestamp and user identity. When a compliance auditor or a patient asks “who accessed my CBCT data and when?” your system must produce a complete answer. Email and messaging apps cannot do this.
Role-based permissions determine who can view, download, upload, or delete files. The receptionist booking appointments does not need access to radiographic data. The technician working on case #4721 does not need access to case #4722. Granular access control is not optional under GDPR — it is Article 25 (Data Protection by Design).
Where are the files physically stored? For EU labs, GDPR requires that personal data stays within the EEA unless adequate safeguards exist. How long must files be retained? Medical record retention laws vary by jurisdiction — Spain requires 5 years minimum. Your file system must support configurable retention policies, not just “delete when storage is full.”
If your current file management workflow involves any combination of personal email, WhatsApp, free cloud storage, and USB drives, you are almost certainly non-compliant. The question is not whether to fix this, but how quickly you can do it before an audit or a data breach forces the issue. For a deeper look at GDPR requirements specific to dental labs, see our GDPR compliance guide.
TrazaLab was built by a dental lab, for dental labs. File management is not an afterthought bolted onto a CRM — it is the foundation of the entire platform. Here is what that means in practice.
Upload full CBCT datasets, high-resolution STL scans, and multi-file OBJ packages without splitting, compressing, or switching tools. Resumable uploads mean interrupted transfers pick up where they left off.
Every file is automatically attached to its case. No manual organizing, no folder hierarchies, no searching through email threads. Open the case, see every file — STLs, photos, DICOMs, prescriptions.
Every new upload creates a version, not a replacement. Full history trail with timestamps and uploader identity. Any version is recoverable. No more “which scan is the right one?” disputes.
TLS 1.3 in transit, AES-256 at rest. Role-based access control and complete audit logging. GDPR-compliant data residency within the EU. Built for healthcare-grade trust.
Find any file by case number, patient, clinic, date, or file type. Full-text search across prescriptions and case notes. When you need to find the CBCT from three months ago, it takes seconds, not minutes.
Files do not expire. No 7-day links, no storage quotas that force purges. Your files are available for as long as your account exists — for warranty claims, insurance disputes, or audit requests years later.
This guide covers the principles. For a detailed walkthrough of how TrazaLab’s file system works in practice — upload workflows, case attachment, version comparison, and clinic sharing — see the dedicated Clinical File Management page. For a broader look at the full platform including case capture, digital prescriptions, and clinic communication, visit the Product page.
Even when files arrive intact, STL meshes frequently contain errors that prevent clean CAD/CAM processing. Understanding these issues is part of dental lab file management because a file that opens is not necessarily a file that works.
Edges shared by more than two triangles, or triangles with inconsistent face normals. These create ambiguous surfaces that CAM software cannot tool-path correctly. Common cause: intraoral scanner stitching errors where overlapping scan segments were merged improperly.
Missing triangles in the mesh surface, often in areas that were difficult to scan — deep margin lines, interproximal areas, or lingual surfaces. Small holes can be auto-repaired; large gaps require a re-scan because repair algorithms fill them with flat or interpolated surfaces that do not represent the actual anatomy.
Triangle faces pointing inward instead of outward. The mesh appears correct visually but CAM software reads the geometry inside-out, producing impossible tool paths. Usually caused by file format conversion errors (e.g., exporting from one scanner software to another).
Triangles that pass through other triangles, creating impossible geometry. Often invisible in a visual inspection but cause slicing errors in CAM processing. Common in files that were manually edited or combined from multiple scan sessions.
TrazaLab includes a built-in STL mesh repair tool that detects and fixes common issues automatically — non-manifold edges, small holes, inverted normals, and duplicate vertices. For files with severe damage, it flags the issue before the technician begins design work, preventing wasted time on an unworkable scan.
The best method is a platform that links files directly to cases, supports large uploads (STL files for full-arch scans can exceed 200 MB), and maintains version history. Email fails at 25 MB. WeTransfer works for size but creates orphaned links with no case context. Dedicated dental lab platforms like TrazaLab support files up to 5 GB with automatic case linking, version tracking, and resumable uploads so interrupted transfers pick up where they left off.
Dental labs routinely handle six file categories: STL files (surface meshes from intraoral scanners, 5–250 MB), DICOM/CBCT files (volumetric imaging data, 50 MB–2 GB), PLY files (color mesh scans, 10–300 MB), OBJ files (textured 3D models, 20–500 MB), clinical photographs in JPEG/PNG format (2–15 MB each), and PDF prescriptions and reports (1–10 MB). A lab processing 30 cases per day can easily generate 5–10 GB of new files daily.
Yes. Dental files containing patient identifiers — DICOM headers, clinical photographs, prescription PDFs — are protected health information under HIPAA (US) and personal health data under GDPR (EU). Labs must ensure files are encrypted in transit and at rest, access is limited to authorized personnel, and there is an audit trail showing who accessed which files. Using consumer tools like personal WhatsApp or free WeTransfer accounts for patient files creates compliance liability.
STL corruption during sharing typically happens for three reasons: (1) email systems or messaging apps compress attachments automatically, altering the mesh data; (2) file transfers are interrupted mid-upload with no resume capability, producing truncated files; (3) files are renamed or converted during download, breaking the mesh structure. Binary STL files are particularly vulnerable to compression damage because the data is not human-readable — a single altered byte can invalidate thousands of triangles.
Every file revision should be automatically versioned and linked to the case it belongs to, with a timestamp and the identity of who uploaded it. The previous version should never be deleted — overwriting is the single most common cause of rework disputes (“I sent the corrected scan” vs “we never received it”). Good version control means any team member can see the full file history for a case, compare versions, and identify exactly when a change was made and by whom.
You can, but generic cloud storage creates three problems for dental labs: (1) files are not linked to cases — you end up with a folder hierarchy that breaks down as volume grows; (2) there is no dental-specific workflow — no prescription attachment, no case status tracking, no clinic communication thread tied to the files; (3) compliance is your responsibility — you must configure encryption, access controls, and audit logging yourself, and most labs do not. Generic cloud storage works for document storage. It does not work for dental lab case management.
TrazaLab gives your lab 5 GB uploads, automatic case linking, version history, and GDPR-compliant security — from day one. Start your free 14-day trial. Full features, no credit card.