Skip to main content
GroupDocs.Signature package icon

GroupDocs.Signature

GroupDocs.Signature for .NET is a comprehensive library that allows you to sign PDF, Word, Excel, JPG, and Presentation documents using various electronic signatures like text, image, barcode, QR code, metadata, form field, and digital signatures. With this API, you can also create, search, and verify electronic signatures for popular document formats, and customize your signing options to fit your needs.

Total Downloads
653.7K
653,669
Published
Dec 17, 2025
Latest stable version

Install

.NET CLI
dotnet add package GroupDocs.Signature --version 25.12.0
Package Manager Console
Install-Package GroupDocs.Signature -Version 25.12.0
PackageReference
<PackageReference Include="GroupDocs.Signature" Version="25.12.0" />

Frameworks

.NETStandard2.1 net6.0 .NETFramework4.6.2

Dependencies

Aspose.Drawing.Common
.NETStandard2.1
[25.7.0, )
Autofac
.NETStandard2.1
[7.1.0, )
[5.0.0, )
[5.0.0, )
Newtonsoft.Json
.NETStandard2.1
[13.0.3, )
SkiaSharp
.NETStandard2.1
[3.119.1, )
System.Buffers
.NETStandard2.1
[4.5.1, )
[8.0.1, )
[4.5.0, )
System.Drawing.Common
.NETStandard2.1
[6.0.0, )
System.Net.Http.Json
.NETStandard2.1
[8.0.1, )
System.Reflection.Emit
.NETStandard2.1
[4.7.0, )
[4.7.0, )
[7.0.0, )
[7.0.0, )
[5.0.0, )
[9.0.2, )
System.Text.Json
.NETStandard2.1
[8.0.5, )
[25.7.0, )
Autofac
net6.0
[7.1.0, )
[13.0.3, )
[3.119.1, )
[6.0.0, )
[4.7.0, )
Newtonsoft.Json
.NETFramework4.6.2
[13.0.2, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.

The published metadata declares 40 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.