Installing iText 7 for .NET
How to install iText 7 .NET version
Thank you for your interest in our open-source PDF library, iText 7, we hope you will enjoy using our product and share your experiences with us and the iText community. We will walk you through the installation process, from downloading iText 7 to adding the dependencies to your .NET build tool.
If you require any extra help please have a look at our FAQs or the community discussion at StackOverflow. If you are interested in getting support from our in-house developers and/or a license key for commercial iText products, you will need to acquire a commercial license.
Before you install (commercial license users only)
- Make sure you have purchased a commercial license for iText 7. All downloads we offer closed-source come with our commercial license model.
- If you do not use the "Automated dependency management" method to install iText 7, you will need to download the proper license key library. You can find the installation guide here.
- Important remark: In the installation guide, we use NuGet as a build tool for .NET. - iText 7
Automated dependency management
iText 7 is available on NuGet. To install the core iText 7 modules, you can install them with a single NuGetPackage by typing the following command in the NuGet Package Manager:
If you have a trial or a commercial license you will also need the iText 7 license key library. You can install this typing the following command in the NuGet Package Manager:
NOTE: This is a required dependency for the closed-source add-ons, so it will automatically be installed when you install an add-on that needs the license key library.
Using the iText Artifactory Server
iText 7 NuGet packages are also available on the iText Artifactory server. You can add it as a custom NuGet repository to Visual Studio. In the NuGet Package Manager, go to the settings and add the following URL as a package source: https://repo.itextsupport.com/api/nuget/nuget. You can also browse the iText Artifactory server and download NuGet packages manually.
You can find the .NET jump-start tutorial and helpful code examples in the Resources section of our website.
iText 7 Core .NET on GitHub
The source code is available on GitHub.
You can download the modules (.nupkg) of iText 7 Core in a single ZIP file for .NET: iText 7.
Developers can clone the following git projects to access the source code for .NET: iText 7.
Installing SNAPSHOT builds
During development we release SNAPSHOT builds which you can install if you require a fix for a specific issue, before it is made available on an official RELEASE. Snapshots can be downloaded from the iText Artifactory and are appended with a
Our SNAPSHOT builds pass the same quality control as RELEASE versions. We don't introduce breaking changes between minor releases (
0.0.x), so the main difference from a
RELEASE version is that a
SNAPSHOT version will be continually updated and includes all the fixes and improvements introduced since the latest release.
If you’re using NuGet you can add the iText Artifactory as a NuGet packages server for your solution and download the SNAPSHOT version via the NuGet Package Manager.
To do this you need to create a file in the same folder as your solution (
.sln) file with the name: "
nuget.config". Its content should be as follows:
<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="iText Artifactory" value="https://repo.itextsupport.com/api/nuget/nuget" /> </packageSources> </configuration>
NOTE: If you do not see any snapshots listed, you should configure the NuGet Package Manager to include prerelease versions.
Alternatively you can browse the iText Artifactory if you want to manually download the
.nupkg file. You can open this file like a ZIP file to extract the dlls.
NOTE: If you’ve previously installed a SNAPSHOT build you may need to clear your local cache. In NuGet you can run
dotnet nuget locals all --clear from the NuGet Package Manager console.
Adding our iText 7 add-ons
If you would like to add one of our add-ons, please first have a look at the compatibility matrix and the installation guides of each of these add-ons.