Where are Revit plugins?

Revit plugins are primarily located in specific folders on your computer, with the most common path being C:\ProgramData\Autodesk\Revit\Addins\. However, the exact location can vary depending on how the plugin was installed and whether it's intended for all users or a specific user.

Understanding Revit Plugin Locations

Revit plugins consist of at least two main components: an .addin XML file and the actual plugin assembly (usually a .dll file). The .addin file acts as a manifest, telling Revit where to find the plugin's code and how to load it.

The main directories where Revit looks for these .addin files are:

Common Plugin Directory Paths

Location Type	Typical Path	Purpose
All Users	C:\ProgramData\Autodesk\Revit\Addins\[RevitYear]	For plugins available to all users on the machine for a specific Revit version. This is the most frequent location.
Per User	C:\Users\<YourUsername>\AppData\Roaming\Autodesk\Revit\Addins\[RevitYear]	For plugins installed only for a specific user.
Application-Specific	C:\Program Files\Autodesk\Revit [RevitYear]\AddIns	Less common, but some plugins may install directly into the Revit program files folder.
Custom Installer	Varies widely	Some plugin installers create their own directories, with the .addin file pointing to them from one of the above paths.

Important Note: While C:\ProgramData\Autodesk\Revit\Addins\ is a very common location for Revit plugin files, it's not a guaranteed path for all plugins. Developers and installers have some flexibility in where they place the actual plugin assemblies (DLLs), although the .addin file itself usually resides in one of the standard Revit Addins folders.

Deep Dive into Plugin Files

When you install a Revit plugin, an .addin file is typically placed in one of the Addins folders mentioned above. This .addin file is a simple XML document that contains critical information, such as:

• Assembly Path: The full path to the plugin's .dll file, which contains the plugin's code.
• AddInId: A unique identifier for the plugin.
• VendorId, VendorDescription: Information about the developer.
• Name, Description: The name and description that appear in Revit.

For example, an .addin file might look something like this:

<?xml version="1.0" encoding="utf-8"?>
<RevitAddIns>
  <AddIn Type="Application">
    <Name>MyCustomPlugin</Name>
    <Assembly>"C:\Program Files\MyCompany\MyCustomPlugin\MyCustomPlugin.dll"</Assembly>
    <AddInId>A1B2C3D4-E5F6-7890-ABCD-EF1234567890</AddInId>
    <VendorId>MYCP</VendorId>
    <VendorDescription>My Company, www.mycompany.com</VendorDescription>
  </AddIn>
</RevitAddIns>

In this example, the .addin file itself might be in C:\ProgramData\Autodesk\Revit\Addins\2024\MyCustomPlugin.addin, but it points to the actual MyCustomPlugin.dll located in C:\Program Files\MyCompany\MyCustomPlugin\.

How to Find a Specific Plugin

If you're looking for a particular plugin, here's a structured approach:

1. Identify your Revit Version: Plugins are typically version-specific (e.g., Revit 2024). This will guide you to the correct subfolder (e.g., ...Addins\2024).
2. Check the All Users Path:
   • Navigate to C:\ProgramData\Autodesk\Revit\Addins\
   • Look for a subfolder corresponding to your Revit year (e.g., 2024).
   • Inside, search for .addin files related to your plugin.
3. Check the Per User Path:
   • Open File Explorer and type %APPDATA%\Autodesk\Revit\Addins\ in the address bar, then press Enter.
   • Again, look for the relevant Revit year folder and search for .addin files.
4. Examine the .addin File: Once you find the .addin file for your plugin, open it with a text editor (like Notepad). Look for the <Assembly> tag; this will give you the exact path to the plugin's .dll file.
5. Check Program Files: If the .addin file isn't found in the common locations, or if the <Assembly> tag points elsewhere, you might need to check C:\Program Files\Autodesk\Revit [YourYear]\ or a custom installation folder that the plugin's developer might have created.

Understanding these locations is key for managing, troubleshooting, or developing your own Revit add-ins.