A file is not enough.

It is not presented as universal compatibility or as a certified integration with every manufacturer. The audited import recognizes a broad set of extensions and can infer a probable origin from the file name or path. That inference is a classification aid, not a reading of the proprietary schema or a guarantee of interoperability. The responsible way to check a workflow is to test a representative package from the scanner, the design software, and the export route your team uses. The synthetic case TL-7316 on this page shows that method without attributing certification to any specific vendor.

The audited ZIP route can accept 3D and scanner files, clinical images, PDFs, and auxiliary documents within an allow list. Recognized extensions include STL, PLY, OBJ, 3MF, DCM/DICOM, and several proprietary containers or projects, plus JPG, PNG, WEBP, HEIC, TIFF, PDF, TXT, JSON, XML, CSV, and MTL. Recognizing the extension determines how the file is kept and initially classified; it does not prove that the content is clinically correct, that every geometry can be previewed, or that a proprietary package has been decoded.

It means the extension and some signals in the name allow it to be placed in an initial category. It does not mean the file has been accepted for fabrication. The clinical function — working arch, antagonist, bite, preparation, scan body, photograph, or document — can be suggested by name heuristics, but a person must confirm it. TrazaLab keeps that difference visible: recognizing organizes the package; reviewing establishes its function; approving or returning remains a human decision inside the case.

In the audited journey, direct preparation for preview is limited to STL, OBJ, and PLY. Other formats can be kept as case files without becoming visible geometry. STL can receive basic, sampled statistics within concrete limits, but that reading is not mesh repair, clinical analysis, automatic margin detection, or validation for fabrication. An OBJ may need its MTL and related textures; recognizing the files does not guarantee that every material or relationship is rebuilt perfectly.

The implementation can keep recognized proprietary containers and projects and has specific heuristic-based routes for some package types. That is not equivalent to decoding all of their internal objects through a manufacturer-certified schema. The page deliberately separates keeping from interpreting: the package can travel with the case and remain available for the appropriate application, while the interface avoids inventing a preview or claiming to have understood every proprietary datum.

DICOM files are classified as a separate category and their review belongs to the DICOM workspace with its own scope. A file ending in DCM or DICOM does not prove that any transfer syntax, compression, color, device, or study is compatible. This page does not promise complete anonymization, diagnosis, PACS interoperability, DICOM-to-STL conversion, or universal reconstruction. The goal of the package is to keep the relationship with the case; reading capability must be confirmed in the corresponding DICOM workspace.

It must not be presented as automatic clinical validation. Names can help propose functions such as upper arch, lower arch, bite, preparation, or antagonist, but the result depends on how the package was exported and needs human review. The missing-bite scene on this page explains a process control: compare what was received with what the treatment requires, flag the missing item, and return a question to the owner. TrazaLab structures the verification; it does not by itself declare that the occlusion, the margin, or the case are correct.

The verified generic ZIP route uses a top-level ZIP file, with a configured maximum of 2 GB, up to 5,000 entries, and up to 8 GB uncompressed. The separate smart-import route for loose files applies other limits: up to 60 files, under 900 MB per batch, and 220 MB per file. These numbers describe the audited implementation, not a promise that every package within the limit is safe, readable, or acceptable. No anti-malware scanning, universal quarantine, resumable upload, or clinical content validation is attributed.

After human confirmation, the audited route keeps the original ZIP and the accepted files, relates them to the case, and records the import event. The page represents that provenance as a visible chain between package, function, site FDI 26, treatment, version, and owner. Keeping that relationship helps explain what the laboratory received and which version was reviewed; it does not turn the history into an immutable signature, does not certify that the file is manufacturable, and does not replace the access control, privacy, or retention each organization must apply.