Note: This article is written and published in Spanish and is a translated version of the original published here.
1. THE PROBLEM IT SOLVES
For years, BIM teams have managed their content libraries the same way: folders on local servers, family files circulating by email, and duplicate versions with names like "puerta_final_v3_DEFINITIVO.rfa". This model has a real cost that few organizations measure: time wasted searching for content, errors caused by using outdated families, and inconsistency across disciplines and projects.
Autodesk Content Catalog was created to close this gap. It is not simply a cloud repository: it is the infrastructure that turns dispersed BIM content into corporate digital assets — versioned, governed, and accessible from any tool in the Autodesk ecosystem.
|
Without Content Catalog |
With Content Catalog |
|
Families in network folders, with no version control |
Centralized assets with complete version history |
|
Each user maintains their own local copy |
A single source of truth accessible from the cloud |
|
Manual updates, inconsistent process |
Automatic update with multi-version Revit conversion |
|
No traceability of who uses which family |
Complete access and modification audit |
|
Unapproved content can enter projects |
Only validated content reaches modeling teams |
|
Onboarding new users takes days or weeks |
Immediate access with predefined permissions by role |
2. WHAT IS AUTODESK CONTENT CATALOG?
Content Catalog is Autodesk's management platform designed exclusively for BIM and AEC environments. It centralizes the storage, versioning, searching, and distribution of approved content — Revit families, AutoCAD blocks, materials, drafting views, Rhino files, and more — ensuring that every team member is always working with the correct version.
Note: Content Catalog was acquired by Autodesk in March 2023 — formerly known as UNIFI — and officially launched as a native product in August 2024. It responds to one of the most frequently requested items on the public Revit roadmap: an enterprise BIM content management system integrated into the workflow.
Available for organizations with an active subscription to AEC Collection, Autodesk Docs, or Forma Data Management. It is not included with standalone Revit licenses.
How is it different from a file server or SharePoint?
The key difference lies in native integration with authoring tools. While a file server forces the user to leave Revit, search manually, download, and load the family, Content Catalog does everything from the add-in installed in Revit: search, 3D preview, selection, and direct insertion into the active model, without interrupting the workflow.
Also, unlike generic solutions, Content Catalog understands the .RFA format natively: it extracts parameters, generates automatic 3D thumbnails, converts Revit versions, and maintains asset lineage over time.
3. TECHNICAL ARCHITECTURE
The service is structured in three functional layers that operate in an integrated way within the Autodesk Forma ecosystem:
|
Layer |
Component |
Responsibility |
|
Administration |
Hub Admin → Library → Content Catalog |
Service configuration, collection management, user groups, and access permissions |
|
Cloud Repository |
contentcatalog.autodesk.com |
Secure storage, indexing, versioning, advanced search, and asset preview |
|
Tool Integration |
Add-in for Revit, AutoCAD, Civil 3D, and Rhino |
Upload and retrieval of assets directly from the active modeling tool |
Supported content types
|
Asset Type |
Extension / Format |
Direct Insert |
Notes |
|
Revit Loadable Families |
.RFA |
Yes |
Automatic conversion between Revit versions |
|
Drafting Views |
Native Revit |
Yes |
Exported directly from Revit projects |
|
System Families |
Native Revit |
Yes |
Walls, ceilings, floors, roofs, etc. |
|
Fill Patterns |
Native Revit |
Yes |
Standardized corporate fill patterns |
|
Revit Materials |
Native Revit |
Yes (Beta) |
Feature still in a maturing stage |
|
AutoCAD Blocks |
.DWG / .DXF |
Yes |
Direct insert in AutoCAD and Civil 3D |
|
Rhino Files |
.3DS / .3DM / .OBJ |
Yes |
For workflows using Rhino geometry |
|
Documents and other formats |
PDFs, images, etc. |
No |
Available for download; not inserted into models |
4. OPERATIONAL FLOW
The work cycle in Content Catalog follows five sequential stages, from initial configuration to insertion of the asset into the BIM model. The diagram below shows the complete flow with the actors responsible for each stage.
Figure 1. Content Catalog operational flow: from configuration to insertion in the BIM model
Each stage has a defined actor and responsibility. The Administration stage is executed only once by the Hub Admin; the Search and Insert stages are performed by end users in every modeling session.
Collections as an organizational unit
Content Catalog organizes content in Collections, not nested folders. Each collection can represent a discipline, project type, geographic region, or approval status. The same asset can belong to several collections simultaneously without creating duplicates of the master file.
|
Criterion |
Examples of collections |
When to apply it |
|
By technical discipline |
Architecture, MEP, Structural, Civil |
Organizations with specialized teams by discipline |
|
By unit system |
Metric, Imperial |
Teams working in markets with different standards |
|
By approval status |
WIP – In review, Approved – Production |
Flows with a formal family validation process |
|
By project type |
Residential, Infrastructure, Industrial |
Portfolios with very different project types |
|
By client or standard |
Corporate Standard, Client A, Local Regulation |
Organizations managing third-party standards |
Avoid creating collections by element type ("Doors", "Windows", "Columns"). That level of granularity is better handled through tags and internal categories, not through separate collections.
5. ENABLING THE SERVICE
Prerequisites
|
Requirement |
Detail |
|
Required license |
AEC Collection, Autodesk Docs, Forma Data Management, or Forma Data Management Essentials |
|
Minimum role in Autodesk Forma |
Hub Administrator or Standards Administrator |
|
Supported Revit versions |
2021, 2022, 2023, 2024, and 2025 |
|
Regional availability |
Australia, the European Union, and the United States. Not yet available in Canada, Germany, India, Japan, or the United Kingdom |
|
Connectivity |
Requires active internet access for both the web interface and the Revit add-in |
Activation in the Autodesk Forma portal
To activate Content Catalog, log in to the Autodesk Forma portal with Hub Administrator credentials and navigate to Hub Admin → Library. The screen shows all services available on the platform; Content Catalog appears as one of the options in the Library section.
Figure 2. Hub Admin → Library: Content Catalog appears as an available service alongside Classifications, Model Analytics, and other modules
Once the service has been activated, storage region changes are not retroactive. Confirm the correct region before uploading content.
Installing the add-in in Revit
The Content Catalog add-in for Revit is downloaded from the Autodesk Portal. Go to manage.autodesk.com, then to Products and Services → Product Updates, and search for "catalog".
Figure 3. Autodesk Portal: search for the "Content Catalog Revit 2024-2027 Extension" add-in under Products and Services
Download and install the add-in on each machine running Revit. Once installed, Content Catalog appears on the Insert tab in Revit, within the Load from Library panel.
Figure 4. Revit ribbon: Content Catalog button on the Insert tab, Load from Library panel |
Figure 5. Launch options: as an integrated app or in a web browser |
In Revit 2025 and later, Content Catalog appears integrated directly in the ribbon without additional configuration steps.
6. MANAGING USERS AND PERMISSIONS
Content Catalog implements an access control model based on user groups, not individuals. This approach allows permissions to be managed centrally and at scale: when a new member joins the team, it is enough to add them to the corresponding group so they automatically inherit the configured access.
Permission levels by collection
|
Permission |
Enabled action |
Typical role |
|
Read collection |
View the collection and its contents from the web and the Revit add-in |
All users on the team |
|
Download / Insert content |
Insert assets into Revit models or download files locally |
Modelers, designers, consultants |
|
Upload content |
Publish new families, blocks, and other assets to the collection |
BIM coordinators, content managers |
|
Edit collection |
Modify asset metadata, tags, descriptions, and properties |
BIM Manager, senior coordinators |
Hub Administrators and Standards Administrators have inherent full control over Content Catalog. They are the only users capable of creating or deleting collections, managing groups globally, and configuring account preferences.
Suggested group structure
|
Group |
User profile |
Access to collections |
Permission level |
|
BIM Administrators |
BIM Manager, BIM IT leads |
All collections |
Full administrator |
|
BIM Coordinators |
Discipline coordinators |
Approved collections + WIP |
Editing and approval |
|
Modeling team |
Designers, drafters |
Production collections |
Read and insert |
|
External collaborators |
Consultants, subcontractors |
Selected collections |
Read only |
Procedure: create a user group
Preconditions: Hub Admin role active in the account, members previously added to the hub (Hub Admin → Members), and Content Catalog service activated. The process starts from the User Groups tab within Content Catalog.
Figure 6. Content Catalog: Collections, Channels, and User Groups tabs — starting point for access management
- Click + Create user group. The User Group Builder form opens.
Figure 7. Group creation form: name field, pinned collections selector, and area for adding users
- Enter a descriptive name based on the group’s role or discipline.
- Click + Add users. A dialog opens to enter corporate email addresses.
Figure 8. Add users modal: enter or paste email addresses to add members to the group
- Select the Pinned Collections: the collections that will appear preselected each time users in the group log in, streamlining access to commonly used content.
Figure 9. Pinned Collections selector: available collections appear in the dropdown to be assigned to the group
- Save the group with the Save button (upper-right corner of the form).
- Assign the group to the corresponding collections and configure permissions for each one.
Once the group is created, it appears in the User Groups list. Clicking it opens a side panel with Edit and Delete options.
Figure 10. Created group: side panel with Edit and Delete options and the group creation date
A group with no assigned collections has no visibility over any assets in the catalog. Assigning collections is a mandatory step after group creation.
7. UPLOADING AND PUBLISHING ASSETS
Method 1 – Direct export from Revit (recommended)
- Open in Revit the project or template that contains the families to be published.
- Launch the Content Catalog add-in from the Insert tab.
- Click the Upload icon in the add-in interface.
- Select the active model as the source.
- Filter by categories and mark the specific families to export.
- Choose the target collection and confirm the upload.
Method 2 – Drag-and-drop upload
From the web interface at contentcatalog.autodesk.com, it is possible to drag .RFA files directly into the target collection. Useful for individual uploads or when working outside an active Revit model.
Automatic Revit version upgrade
A distinctive capability of Content Catalog is automatic version conversion: when you publish a family in Revit 2025, the platform automatically generates compatible versions for Revit 2024, 2025, 2026, and 2027. This eliminates the need to maintain multiple copies of the same file for different versions of the software.
Figure 11. File history: a family uploaded in Revit 2025 automatically generates versions for Revit 2024, 2025, 2026, and 2027
This functionality solves one of the most recurring problems in teams with multiple Revit versions installed in parallel, especially during version migration periods.
8. METADATA, TAGS, AND SEARCHABILITY
The usefulness of a content library depends directly on how easy it is to find what is needed. Content Catalog addresses this challenge through a rich metadata system that is generated automatically during upload and can be supplemented manually.
From the Revit add-in, users can search for assets by name, category, collection, or tags. Results show automatically generated 3D thumbnails, allowing users to visually identify the correct item before inserting it.
Figure 12. Search in the Revit add-in: results with 3D thumbnails, asset name, and direct Insert button into the model
Complete asset card
When an asset is selected, its complete card is displayed with all available metadata: the collections it belongs to, assigned tags, interactive 3D preview, properties and types, version history, and compatibility with different Revit versions.
Figure 13. Complete asset card: collections, tags, 3D preview, and list of properties by type |
Figure 14. Revit add-in card: preview, collections, tag, and Insert button |
|
Metadata |
Description |
Origin |
|
3D preview |
Thumbnail automatically generated from the asset geometry |
Automatic |
|
Revit name and category |
Official asset designation and category in Revit |
Automatic |
|
Unit system |
Metric or Imperial; automatically corrected in recent versions |
Automatic |
|
Authoring Revit version |
Version of Revit in which the asset was originally created |
Automatic |
|
Generated compatible versions |
Revit versions available after automatic conversion |
Automatic |
|
Parameters and types |
Shared, instance, and type parameters available in the family |
Automatic |
|
Tags |
Keywords assigned to facilitate search and classification |
Manual |
|
Associated collections |
Repositories to which the asset belongs |
Manual |
|
Version history |
Chronological record of prior changes and publications |
Automatic |
|
Date of last publication |
Time-based traceability of the asset life cycle |
Automatic |
Tagging strategy
A well-designed tag system is the indispensable complement to a simple collection structure. It is recommended to define a corporate tag taxonomy before starting content uploads, considering at least these dimensions:
- Technical discipline: ARQ, MEP, EST, CIV
- Element type: furniture, sanitaryware, structure, lighting, etc.
- Reference standard or norm: ISO, NTE, ASHRAE, etc.
- Asset status: validated, in-review, obsolete
- Unit system: metric, imperial
Documenting the tag taxonomy in a BIM standard or corporate content guide ensures that multiple administrators classify content consistently.
9. CONTENT REQUEST FLOW
Content Catalog incorporates a formal mechanism that allows any team member to request the addition of new content without needing to upload it directly. The following diagram shows the complete process, including the responsibilities of each actor and the two possible paths: approval or rejection.
Figure 15. Content Request flow: from identifying the need to notifying the user
The Content Request flow is the recommended method for channeling all new content requests. It prevents users with limited permissions from uploading unvalidated families and ensures that the catalog grows in a controlled manner.
10. QUALITY CRITERIA FOR PUBLISHING FAMILIES
One of the main risks in implementing a corporate catalog is publishing unvalidated content. A family with errors in a centralized catalog is instantly propagated to all projects that use it. For this reason, it is recommended to establish a quality checklist prior to any publication in production collections.
|
Dimension |
Verification criterion |
|
Geometry |
The family has no open solids, invalid edges, or overlapping geometry |
|
Parameters |
Type and instance parameters are correctly defined and labeled |
|
Shared parameters |
Uses the corporate standard shared parameters when appropriate |
|
Naming convention |
The file name and family name follow the naming convention defined in the BEP |
|
Revit category |
Assigned to the correct category for proper behavior in views and legends |
|
Origin and orientation |
The insertion point is in the correct position according to the element type |
|
Performance |
The file size is appropriate; it does not contain unnecessary detailed 3D geometry |
|
Minimum version |
The minimum Revit version required for correct operation is declared |
|
Insertion test |
It has been inserted and tested in a Revit model before publication |
|
Approval |
Validated by the designated BIM Manager or content owner |
11. OPERATIONAL AND STRATEGIC BENEFITS
Operational impact
|
Benefit |
Impact description |
|
Single source of truth |
Eliminates the coexistence of outdated parallel family versions on local servers and individual computers |
|
Automatic multi-version conversion |
Eliminates the rework of maintaining multiple files for different Revit versions installed on the team’s machines |
|
Advanced and contextual search |
Reduces the time required to locate content through filtering by name, category, collection, and tags |
|
Direct insert without leaving Revit |
Eliminates the manual cycle of search → download → import, which can consume several minutes per element |
|
Asset traceability and auditing |
Allows tracking of which version of a family was used in each project and when it was updated |
|
Active catalog governance |
Only validated and approved content is accessible to project teams, reducing errors in later stages |
|
Cross-platform access |
Available from a web browser or the Revit add-in, with no dependency on a local network or VPN |
Strategic impact
- Cross-project standardization: all teams and projects consume the same validated content, ensuring consistency in BIM delivery.
- Reduction of technical non-conformities: incorrect or unapproved families are a frequent cause of errors detected in advanced reviews.
- Scalability of the BIM model: the corporate library can grow without local storage limitations.
- Accelerated onboarding of new resources: new staff gain immediate access to approved standard content.
- Foundation for BIM maturity under ISO 19650: centralized asset management is a key component of the CDE defined by the standard.
12. KNOWN SERVICE LIMITATIONS
|
Limitation |
Detail and recommendation |
|
Subscription dependency |
Requires AEC Collection, Autodesk Docs, or Forma Data Management. Standalone Revit licenses do not provide access to the service. |
|
Revit Materials in beta |
The integration with Revit Materials is in beta; it may show unexpected behaviors. |
|
Formats without direct insert |
PDF files and other formats not natively supported require manual download for use. |
|
Deleting collections |
It is not possible to delete a collection that contains assets. It must be fully emptied before proceeding. |
|
Mandatory connectivity |
The service does not have an offline mode. An active connection is required for any operation. |
|
Autodesk Forma membership |
Only people who are already members of the Autodesk Forma account can be added to user groups. |
14. RECOMMENDATIONS FOR SUCCESSFUL ADOPTION
- Designate a BIM Content Owner: a formal role responsible for catalog quality, consistency, and updates.
- Implement a family quality checklist before publishing to production collections.
- Define the tag taxonomy before uploading content to avoid having to go back and mass-tag content later.
- Perform quarterly catalog reviews: verify active members, clean up obsolete assets, and update families.
- Monitor the Autodesk roadmap: Content Catalog is an actively evolving product with new functionality added regularly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.