Loading Families — Save and load families into a project

Historical Context & Motivation

Before the advent of Building Information Modeling, architects and designers relied on libraries of hand-drawn symbols and CAD blocks that were little more than static geometric shapes. A door symbol on a plan conveyed visual meaning, but it carried no inherent data about manufacturer specifications, swing direction, or material properties. The paradigm shift introduced by parametric families in Revit fundamentally changed this relationship: every component placed in a project is an intelligent, data-rich object whose geometry and metadata respond dynamically to user-defined parameters. Understanding how to load families into a project is therefore central to working productively in Revit, because without the correct families, a model remains an empty shell devoid of meaningful content.

The question that arises for every Visual Arts student beginning to work with Revit is deceptively simple: how do I get the content I need—doors, windows, furniture, lighting fixtures, custom sculptural elements—into my project? The answer involves understanding the family file ecosystem, the loading mechanisms Revit provides, and the strategies for keeping a project file lean and well-organized. This lesson addresses each of these concerns in depth.

Core Principles & Definitions

At the heart of every Revit project lies a hierarchical content system built on three tiers: categories, families, and types. A category is a broad classification defined by Revit itself—Doors, Walls, Furniture, Generic Models, and so on. Within each category, families define a distinct object class (for example, a "Panel Door" family), and within each family, types represent dimensional or material variants (a 36" × 84" single-panel oak door versus a 30" × 80" version). When you load a family into a project, you are importing one or more types along with all the parametric logic, geometry definitions, and metadata that define the family.

Visual Explanation — The Family Loading Workflow

The flowchart illustrates that loading a family is not a single rigid procedure but rather a set of converging paths that all result in the same outcome: a family definition residing inside your project's database. The most common route begins at the Insert tab → Load Family command on the Ribbon, which opens a standard file browser pointed at the default Revit library path. You can navigate to your office server, a downloaded folder, or any local directory containing .rfa files. Once loaded, the family and its types appear in the Project Browser under the appropriate category heading—Doors, Furniture, Generic Models, and so on—ready for placement into views. The bottom portion of the diagram highlights the equally important reverse operation: editing a family that is already loaded, refining it in the Family Editor, and either reloading it directly into the open project or saving it as an independent .rfa file for future use.

How Family Loading Works — The Mechanism

What Happens When You Load a Family?

Loading a family is, at a technical level, an act of embedding a complete parametric definition into the project's central database. Revit copies the family's geometry engine, its parameter table, material mappings, visibility settings, and type catalog entries from the external .rfa file into the project file (.rvt). From that moment onward, the project file carries its own internal copy of the family—modifications to the original .rfa on disk will not automatically propagate into the project. This is a crucial concept: there is no live link between the source .rfa and the loaded family. If the source family is updated, you must explicitly reload it into the project to apply changes.

Step-by-Step: The Load Family Command

1. Navigate to Insert → Load Family on the Ribbon. The standard Windows file-open dialog appears, defaulting to the Revit library folder installed with the software.
2. Browse to the .rfa file you wish to load. You may select multiple .rfa files at once by holding Ctrl or Shift.
3. Click Open. If the family has a type catalog (.txt file in the same directory), Revit presents a dialog asking which types to load—select only the types you need to minimize file bloat.
4. Verify in the Project Browser. Expand the Families node under the relevant category to confirm the family and its types now appear.
5. Place instances using the Component command (Architecture → Component → Place a Component) or by selecting the family from a host-specific placement command (e.g., a door family loads via Architecture → Door).

Type Catalogs — Loading Selectively

A type catalog is a plain-text file (with a .txt extension and the same filename as the .rfa) that lists all available types and their parameter values in a comma-separated format. When Revit detects a matching type catalog during loading, it displays a selection dialog rather than importing every type. This mechanism is especially important for families with dozens or hundreds of types—such as structural steel sections or lighting fixture families with numerous lamp configurations. For Visual Arts students working with large furniture or fixture libraries, type catalogs prevent unnecessary data from inflating the project file. Only the types you select are embedded; the rest remain external until explicitly loaded later.

Detailed Breakdown — Family Sources & Organization

Knowing where to find families is just as important as knowing how to load them. The Revit ecosystem offers several distinct sources, each with its own strengths and caveats. A well-organized office maintains a curated library on a shared server or cloud drive, with families that have been vetted for naming conventions, parameter consistency, and geometric quality. Downloading families indiscriminately from the internet—while tempting—can introduce inconsistent naming, excessive geometric complexity, and parameters that conflict with your project standards.

Worked Example — Loading a Custom Chair Family

Imagine you are designing an interior gallery space and need to place a specific lounge chair that your studio has modeled as a custom Revit family. The family file, "VA_Chair_Lounge_Modern.rfa," resides on your office server along with a type catalog listing four fabric color variants. Here is the complete procedure from loading through placement and eventual re-export.

Strengths, Limitations & Best Practices

The family loading system in Revit is remarkably powerful, yet it carries important constraints that every designer must understand to maintain project health and collaborative efficiency. The table below compares the key strengths of the system against its most common limitations, followed by practical best practices that bridge the gap.

Connection to Advanced Family Management

The basic loading workflow covered in this lesson is the foundation upon which several advanced family management strategies are built. As you progress in your Revit proficiency, particularly within collaborative studio projects or professional practice, you will encounter techniques that extend, automate, or govern the family loading process in sophisticated ways.

For Visual Arts students, the most immediately relevant advanced topic is likely the intersection of adaptive component families with the loading workflow. Adaptive families allow you to create geometrically complex, point-driven forms—think parametric façade panels or freeform sculptural elements—that are loaded and placed like any other family but respond to host surfaces and adaptive points. Mastering the standard loading mechanics covered here is a prerequisite for working with these more advanced family types, because the same Insert → Load Family → Place workflow applies, and the same attention to file organization, type management, and version control remains essential.

Practice Problems

Lesson Summary