Revit Links Workflow: Trainer Tested Fix for Cloud Path Breaks
The recommended workflow is straightforward: link discipline models with the correct reference type, control visibility through the Manage Links dialog and View Templates, migrate those links to the cloud with Reload From when your team moves to Revit Cloud Worksharing, and swap heavy context into Coordination Models to protect performance. Autodesk Revit supports this entire chain natively, and getting the sequence right is what separates a coordinated project from a tangle of broken paths and invisible worksets.
TL;DR:
Use Overlay by default so nested links do not travel into downstream projects; choose Attachment only when the nested model must remain with its host.
A linked model stays invisible when its required workset is closed, regardless of display mode; use View Templates to keep visibility settings consistent across views.
For cloud migration, save each linked file as a cloud model, then use Reload From in the host; uploading alone does not update paths.
Use Navisworks coordination models for large visual context, but keep live Revit links for editable daily coordination; only the former cannot be edited.
Table of Contents
Why link models and which formats to use
Linking keeps architectural, structural, and MEP work in separate files that reference each other instead of living in one bloated model. On a large project, that separation makes files faster to open, easier to assign to teams, and simpler to troubleshoot when something goes wrong.
Revit supports several link formats depending on what you are coordinating against. According to Autodesk’s documentation, linking supports Revit (.rvt), IFC, CAD (.dwg/.dxf), point clouds, and Navisworks coordination models (NWD/NWC).
Revit links are best for live, editable coordination between disciplines working in Revit.
IFC and CAD links suit consultants working in other software or legacy drawings.
Point clouds support renovation and as-built coordination.
Coordination models carry heavy context without the overhead of a full Revit file.
Linking also updates automatically when the source file changes, which is why it is preferred over importing whenever you expect a file to keep evolving. Importing CAD geometry instead of linking it can bloat categories and slow performance over time, according to Autodesk’s guidance on importing versus linking CAD files. For very large external context, a coordination model is often the lighter choice, a point worth revisiting once your project grows past a handful of linked files.
Manage Links dialog: the practical controls you must use
The Manage Links dialog is where you operate every link in your project, and learning its layout early saves hours of guesswork later. It organizes links into tabs, including Revit, IFC, CAD, Coordination Model, and Point Clouds, with a status column showing whether each one is Loaded, Not Loaded, Not Found, or In Closed Workset, according to Autodesk’s reference on the Manage Links dialog.
Each tab lists only links of that file type, which keeps large projects with mixed formats readable.
The status column flags problems instantly, so a Not Found link is caught before it derails a coordination meeting.
Rows can be sorted and multiple links selected at once for batch actions.
The sort order you set persists between sessions, so your view of the dialog stays consistent.
Reload and Reload From are the two commands you will use most. Reload refreshes a link from its current path, while Reload From lets you repoint a link to a new file location, which is exactly what you need when a file moves or when you remap a local link to a cloud-hosted model, per Autodesk’s tools to manage links.
Unload options matter in workshared projects too. Unload for me hides a link only in your session, while Unload for all users removes it for the whole team, and Clear my override resets a personal setting back to the shared default, according to Autodesk’s documentation on managing links.
Pro Tip: Sort the Manage Links dialog by status before every coordination meeting so Not Found links surface first, not halfway through the review.
Reference Type: Attachment vs Overlay and nested links
When a linked model contains its own links, those become nested links, and how they behave depends on the Reference Type you choose. Attachment means nested links load with the host, so if you link a structural model that is attached to a site model, the site model comes along for the ride wherever the structural model goes. Overlay does the opposite: nested links do not load when the host is linked into another project, according to an explanation of attach versus overlay behavior.
This distinction has real downstream effects. According to Autodesk’s guidance on nesting linked models, nested links show up under their parent in the Revit Links branch of the Project Browser, but they do not appear as separate rows in the Manage Links dialog. That matters for selection and interference checking, since a nested link you cannot see directly in Manage Links can still clutter a view or a clash report if it loaded along with its host.
Use Overlay when a reference should not travel into other projects that later link your model.
Use Attachment only when the nested model genuinely needs to move as a package with the host.
Check the Project Browser, not just Manage Links, to confirm what nested geometry is actually loaded.
A simple habit prevents most surprises here: default to Overlay unless you have a specific reason to attach, since attachment cascades in ways that are easy to forget once a project has several layers of links.
Controlling visibility and graphics for linked models
Visibility problems account for a large share of “where did that link go” questions, and the fix usually comes down to three settings working together. On the Basics tab of RVT Link Display Settings, you choose the linked view, and you control display with one of three modes: By host view, By linked view, or Custom, according to Autodesk’s documentation on visibility of linked models.
By host view matches the linked model’s display to whatever view settings are active in the host, useful when you want consistency with your own project standards.
By linked view preserves the exact view settings the other discipline set up in their own model, which is handy when a structural team has already configured their own useful view.
Custom lets you show only specific worksets or categories from the link, which is the right choice when you need, say, only the structural grid and columns visible in an architectural plan.
A linked workset also has to be open in the host model before any of its elements can display, regardless of which display mode you pick, per Autodesk’s guidance on controlling visibility of linked worksets. That single setting trips up more teams than any other part of the linking process, since a closed workset simply will not appear no matter what display override you apply.
View Templates are the mechanism that makes all of this repeatable. Rather than configuring link visibility one view at a time, apply a view template that bakes in your linked-model display settings, workset visibility, and discipline-specific graphics, including halftone and transparency to visually separate one discipline from another. You can also apply view filters to linked and nested models, using either the host’s filters or the filter already set in the linked view, according to Autodesk’s reference on view filters for linked models.
Pro Tip: Build your linked-model view template before you insert your first link, not after visibility problems start piling up.
Cloud workflows: migrating links and publishing with links
Moving a project to Revit Cloud Worksharing does not automatically bring your linked models along. Each linked model has to be saved as a cloud model in its own right, and then, in the host project, you open Manage Links and use Reload From to point the link to that cloud location, an explicit remapping step that Autodesk’s documentation describes clearly for migrating workshared linked models to the cloud. Simply uploading files to cloud storage does not update existing file-path links on its own, according to Autodesk’s support article on changing linked model visibility.
Open each linked model individually and save it as a cloud model before touching the host.
In the host model, use Reload From, not Reload, since the path itself is changing, not just the content.
Confirm the remap succeeded by checking the status column in Manage Links.
Keep cloud and local links from mixing in the same project once migration starts.
Publishing adds another layer worth planning for. By default, only the 3D default view and 2D sheets get published to Autodesk Docs, so if reviewers need floor plans, sections, or specific coordination views, you have to customize the publish settings to include them, per Autodesk’s documentation on publishing cloud models.
Cloud models also need to come from the same Revit release to link successfully, and file renames can cause path confusion that a straightforward Reload will not fix, only Reload From will. A sensible cadence is to publish whenever external reviewers need a coordinated snapshot, while your internal team keeps reloading links locally for day-to-day, live coordination between syncs.
Coordination models and performance strategies
When a linked Revit file exists mainly to give you visual context rather than editable geometry, a coordination model is often the better tool. These are lightweight, non-editable references brought in from Navisworks NWD or NWC files, and they support transparency, pinning, and phasing without the overhead of a full Revit link, according to Autodesk’s documentation on coordination models.
Link coordination models from a local Navisworks file or directly from Autodesk Docs.
Use transparency and phasing controls to keep the context visible without it competing visually with your working model.
Reload coordination models the same way you reload any other link, which keeps your context current without re-inserting it.
Convert a heavy Revit link to a coordination model when its only job is visual reference during periodic review rounds.
As our guide to coordination models covers, coordination models are generally preferred for large multidisciplinary context specifically because they offer performance advantages over carrying a full native Revit link.
Unload for me is the other tool worth reaching for regularly. It hides a heavy link in your own session without affecting anyone else’s view of the project, which is useful when you are working in a detail-heavy view and do not need the structural or MEP model loaded at all, according to Autodesk’s tools to manage links. Reserve the team-wide Unload for all users option for links nobody currently needs, since it affects every user’s session until someone reloads it.
Step-by-step recommended Revit links workflow (practical checklist)
Here is the sequence we recommend following on a new multidisciplinary project, from first link to ongoing maintenance.
Establish shared coordinates and naming conventions first. Clean out unwanted categories in files before they get linked, since import clutter follows the link, according to Autodesk’s guidance on importing or linking CAD files.
Insert each link with the correct positioning. Choose Auto - Origin to Origin or Auto - By Shared Coordinates, and confirm the result in a Coordination discipline view, per Autodesk’s instructions for linking one model to another.
Set Reference Type deliberately. Default to Overlay unless a nested model must travel with its host, and confirm what actually loaded by checking the Project Browser.
Configure RVT Link Display Settings for the view and open the worksets you need. Then apply a view template so the settings hold across every similar view, per Autodesk’s guidance on linked workset visibility.
Migrate to the cloud when the project calls for it. Save linked models as cloud models, remap with Reload From, and publish only the views and sheets reviewers actually need, per Autodesk’s cloud migration documentation.
Maintain the setup on a schedule. Check Manage Links regularly for Not Found entries and use Unload for me whenever you are working a heavy, detail-focused view.
Pro Tip: Treat step one, naming and folder structure, as non-negotiable: most “Not Found” link errors trace back to a file that moved outside the convention everyone agreed on.
S15Studio perspective: trainer-tested tips for teams
A few habits from project work consistently cut down on link headaches. Naming links with a project code and a discipline prefix (ARC, STR, MEP) makes Not Found errors far easier to trace when a file moves. For a minimum viable view template, start with three settings: linked model halftone, which worksets are open by default, and the discipline’s own view display, before adding anything more elaborate.
Name every linked file with a project code and discipline prefix from day one.
Build your first view template around halftone, workset rules, and discipline display settings only.
Use coordination models for weekly clash review cycles, and keep live Revit links for daily authoring work, a pattern our clash detection workflow guide walks through in more detail.
Reinforce worksharing basics with our guide to Revit worksharing before layering cloud migration on top.
These habits come from running the same workflow repeatedly in project-based training, not from a single edge case.
Author perspective: how teams change linking habits successfully
Most link problems I see trace back to three habits: inconsistent file naming, forgetting to use Reload From after a file moves, and defaulting to Attachment for nested links out of convenience rather than intent. None of these are hard to fix, but they require a team agreement, not just individual discipline.
The two changes with the biggest payoff are simple. Apply a view template at the start of a project, before visibility problems accumulate, and make “Reload From cloud” a required step in every model handover, not an optional cleanup task.
— Steve
How S15Studio training helps with Revit links and collaboration
Reading documentation gets you the rules, but building the habit of linking, reloading, and visibility management correctly comes from working through real projects, which is how we built our training. Our Worksharing Course covers collaboration workflows through project-based exercises rather than isolated feature demos.
If you want broader Revit skills alongside that collaboration focus, our Revit Course Only covers linking and worksharing within a full beginner-to-advanced curriculum, with lifetime access to materials and direct trainer support along the way. Start with whichever matches where your skills stand today, and build from there with real project files rather than isolated tutorials.
FAQ
How do I manage links in Revit?
Open the Manage Links dialog from the Insert or Manage tab to see every linked file, its status, and format-specific tabs for Revit, IFC, CAD, and coordination models. From there you can reload, reload from a new path, unload for yourself or the whole team, and sort or batch-select links, according to Autodesk’s Manage Links documentation.
What is the difference between a coordination model and a Revit link?
A Revit link is a live, editable reference to another Revit file, IFC file, or CAD drawing that updates when its source changes. A coordination model is a lightweight, non-editable reference built from a Navisworks NWD or NWC file, used mainly for visual context and performance on large projects, per Autodesk’s documentation on coordination models.
Should Revit links be overlay or attachment?
Overlay is the safer default, since it prevents nested links from cascading into other projects that later link your model. Attachment should be reserved for cases where a nested model genuinely needs to travel as a package with its host, according to guidance on attach versus overlay behavior.
How do I link two Revit files together?
Use Insert, then Link Revit, select the file, and choose a positioning method such as Auto - Origin to Origin or Auto - By Shared Coordinates. Confirm the result in a Coordination discipline view before adjusting visibility settings, per Autodesk’s instructions for linking one model to another.
Sources
The guidance above draws on Autodesk’s official documentation for linking, Manage Links, visibility controls, and Revit Cloud Worksharing, alongside our own coordination model guide for architects. Check these directly for the most current detail on any step covered here.
Recommended
Comments