Add a README to Your NuGet Package

Christopher Gill

In March, we published a blog on the State of the NuGet Ecosystem, where we discussed insights gained from the hundreds of customers we’ve heard from over the last six months. One of the top problems customers identified in our surveys is that “most packages have insufficient docs” easily accessible from In fact, 45% of survey respondents reported “critical packages I need do exist but they are not well documented” as a reason for dissatisfaction with the NuGet ecosystem.

We’re excited to announce that you can finally pack a file in your NuGet package and have it fully rendered on!

Image of README from MySqlConnecter package on

– Image from MySqlConnector package

This new capability is still in preview with support starting in .NET SDK 5.0.300 preview, NuGet 5.10 preview 2, and Visual Studio 16.10 preview 2. The easiest way to try this feature today is to install the latest .NET 6 preview or the latest Visual Studio preview.

Previously, we offered limited support for markdown documentation on However, this experience required authors to paste a link to their README or paste their README contents on for each new package version. We heard from authors that this additional step took too much time and felt removed from the rest of the package creation and publishing process.

In the new experience, you add the file the same way you would for any other embedded package file like an icon or license. This means:

  1. You don’t have to go to just to add documentation to your package, you can do it with whichever tools you prefer to use to author NuGet packages.
  2. Once you set up your project file with a path to your, the latest version of your README will be packed every time. Just set it and forget it!
  3. The README file is immutable and version-specific, so consumers can view the relevant README for older versions of the package too!

Add a README to your package

If you already have a file, including it in your package is as easy as adding a couple lines to your project file for SDK-style projects or nuspec for non-SDK-style projects. If you are new to creating NuGet packages, we recommend going with an SDK-style project.

For the following examples, I am keeping my file in a “docs” folder so its relative path to my project file is docs\ You can also use a README file at the repository root or any other folder as long as you use adjust the relative path. Additionally, you can name the target file anything you would like, such as instead of

You can reference the README in the project file as follows:

<Project Sdk="Microsoft.NET.Sdk">

        <None Include="docs\" Pack="true" PackagePath="\"/>

Add a README in your nuspec

You can reference the same README in the nuspec as follows:

    <file src="..\" target="docs\" />

Writing a README for

Consider including the following items in your README:

  • An introduction to what your package is and does – what problems does it solve?
  • How to get started with your package – are there any specific requirements?
  • Links to more comprehensive documentation if not included in the README itself.
  • At least a few code snippets/samples or example images.
  • Where and how to leave feedback such as link to the project issues, Twitter, bug tracker, or other platform.
  • How to contribute, if applicable.

Keep in mind, high quality READMEs can come in a wide variety of formats, shapes, and sizes! If you already have a package available on, chances are that you already have a file in your repository that would be a great addition to your details page.

Preview your README

To preview your README file before it’s live on, upload your package using the Upload Package web portal on and scroll down to the “Readme File” section of the metadata preview. It should look something like this:

Image of README file preview section of the package upload metadata preview page

Consider taking time to review and preview your readme file for image compliance and supported formatting to make sure it gives a great first impression to potential users! To correct mistakes on your package README once it’s published to, you will need to push an updated package version with the fix. Making sure everything looks good in advance may save you headache down the road.

Markdown and image support READMEs support CommonMark compliant Markdown through the Markdig parsing engine. See our README documentation for a full list of supported Markdown features.

Due to security and privacy concerns, will only support badges and images from a trusted allow-list of sources. Unfortunately, links to local images won’t be supported at this time either. Consider hosting local images in one our trusted sources to produce a link to include in your README.


We want to thank every package author that volunteered to try out the new README experience in advance to give us feedback and serve as models for the broader NuGet ecosystem.

Check out the following packages and how they used READMEs to enhance the richness of their package details page and improve the onboarding experience for new and prospective users:

Where can I see package READMEs?

When a package with an embedded README is uploaded to, the README can be found on its package details page. A link to the README will also be available in the Visual Studio package details pane.

Image of the Ben.Demystifier package details pane in Visual Studio that includes a link to their README on

– Image from Ben.Demystifier package

We want to hear your feedback!

Your feedback is very important to us. If you experience any problem trying the new README feature, check out our documentation on submitting bugs and suggestions to find the right place to look for solutions or file new issues.

To see what is coming to NuGet next, view our public proposals or create your own proposal. Be sure to leave your feedback on existing issues & pull requests!

If you add a README to your package, tweet about it and mention @nuget to get a like or retweet from us to signal boost your package!


Discussion is closed. Login to edit/delete existing comments.

  • Mark Adamson 0

    This is good news, it should help a lot. Something is a bit jarring about the property name PackageReadmeFile, I think it is the apparently redundant File word and the fact that it is Readme, not ReadMe.

    • Christopher GillMicrosoft employee 1

      Hi Mark!

      I understand your concerns. We chose the name “PackageReadmeFile” to be consistent with existing similar elements like “PackageLicenseFile”. The “File” at the end is to make the distinction between URL and embedded file support (we used to support license URLs which are now deprecated).

      Regarding the capitalization, in this context I’ve typically seen “README” considered a single word/noun. Most package managers and repositories including GitHub use either “README” or “Readme” as the default capitalization scheme.

    • Christopher GillMicrosoft employee 0

      Thanks for catching that! I updated the post to have the proper link.

  • Sahil . 0

    Hi Christopher

    I’m unable to see the README link in the visual studio package details pane on mac. Does it mean that I’ve not configured the readme properly, I doubt whether the readme section will be visible on Nuget or not, as in the details pane it’s not visible to me.

    Visual Studio for Mac’s version: 8.9.6 (build 6)
    Kindly help me with this issue.

    • Christopher GillMicrosoft employee 0

      Hi Sahil,

      The README link is only currently available in Visual Studio for Windows. However, this shouldn’t prevent you from adding your README to, in which case it’ll still be easily accessible to consumers when they click the link in VS for Mac.

Feedback usabilla icon