01 / 20

Revit Family
Types

Master the three family categories in Autodesk Revit: system, loadable, and in-place. Understand when and why to use each one.

Autodesk Revit

What Is a Family in Revit?

In Revit, a family is the fundamental building block of every model. Every element you place: walls, doors, columns, furniture, annotations: belongs to a family. A family defines an element's geometry, parameters, and behavior.

The Family Hierarchy

Category Family Type Instance e.g. Doors e.g. Single Flush e.g. 36" x 84" Placed in model

Why Do Families Matter?

1
Consistency: Families ensure every instance of a wall, door, or fixture shares the same rules and parameters.
2
Efficiency: Change one type, and every instance updates automatically across the model.
3
Scheduling: Accurate schedules and quantity takeoffs depend on properly organized families.
4
Collaboration: Standard families make it easy for teams to share and understand the model.

The Three Family Types

System Families Built into Revit Cannot be loaded from external files Walls, Floors, Roofs Loadable Families Created externally in Family Editor Loaded as .rfa files Doors, Windows, Furniture In-Place Families Created directly inside the project Unique one-offs Custom Shapes, Sculpted Forms

System Families Explained

System families are predefined in Revit and control the behavior of fundamental building elements. They are not stored as external files: they exist only within Revit project files or templates.

Walls
Compound layers defining structure, insulation, and finish
Floors
Horizontal assemblies with multiple layers and slopes
Roofs
Sloped or flat assemblies following the building footprint

Loadable Families Explained

Loadable families are the most flexible type. They are created in the Family Editor, saved as .rfa files, and loaded into any project. They support custom parameters, nested families, and type catalogs.

Component
Doors, windows, furniture, fixtures: 3D objects placed in the model
Annotation
Tags, symbols, title blocks: 2D elements for documentation
Profile
Sweep and reveal profiles used by system families like walls and railings

In-Place Families Explained

In-place families are created directly within the project for unique geometry that won't be repeated. They reference existing model geometry (levels, walls, grids) for placement, making them context-dependent.

1
Unique geometry: Custom-shaped reception desks, sculpted canopies, or freeform facades.
2
Context-specific: They reference the existing model, so they "know" about nearby walls and levels.
3
Use sparingly: Overuse increases file size and reduces model performance.

Key Distinction: Reuse vs. Uniqueness

Reusable System Families Loadable Families Multiple instances across the project vs. Unique In-Place Families One-off geometry in one project only

Side-by-Side Comparison

System Loadable In-Place
File format Embedded in .rvt .rfa files Embedded in .rvt
Created in Revit project Family Editor Project (in-place)
Reusable Transfer Std. ✓ Yes ✕ No
Examples Walls, Floors Doors, Furniture Custom sculpts
Type catalog ✕ ✓ ✕

How to Choose the Right Family

1
Identify the element: Is it a wall, floor, roof, ceiling, stair, or ramp? If yes, it is a system family.
2
Check for reuse: Will this element appear in multiple locations or projects? If yes, build a loadable family (.rfa).
3
Evaluate uniqueness: Is the geometry truly one-of-a-kind and context-specific? Only then use an in-place family.
4
Consider performance: Too many in-place families slow down the model. Prefer loadable families when possible.
5
Verify the category: Assign the correct Revit category so the family shows up in schedules and filters correctly.

Example 1: Exterior Wall

Brick Insulation Sheathing Drywall Wall Assembly (Compound Layers)

Example 2: Custom Door

Family Editor Door.rfa Load Revit Project Multiple instances

Example 3: Sculptural Canopy

Building Facade In-Place Canopy Unique shape Not reused

Common Mistakes

✕ Overusing In-Place Families
Creating in-place families for elements that could be loadable families. This bloats file size and kills performance.
✕ Trying to Save System Families as .rfa
System families cannot be exported as .rfa files. Use Transfer Project Standards to move them between projects.
✕ Wrong Category Assignment
Assigning a loadable family to the wrong category causes it to disappear from schedules, filters, and visibility settings.

Question 1 of 5

Which type of Revit family is a wall classified as?

Question 2 of 5

You want to create a custom light fixture that will be used in many projects. What family type should you use?

Question 3 of 5

What is the main disadvantage of overusing in-place families?

Question 4 of 5

How do you transfer a system family type (like a wall type) from one project to another?

Question 5 of 5

A designer needs to model a unique, freeform reception desk that references the lobby's curved wall. Which family type is most appropriate?