Revit Content Catalog Empty or Not Showing Libraries? Complete Fix Guide (2026)

If your Revit Content Catalog shows empty libraries, missing thumbnails, or returns “No results found”, you’re dealing with a known set of issues tied to authentication, cache, and regional service instability.

Since the transition from UNIFI to the integrated Autodesk system, these problems show up frequently in production environments. The content is usually still there—what’s failing is how the Revit extension syncs and displays it.

This guide consolidates field-proven fixes, including the original workflows and additional diagnostics used in real BIM environments.


Quick Fix (Start Here)

If you need a fast resolution, run this sequence first:

  • Log out of the Content Catalog (do not just close the window)
  • Close Revit and all browsers (Chrome, Edge)
  • Clear browser cache and cookies
  • Restart Revit and log back in

This resolves most cases where the Content Catalog appears empty or unresponsive.

If the issue persists, proceed directly to the Deep Reset + Cache Removal section below.


The Core Problem: Sync and Cache Desynchronization

The primary issue stems from how the Revit-embedded Content Catalog handles authentication tokens and cached sessions.

Unlike a standard browser:

  • The embedded panel runs on a WebView2 (Chromium-based) container
  • It can retain stale session data
  • Failed updates can leave the interface in a locked or blank state
  • Authentication tokens may expire without triggering a refresh

This explains why:

  • Your library appears correctly in the web portal
  • But shows as empty inside Revit

This is not a data loss issue. It’s a session and cache desynchronization problem inside the embedded Chromium layer.


Proven Solutions from the Field

1. The “Deep Reset” Protocol

Simple cache clearing often fails because the active session remains stuck inside both the browser and Revit’s embedded WebView.

Follow this exact sequence:

  1. Log Out
    Use the explicit “Log Out” option inside the Content Catalog interface
  2. Terminate Revit and Browsers
    Close Revit and all instances of Chrome or Edge
  3. Clear Web Cache
    Clear cache and cookies for your default browser
  4. Restart and Log In
    Re-open Revit and log back into the Catalog

This forces a fresh authentication token and clears broken session data.


2. Advanced Fix: Clearing the Revit WebView Cache (Critical)

In real-world cases, the standard reset is sometimes not enough because Revit maintains its own WebView2 cache, independent of the browser.

If the issue persists:

  • Navigate to:
    %LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit 202x\CefCache
  • Delete the entire CefCache folder
  • Restart Revit and log back in

This is effectively a full reset of the embedded Chromium session.

Use this when:

  • The catalog stays blank after multiple resets
  • Login loops occur
  • UI fails to load consistently

3. Regional Server Workarounds (EU Focus)

Autodesk has acknowledged stability issues affecting users on EU servers.

If the extension fails inside Revit:

  • Access the catalog directly via:
    contentcatalog.autodesk.eu
  • Use a supported browser (Chrome or Edge)

Practical workaround:

  • Avoid the Revit-embedded panel when unstable
  • Manage and download families through the web portal

This is currently the most reliable method for EU-based teams.


4. Version Compatibility and Updates

Make sure you are running the latest version of the Content Catalog extension.

  • Current stable version: 1.1.4.0 (March 2025)
    Fixes several “zero-result” search issues

Known issue:

  • Content uploaded in older Revit versions (2021–2023) may not trigger insertion correctly in newer versions if the extension is outdated

Action:

  • Update the extension through your Autodesk Account
  • Restart Revit after installation

5. Browser Behavior and Compatibility

The Content Catalog is built on a Chromium-based stack.

This explains the behavior observed in the field:

  • Chrome and Edge (Chromium) behave almost identically
  • Both rely on the same rendering and script engine
  • Issues affecting one often affect the other

In contrast:

  • Firefox (non-Chromium) uses a different engine
  • It can bypass certain script execution or caching issues

This is why Firefox sometimes works when Chrome/Edge fail.

Use case:

  • Search results not loading
  • UI elements not rendering
  • Persistent script failures

This remains a workaround, not a standard deployment setup.


Additional Diagnostics (When the Issue Persists)

Check Autodesk Hub / Account Mapping

This is often misdiagnosed as a missing library issue.

You need to verify:

  • The correct Autodesk Hub is selected inside the Content Catalog
  • The user is mapped to the correct Autodesk Account / project context

A user can:

  • Be logged in
  • Have access to the project

But still see empty libraries if the wrong Hub context is active.


Check Account Permissions

  • Confirm your ACC access and role assignments
  • Verify Library Manager permissions

Missing permissions can result in:

  • Empty libraries
  • Invisible collections

Verify Active Filters

A common oversight:

  • The catalog is filtered to an empty collection

Check:

  • The “Collections” filter is set correctly
  • No restrictive filters are applied

This often explains “No results found” for basic searches.


Check Network and Firewall Constraints

In corporate environments:

  • Firewalls or proxies may block catalog endpoints
  • Authentication calls may fail silently

Symptoms:

  • Blank screen
  • Infinite loading
  • Missing thumbnails

Action:

  • Test on a different network
  • Whitelist Autodesk services if needed

Thumbnail and Processing Delays

If thumbnails are missing:

  • This is often a server-side processing delay after upload

Standard behavior:

  • Thumbnails should appear within 24 hours

If not:

  • Use “Re-process” in Catalog management settings
  • Check the File History tab to confirm upload validation

FAQ: Common Content Catalog Issues

Why does my Content Catalog show “No results found” even for simple searches?

This usually comes from a stalled session or corrupted cache.

Fix:

  • Run the Deep Reset protocol
  • Verify that Collections filter is not empty

Why is my Revit Content Catalog empty but works in the browser?

This indicates a desynchronization between Revit and Autodesk servers, specifically in the WebView2 embedded session.

Typical causes:

  • Expired authentication token
  • Corrupted embedded cache

Fix:

  • Log out
  • Clear cache
  • If needed, delete CefCache

Is there a way to see the latest fixes and known issues?

Yes.

  • In the bottom-left corner of the Content Catalog interface
  • Click the version number

This opens the Release Notes, updated on a bi-weekly cycle.


Why can’t I see the Content Catalog in Revit 2023 or older?

The Content Catalog is primarily integrated with:

  • Revit 2024
  • Revit 2025

For older versions:

  • You must install the Content Catalog Revit Extension
  • Available via manage.autodesk.com

My thumbnails are broken or missing. How do I fix them?

Likely a processing delay after upload.

Steps:

  • Wait up to 24 hours
  • If still missing:
    • Use Re-process
    • Check File History for validation errors

Can I still use my old UNIFI libraries?

Yes.

Autodesk migrated UNIFI libraries into the Content Catalog.

If content is missing:

  • Confirm your Autodesk Hub is correctly selected
  • Verify your Library Manager permissions

Why does search return zero results randomly?

This is tied to:

  • Outdated extension versions
  • Session cache issues
  • Chromium/WebView inconsistencies

Fix:

  • Update to version 1.1.4.0 or newer
  • Run the Deep Reset protocol
  • If needed, clear CefCache

What Actually Works in Production

In active BIM environments, the most reliable setup today is:

  • Use the web portal for browsing and management
  • Keep the Revit extension updated
  • Reset sessions when issues appear
  • Clear WebView cache when standard fixes fail
  • Avoid relying entirely on the embedded panel during unstable periods

These issues are not permanent failures. They are session handling and embedded browser limitations.

Once you treat it as a cache and authentication lifecycle problem, recovery becomes predictable.

Similar Posts