SixLabors Dependency Licensing
IronPDF depends on several SixLabors NuGet packages, and SixLabors has changed its licensing model across versions. You do not need a separate SixLabors license to use IronPDF — the SixLabors packages are an internal, transitive dependency of IronPDF, not one you reference directly.
Do you need to comply with the SixLabors commercial license separately?
No. The 3.x.x SixLabors versions that support later .NET releases use the Six Labors Split License, whose commercial terms apply to direct closed-source use. Because you consume SixLabors only indirectly through IronPDF rather than as a direct dependency, no separate SixLabors licensing action is required on your end.
Which license applies on .NET Framework?
On the versions that support .NET Framework, SixLabors continues to use the Apache license.
Are the Apache-licensed versions still supported?
Yes. SixLabors still supports the 2.x.x Apache-licensed versions, and bug-fix releases remain available.


