A Comprehensive Guide to 3D File Types for Architectural Design
In architectural practice, a 3D file is rarely transferred for geometry alone. Depending on the format, it may also contain layers, object classifications, materials, textures, coordinates, quantities, families, animations, or construction information. Choosing the wrong format can therefore produce a model that looks correct on screen but has lost the information required for coordination, documentation, rendering, or fabrication.
The correct format depends on what the receiving team needs to do with the model. A structural consultant exchanging coordinated building elements requires a different file from a visualization artist preparing a rendered scene, while a physical model requires watertight geometry rather than BIM data. This guide explains the principal 3D file formats used in architecture, what each format preserves, and where conversion commonly causes problems.
Native, exchange, and delivery formats
Architectural file formats can be divided into three broad categories. Native formats, such as RVT and SKP, preserve the working structure of a specific application. Exchange formats, including IFC, DWG, DXF, OBJ, and FBX, move information between different programs. Delivery formats, such as GLB and STL, prepare geometry for a particular destination such as a web viewer, real-time engine, or 3D printer.
No exchange format reproduces every feature of the original authoring file. Parametric relationships may become fixed geometry, BIM objects may lose classifications, procedural materials may be converted into images, and complex curves may be tessellated into polygon meshes. File selection should therefore be based on the information that must survive the transfer, not only on whether the receiving software can open the extension.
Principal 3D file formats used in architecture
| Format | Primary role | Information commonly preserved | Main limitation |
|---|---|---|---|
| DWG | CAD drafting and model exchange | Lines, surfaces, solids, layers, blocks, dimensions, and coordinates | Application-specific objects may not translate correctly outside Autodesk workflows |
| DXF | General CAD exchange | Geometry, layers, and basic annotations | Files can be larger than DWG and may lose advanced object behavior |
| RVT | Revit project authoring | BIM objects, families, views, schedules, phases, and project relationships | Primarily intended for Revit-based workflows |
| IFC | Open BIM coordination | Geometry, classifications, properties, spaces, systems, and relationships | Translation quality depends on export settings and software implementation |
| STL | 3D printing | Triangulated surface geometry | Does not normally preserve materials, BIM properties, hierarchy, or units reliably |
| OBJ | Mesh and visualization exchange | Polygon geometry, UV coordinates, normals, and basic material references | Uses separate material and texture files and does not preserve BIM intelligence |
| FBX | Visualization and real-time production | Meshes, hierarchy, cameras, materials, lights, and animation | Material translation varies between rendering applications |
| SKP | SketchUp modeling | Groups, components, layers or tags, scenes, materials, and basic metadata | Complex models can become heavy and version compatibility must be checked |
| 3DS | Legacy mesh exchange | Basic meshes, cameras, lights, and materials | Legacy limits make it unsuitable for most current production workflows |
| glTF / GLB | Web, AR, and real-time delivery | Optimized meshes, PBR materials, textures, hierarchy, and animation | Designed for delivery rather than CAD or BIM authoring |
DWG and DXF for CAD information
DWG remains one of the principal formats for architectural drawings, consultant backgrounds, surveys, fabrication details, and two-dimensional documentation. It can also contain three-dimensional surfaces and solids, although its most common architectural role remains the exchange of precise CAD information.
Its main advantage is the ability to preserve layers, line types, blocks, dimensions, and drawing coordinates. However, a DWG file may contain application-specific objects that another program interprets only as simplified geometry or proxy objects. A file being readable does not necessarily mean that every object remains editable.
DXF was developed to facilitate the exchange of drawing information between CAD systems. It is useful when a receiving application cannot read a particular DWG version or when geometry must pass through a more broadly documented exchange structure. DXF is not automatically safer than DWG, however. Complex objects may still be simplified, and ASCII DXF files can become considerably larger than equivalent binary files.
Before exchanging either format, teams should confirm the drawing units, insertion point, coordinate system, layer naming, and whether external references have been bound or supplied separately.
RVT and IFC for BIM workflows
An RVT file is not simply a container for three-dimensional geometry. It is a Revit project database containing elements, families, constraints, views, sheets, schedules, phases, design options, and relationships between building components. It is therefore most effective when the project team works within compatible Revit environments.
Sharing an RVT file also requires attention to software versions, linked models, worksets, coordinates, ownership, and model-cleaning procedures. A receiving team may be able to view the model but still lack linked files, custom families, or the information required to reproduce the complete project environment.
IFC provides an open method for exchanging structured building information across different BIM platforms. Unlike a general mesh format, it can distinguish walls, slabs, doors, spaces, systems, and other building elements while carrying selected properties and relationships.
IFC should not be treated as a one-click guarantee of perfect interoperability. The exported result depends on the IFC version, Model View Definition, classification mapping, property sets, coordinate setup, and the capabilities of both the authoring and receiving applications. An IFC model intended for coordination may require different settings from one prepared for quantity extraction or asset information.
OBJ and FBX for visualization
OBJ is a widely supported mesh format suitable for transferring static architectural geometry to modeling, rendering, and sculpting applications. It can preserve polygon geometry, surface normals, UV coordinates, and basic material assignments. Materials are commonly stored in a separate MTL file, while texture images remain external assets.
This separation makes file management important. Sending the OBJ without its MTL file and texture folder may produce an untextured model. OBJ also lacks the parametric and semantic structure of CAD and BIM formats, so a wall generally arrives as mesh geometry rather than an editable building element.
FBX supports more complete visualization scenes, including model hierarchy, cameras, lights, animation, and material references. It is commonly used between applications such as 3ds Max, Blender, Unity, and Unreal Engine, although rendering platforms may interpret shaders and material parameters differently.
For architectural visualization, FBX is generally more suitable than OBJ when hierarchy, scene organization, cameras, or animation must be retained. OBJ remains useful for stable static geometry and workflows where broad compatibility is more important than scene complexity.
SKP for conceptual architectural modeling
SKP is the native SketchUp format and is widely used during concept development, massing, interior studies, and design presentations. It can preserve groups, components, tags, scenes, section planes, materials, and geolocation information within a relatively accessible modeling environment.
The main difficulty is not the format itself but model organization. Excessive polygon counts, imported warehouse objects, duplicated materials, hidden geometry, and poorly structured components can produce unnecessarily heavy files. Before exchange, unused content should be purged and the model should be checked for reversed faces, nested geometry, and incorrect coordinates.
SKP version compatibility should also be confirmed. When the receiving software cannot read the current file version, saving to an earlier version or exporting through IFC, DWG, OBJ, FBX, or glTF may be necessary, depending on the purpose of the transfer.
STL and the requirements of 3D printing
STL describes the external surface of a model as a collection of triangles. It remains common in 3D printing because it is simple and widely accepted by slicing software. That simplicity also explains its limitations: it does not normally preserve object names, BIM properties, assembly hierarchy, materials, or dependable unit information.
An architectural model cannot be printed successfully merely because it has been exported as STL. The geometry should form closed volumes, have consistent surface normals, contain no unintended intersections, and respect the minimum thickness supported by the printing method. Railings, fins, glazing frames, and other elements that appear acceptable on screen may be too thin to fabricate at model scale.
Where supported, 3MF can provide a more structured alternative for additive manufacturing because it can carry units, materials, colors, and additional manufacturing information. STL nevertheless remains useful when the printing workflow requires only clean, watertight geometry.
glTF and GLB for web-based 3D content
glTF was developed as an efficient delivery format for loading three-dimensional scenes into web viewers, real-time applications, and augmented-reality experiences. It supports meshes, hierarchy, animation, textures, and physically based rendering materials without carrying the full complexity of an authoring file.
A glTF asset may reference separate binary and texture files, while GLB packages the principal components into one binary file. GLB is therefore convenient for publishing an interactive architectural model because fewer external files need to be managed.
Neither format should replace the original CAD or BIM model. They are optimized for display and transmission, not for producing construction documents, modifying parametric elements, or coordinating engineering systems.
Why 3DS is now a legacy format
The 3DS format belongs to an earlier generation of 3D Studio workflows. Although some applications continue to import it, the format has restrictive limits related to mesh structure, object naming, and material handling. Its presence in older model libraries does not make it an appropriate choice for a new project.
When an archived 3DS model must be reused, it is usually better to open it in compatible software, inspect the geometry and materials, and then save a controlled production copy in a current format such as FBX, OBJ, or the native format of the receiving application.
Practical compatibility between architectural software
Software support changes according to the application version, operating system, subscription level, and installed plug-ins. The following table describes the most practical exchange routes rather than suggesting that every listed format behaves as a native editable file.
| Software or workflow | Native project format | Common incoming formats | Common outgoing formats | Important qualification |
|---|---|---|---|---|
| AutoCAD | DWG | DWG, DXF and supported CAD references | DWG, DXF and selected fabrication or exchange formats | Availability of some 3D formats depends on the AutoCAD toolset and version |
| Revit | RVT | RVT links, IFC, DWG, DXF, SKP and other supported CAD formats | IFC, DWG, DXF, FBX, STL and other published formats | Imported geometry does not automatically become native Revit building elements |
| SketchUp | SKP | DWG, DXF, IFC, STL, glTF or GLB, depending on version and plan | SKP, DWG, DXF, IFC, OBJ, FBX, STL, DAE and glTF or GLB, depending on version and plan | Professional exchange options may not be available in every edition |
| 3ds Max | MAX | FBX, OBJ, DWG, DXF, STL and supported Revit workflows | FBX, OBJ, DWG, DXF, STL and other visualization formats | Material conversion depends on the source renderer and target renderer |
| Blender | BLEND | FBX, OBJ, STL, glTF, USD and other mesh formats | FBX, OBJ, STL, glTF, USD and other mesh formats | DWG, SKP and structured IFC workflows commonly require add-ons or conversion |
| Rhino | 3DM | DWG, DXF, SKP, STEP, IGES, FBX, OBJ, STL and glTF | DWG, DXF, SKP, STEP, FBX, OBJ, STL and glTF | Structured BIM exchange may require tools such as VisualARQ or another IFC workflow |
| Unity | Unity project | FBX and supported mesh formats; CAD and BIM through dedicated industry tools | Application-specific builds and asset packages | FBX is commonly preferred for standard production import |
| Unreal Engine | Unreal project | FBX, Datasmith and supported real-time asset formats | Application-specific builds and packaged projects | Datasmith is often more effective than a basic mesh export for architectural scenes |
| 3D printing | Printer or slicer project | STL, 3MF and sometimes OBJ | Printer-specific toolpaths | The source geometry must be repaired, scaled, and checked for fabrication |
Choosing the format according to the task
| Required outcome | Preferred format | Reason |
|---|---|---|
| Exchange technical drawings | DWG or DXF | Preserves precise CAD geometry, layers, and drawing information |
| Continue work inside Revit | RVT | Retains Revit elements, families, relationships, and project structure |
| Coordinate between different BIM platforms | IFC | Transfers classified building objects and selected properties through an open standard |
| Transfer a static model for rendering | OBJ | Provides broad support for mesh geometry and UV mapping |
| Transfer a complete visualization scene | FBX | Can retain hierarchy, cameras, lights, and animation |
| Continue conceptual modeling in SketchUp | SKP | Preserves SketchUp groups, components, scenes, and tags |
| Publish an interactive model online | GLB | Packages optimized geometry, textures, and materials into a portable file |
| Prepare a physical architectural model | STL or 3MF | Produces geometry suitable for slicing and additive manufacturing |
| Archive an editable project | Native file plus open exchange copy | Preserves authoring information while reducing dependence on one application |
What can be lost during conversion?
- Parametric behavior: Editable walls, families, modifiers, and constraints may become fixed geometry.
- BIM properties: Classifications, system relationships, quantities, and asset information may be omitted or mapped incorrectly.
- Materials: Procedural shaders and renderer-specific settings may not reproduce in another application.
- Object hierarchy: Groups, components, linked models, and instances may be merged or duplicated.
- Coordinates and scale: Incorrect units, origins, or geographic coordinates can displace or resize the model.
- Curved geometry: NURBS and analytical surfaces may be converted into triangulated meshes with insufficient resolution.
- References: Textures, linked models, fonts, and external drawings may not be embedded in the exchanged file.
Model exchange checklist
- Confirm what the recipient intends to do with the model.
- Agree on the software version, file format, units, and coordinate system.
- Remove unnecessary objects, duplicated geometry, and unused materials.
- Check object naming, layers, classifications, and model hierarchy.
- Package linked files, textures, and other external references where required.
- Open the exported file in the receiving application or an independent viewer.
- Compare dimensions, coordinates, object counts, and critical properties with the source model.
- Record the export settings and retain the native source file.
A file extension confirms how information has been packaged, but it does not confirm the quality or completeness of the model. Reliable exchange requires a defined purpose, agreed export settings, and verification after conversion. For this reason, the most dependable project archive usually contains both the native authoring file and an appropriate open or widely supported exchange copy.
Learn more about our project process through How We Work, or explore the architectural practice through Who We Are.
Technical references
- Autodesk: Standards and file formats supported by Revit
- buildingSMART: IFC and Model View Definitions
- SketchUp: Importing and exporting CAD files
- Blender: Importing and exporting files
- McNeel: Rhino import and export file formats
- Unity: Model file formats reference
- Khronos Group: glTF specification and overview
- Epic Games: Datasmith import process
