Nuget Package - Storage Issue

Hello @UiPath_Community

Actually while creating UiPath Automation script, there is .nuget folder whose size keeps on increasing on regular basis.
So I am thinking to use “Fallback Package Folder” or creating new location for nuget packages.

Can anyone please help me understand, which will be better. Also what are advantage and disadvantages of using (“Fallback Package Folder” or creating new location for nuget packages.).

Please help me as soon as possible.

Thanks in advance

sounds like an automation which stores data within the project / process / nuget folder.

In such case we would recommend to externalize this part and let point it to a location outside of the .nuget repositorium.

In a lot projects we have done it (we refer to the increasing data part) by folders, shared drives…
But we still kept the default location of the .nuget repository

Hello @Vaibhav_Shukla

  • If you’re working on multiple projects with the same set of packages and disk space is not a concern, using the default fallback package folder is convenient.
  • If you need better version control, isolation, and disk space management, consider creating a new location for NuGet packages for each project. This requires more initial setup but can be beneficial in the long run, especially for larger projects or when dealing with conflicting dependencies.

Hi @Vaibhav_Shukla

When working with UiPath projects and NuGet packages, you have the option to customize the package storage location by using either the “Fallback Package Folder” or creating a new location for NuGet packages. Here are the advantages and disadvantages of each approach:

Fallback Package Folder:


  1. Simple Configuration: It’s easy to set up. You can specify a fallback package folder path in the UiPath settings, and UiPath will automatically look for packages there if they’re not found in the default location.

  2. Compatibility: It’s a recommended approach by UiPath, and it ensures compatibility with the Robot and Orchestrator setups.

  3. No Manual Package Moves: UiPath handles the package storage, so you don’t need to manually move packages to another location.


  1. Limited Control: You have limited control over package storage. UiPath manages the packages in its default folder, which might lead to disk space issues if packages accumulate.

Creating a New Location for NuGet Packages:


  1. Greater Control: You have complete control over where you store your packages. This can be beneficial for managing disk space and organizing your packages as needed.

  2. Isolation: Storing packages in a separate location can isolate them from other UiPath processes or potential conflicts.

  3. Disk Space Management: You can proactively manage disk space by periodically cleaning up or archiving packages in your custom location.


  1. Manual Configuration: You’ll need to manually configure UiPath to use the custom package location by specifying it in the project settings. This might require additional setup steps.

  2. Potential Compatibility Issues: If not configured correctly, it may lead to compatibility issues with Robot and Orchestrator setups.

In summary, the choice between using the “Fallback Package Folder” and creating a new location for NuGet packages depends on your specific needs. If you prefer simplicity and are not concerned about disk space or package organization, the “Fallback Package Folder” is a good option. However, if you need more control over package storage and want to manage disk space efficiently, creating a new location for NuGet packages is the better choice. Just be sure to configure UiPath correctly to use the custom location to avoid compatibility issues.