Licensing and Source Code

This hosted PracticalPDF fork is offered under the GNU Affero General Public License v3.0. If you use this site over a network, you can access the corresponding source code for the deployed version.

AGPL Deployment

Corresponding source code is public

The source code for this deployment, including local modifications, branding changes, and legal-page updates, is available in the public repository below.

View Corresponding Source

What This Means

This deployment follows the open-source path. You may use, study, and modify the software under AGPL-3.0, subject to the obligations below.

Allowed Under AGPL

  • Use this hosted fork for free.
  • Fork and modify the code for your own AGPL-compliant use.
  • Host your own version if you also provide corresponding source code.
  • Redistribute your modified version under AGPL-3.0.

Required Under AGPL

  • Keep the software under AGPL-3.0 when distributing modifications.
  • Provide full corresponding source code to network users of your hosted version.
  • Retain applicable upstream license and copyright notices.
  • Comply with the licenses of any optional runtime components you enable.

Compliance Checklist

For This Hosted Fork

  • Source code is published at the repository linked on this page.
  • Shared footer navigation includes a persistent source-code link.
  • This deployment does not rely on a closed-source license path.

If You Reuse This Fork

  • Publish your modified source code if users access it over a network.
  • Keep AGPL notices and license text available in your repo.
  • Do not imply upstream endorsement of your rebranded fork.

Optional Runtime Components

Some advanced features can rely on optional third-party components configured at runtime. These components keep their own licenses. This deployment is intended to remain compliant by following the AGPL public-source path for the hosted service as a whole.

  • PyMuPDF (AGPL-3.0)
  • Ghostscript (AGPL-3.0)
  • CoherentPDF / CPDF (AGPL-3.0)

If you self-host a variant of this project, review the license terms for every optional component you enable and make sure your hosted deployment model remains compatible with those obligations.

Licensing FAQ

Yes. This deployment is offered under AGPL-3.0. The source code for the hosted version is publicly available at the linked repository.

If users interact with your modified version over a network, you must make the corresponding source code for that hosted version available to those users under AGPL-3.0.

No. A different product name or visual identity does not change the AGPL obligations attached to the software.