Free Revit families come from four places: Autodesk’s own installed and cloud content, manufacturer websites, aggregators such as BIMobject and ARCAT, and national libraries such as the NBS National BIM Library, which is built around UK conventions. The safe ones are the ones you have opened in the family editor, purged, and checked against your own content standard. Treat every download as a submittal, not a gift. Most of what you download will not survive that review, and the ones that fail cost an afternoon each if they reach a project first.
BIM here means building information modeling, and a family is the parametric component file, saved with an .rfa extension, that carries the geometry and data for a door, a light fixture, or a curtain wall panel.
Where do free Revit families actually come from?
Four sources, in rough order of how much cleanup they need.
- Autodesk content. The libraries installed with Revit and available through Autodesk’s own channels, built to the conventions in the Autodesk Revit Model Content Style Guide. Generic, clean, lightly parameterized, and a reasonable starting point when you plan to modify anyway.
- Manufacturer portals. The manufacturer’s own site, usually the best data and often the worst geometry. A door hardware maker will hand you an exact model number attached to a lever modeled down to the set screws.
- Aggregators. BIMobject, ARCAT, BIMsmith, and Sweets host manufacturer content with a search layer on top. ARCAT also carries specification sections and details, which makes it useful when you want the family and the spec language to agree.
- National and community libraries. The NBS National BIM Library serves the UK market and follows UK classification and product conventions, so U.S. teams should expect metric units and a different naming logic. Community sources such as the AUGI (Autodesk User Group International) forums are hit and miss.
Notice what is missing from the list: the family somebody emailed you from a previous firm. That one carries the previous firm’s subcategories, line patterns, and habits, and it is the most common source of the quiet mess in a project template.
What makes a free family unsafe to put in a model?
Not viruses. A family file is content, not code. The damage is slower and harder to undo.
- Imported CAD geometry. Computer-aided design (CAD) files dropped inside the family, sometimes a whole plan view of the manufacturer’s showroom. A DWG in there bloats the file, adds line styles you did not ask for, and cannot be cleaned once it is nested three levels deep. It is the single most common defect.
- Polygon counts nobody needs. A modeled thread pattern on a bolt at 1/4 inch scale. You will never see it. Revit will regenerate it every time you rotate a 3D view.
- The wrong category. A chair modeled as a generic model does not schedule as furniture, and nobody notices until the furniture schedule comes up short on a Friday.
- Materials and subcategories that pollute the project. Every material named “Material 3,” every subcategory that shows up in your Visibility/Graphics dialog forever, every unused line pattern.
- Missing data. No Assembly Code, no Keynote, no OmniClass number, none of the shared parameters your schedules depend on. The geometry is fine and the family is still useless.
- Version drift. Families upgrade forward and never backward. A family saved in a newer Revit release will not open in an older one, which matters when a consultant is a version behind.
How do you vet a downloaded family in 10 minutes?
Same discipline as a drawing check, and for the same reason. Bad content becomes rework two phases later, which is the argument in Is Your Drawing Set Review Process Slowing You Down?.
Run it in this order, in a sandbox project, never in the live model.
- Open the file in the family editor and check the file size. Note it.
- Confirm the category and that it schedules where you expect.
- Run Purge Unused, then save and check the size again. A large drop means the author never purged, which tells you what else to expect.
- Search for imported CAD. Select everything, filter for imports, and reject the family if you find any inside geometry you cannot replace.
- Open the materials and subcategories. Generic names and stray line patterns mean cleanup work.
- Flex the types. Change dimensions and swap materials, then check that nothing breaks or throws a constraint warning.
- Check the insertion point and host behavior. A wall-hosted family that should be face-hosted will haunt you at every renovation.
- Compare the parameters against your firm’s shared parameter file. Add what is missing before it goes in the library, not after.
If the family fails at step 4 or step 7, stop. Rebuilding is faster than repairing, and the rebuild leaves you with content you understand.
What level of development should the family carry?
Less than the manufacturer gave you, most of the time.
The BIMForum Level of Development Specification (2024 edition) defines LOD 100, 200, 300, 350, 400, and 500, where LOD 300 is accurate geometry with location and orientation, LOD 350 adds the interfaces with adjacent systems that coordination needs, and LOD 400 is fabrication-level detail. G202-2013, the American Institute of Architects (AIA) Project BIM Protocol, is where those levels get assigned to model elements by phase in a contract.
For a firm library, LOD 300 is the right default, with LOD 350 reserved for the elements you actually clash-check. Manufacturer content routinely arrives at something closer to LOD 400 because it was exported from the fabrication model, and that detail costs you performance for the entire life of the project while showing up on exactly zero sheets.
Post 128 in this pillar goes through the levels in detail and what each one should mean in your own standards.
Where do the families that pass actually go?
Into one folder tree, under one naming convention, with an approved date and a person’s name attached.
A family that passes vetting and then lives in someone’s downloads folder has not been added to anything. The firm library is the point. That means the file gets renamed to your standard, gets its shared parameters, gets an approval date, and gets logged so the next person knows it was checked rather than merely found.
The rules that govern that folder, the naming pattern, the parameter set, and the complexity limits belong in a written content standard, which is the subject of the next post in this pillar. The wider system it sits inside, including the sample library and the detail set, is laid out on the sub-pillar page, How to Build a Firm Material Library That People Actually Use.
Free content is genuinely useful. It is also a supply chain, and every other supply chain in your practice has an inspection step.
AECPulse Project Manager flags a project drifting over its documentation budget while there is still time to react, which is usually the same week someone quietly starts rebuilding downloaded content by hand.