Commercial license benefits

Unrestricted Access
Without the AGPL Friction

Keep your code private, ship on your own timeline, and get direct engineering support from the team behind PyMuPDF.

Contact Sales

Full Ownership

Keep proprietary code private and ship without AGPL source-disclosure obligations.

Support Included

Work directly with the engineering team on integrations, product questions, and deployment guidance.

Enterprise-Ready

Fit SaaS, OEM, internal tooling, and compliance-sensitive environments without open-source restrictions.

Common Commercial use cases

Empower Your Product Team

Contact Sales

SaaS & Hosted Products

Commercial licensing is the cleanest option when you need to keep proprietary code closed and avoid source disclosure.

OEM & Embedded Deployments

Bundle PyMuPDF into your own products with a commercial license designed for redistribution and customer-facing workflows.

Internal Enterprise Tooling

Get predictable licensing, long-term support, and a clear path for production use where compliance matters.

Two license routes

Pick the Model That Matches Your Deployment

Open Source and Community-Driven

If your project is open source, your users can receive the source code, and your use case fits the reciprocal obligations of the GPL ecosystem.


  • • Free to use and redistribute in compliant projects
  • • Source code availability remains part of the agreement
  • • Excellent for public, collaborative development

Private, Controlled, and Enterprise-Safe

Use PyMuPDF in proprietary software, internal tools, or customer-facing products without exposing your source code under AGPL obligations.


  • • No AGPL source-disclosure requirements
  • • Stronger control over proprietary code and distribution
  • • Direct access to technical support and product guidance
AGPLv3 obligations

The Open Source Option Comes With Clear Responsibilities.

Source Code Disclosure

If you deploy the AGPL version in a networked product, users interacting with it must receive the corresponding source code under the AGPL.

Code Changes Must Remain Open

Any modified version of the open-source code must also be distributed under AGPL terms, including the full source you ship.

Keep the Producer Notice

Preserve the relevant copyright and producer metadata in generated PDFs and document output created from the AGPL build.

Quick comparison

Choose the Right Licensing Path for Your Product.

Capability
AGPLv3
Commercial
Use in proprietary software
No
Yes
Share source code with users
Required in many networked deployments
Not required
Support and product consultation
Community support only
Included
Best fit
Open source public projects
SaaS, OEM, enterprise, internal tooling
Need a commercial license?

Talk to the Team About Commercial Licensing

PyMuPDF Logo

© 2026 Artifex Software Inc. All rights reserved.