How Do I Add A NuGet Source In Visual Studio?

What's the issue?

You're seeing a "Package source not found" error, or can't reach a private feed. That usually means your NuGet source isn't configured right in Visual Studio 2026.

Why isn't my NuGet feed showing up in Visual Studio?

NuGet sources are basically endpoints where Visual Studio grabs packages from. Since Visual Studio 2017, NuGet comes built into .NET workloads Microsoft Support. If your feed's not loading, the source might be missing, misconfigured, or blocked by network/auth issues. Private feeds? They usually need a personal access token (PAT) or username/password.

How do I add a NuGet source in Visual Studio?

Here's the quickest way to set one up:

1. Open Visual Studio 2026.

2. Head to Tools > NuGet Package Manager > Package Manager Settings (or hit Ctrl + , and type "NuGet Package Manager settings").

3. In the left sidebar, click Package Sources.

4. Click Add to create a new source.

5. Fill in these details:

   Field	Value
   Name	MyPrivateFeed (or whatever you like)
   Source	https://your-feed-url/v3/index.json

   For nuget.org, just use: https://api.nuget.org/v3/index.json NuGet.org.

6. If it's a private feed, click Update to add your credentials:

   • Using Azure Artifacts? Drop in your Azure DevOps PAT.
   • Got GitHub Packages? Use a GitHub token with read:packages scope.

7. Hit OK to save everything.

8. Restart Visual Studio to make sure the changes stick.

I added the source, but it still doesn't work. What now?

Don't panic yet. Try these troubleshooting steps:

• Check your network: Can you even reach the feed URL? Try running curl -v https://your-feed-url/v3/index.json in a terminal. If it's blocked, tweak your firewall or VPN settings.

• Double-check credentials: Tokens expire after about 90 days Microsoft Learn. Regenerate them if needed.

• Clear the NuGet cache: Sometimes old data causes issues. Delete the cache folder:

  • Windows: %userprofile%\.nuget\packages
  • Mac/Linux: ~/.nuget/packages
  Then restart Visual Studio.

How can I make sure my NuGet sources stay consistent across my team?

Use a NuGet.Config file in your solution root. It keeps everyone on the same page. Here's a quick example:

<configuration>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="MyPrivateFeed" value="https://your-feed-url/v3/index.json" />
  </packageSources>
  <packageSourceCredentials>
    <MyPrivateFeed>
      <add key="Username" value="any" />
      <add key="ClearTextPassword" value="your-pat-here" />
    </MyPrivateFeed>
  </packageSourceCredentials>
</configuration>

Commit this file to source control so your whole team uses the same setup NuGet Docs.

Is there a safer way to handle sensitive feed URLs or tokens?

Absolutely. Store them in environment variables instead of hardcoding them. For example, use NUGET_FEED_URL for the feed URL and reference it in your config or CI/CD pipeline. Keeps secrets out of your codebase.

My feed is hosted privately. How do I monitor if it goes down?

Set up alerts for downtime. Tools like Azure Monitor or Prometheus can watch your feed and notify you if it stops responding. Handy for catching issues before your team does.

Can I automate adding NuGet sources in Visual Studio?

Visual Studio doesn't have a built-in command for this, but you can script it. Use PowerShell or a batch file to edit the NuGet.Config file directly, then restart Visual Studio. Works great for CI/CD pipelines too.

What if I'm using a proxy to access my NuGet feed?

You'll need to configure Visual Studio to use it. Go to Tools > NuGet Package Manager > Package Manager Settings, then find the proxy settings. Enter your proxy server details there. Without this, Visual Studio won't be able to reach external feeds through your proxy.

Do I need admin rights to add a NuGet source?

Not usually. Any user can add a NuGet source in their own Visual Studio settings. But if you're trying to add a source for the whole team, you might need admin rights to place the NuGet.Config file in a shared location.

Why does Visual Studio keep forgetting my NuGet sources?

That's odd. Usually, it's because the NuGet.Config file isn't in the right place or got overwritten. Make sure it's in your solution root or user profile. If you're using a shared config, check that it hasn't been deleted or modified.

Can I use different NuGet sources for different projects?

Sure thing. Visual Studio checks for a NuGet.Config file in the solution root first. If it doesn't find one, it falls back to your user-level config. So you can have project-specific sources by placing a config file in each project folder.

What's the difference between a NuGet source and a package feed?

They're basically the same thing. A NuGet source is just the URL where Visual Studio looks for packages. A package feed is the collection of packages hosted at that URL. Think of the source as the address and the feed as the building at that address.

I'm still stuck. Where can I get more help?

Check the official docs first Microsoft Learn. If that doesn't help, try the NuGet forums or Stack Overflow. Someone's probably run into the same issue before.