head to head · open source

pdfcpu vs browserytools

pdfcpu has 8,842 GitHub stars, 633 forks, 121 open issues and last shipped 4 days ago. browserytools has 689 stars, 79 forks, 2 open issues and last shipped 5 days ago. pdfcpu leads on adoption by 1,183% (8,842 vs 689 stars). pdfcpu is written in Go under Apache-2.0; browserytools is written in TypeScript under AGPL-3.0. pdfcpu has attracted 7% as many forks as stars, browserytools 11%. pdfcpu was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (pdf-tools), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

pdfcpu ★ 8.8K browserytools ★ 689 category Business Software

← all 8884 open source comparisons

Side by side

pdfcpu browserytools
GitHub stars ★ 8.8K ★ 689
License Apache-2.0 AGPL-3.0
Written in Go TypeScript
Last push 2026-09-14 2026-09-13
Forks ⑂ 633 ⑂ 79
Self-hosting Yes Yes
Data ownership Your server Your server

pick pdfcpu if

  • You weight community size — 8.8K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full pdfcpu profile →

pick browserytools if

  • You want the browserytools feature set and don't need the biggest community
  • You prefer the AGPL-3.0 license terms
  • Your stack matches TypeScript
  • You evaluated both and browserytools fits your workflow better

full browserytools profile →

About pdfcpu

pdfcpu is a PDF processing library and command line tool written in Go. It lives in the Go and Golang ecosystem, is distributed under the Apache 2.0 license, and is listed under Business Software in the Document Management and E Signatures category. The project has existed for nine years, carries 8,835 stars and 628 forks, and lists 121 open issues. Its maintainer, Horst Rutter, is a member of the PDF Association, and the project documentation lives at pdfcpu.io. The GitHub topics attached to the repository are cli, go, golang, golang library, pdf, pdf files, and pdf tools, which describes both halves of what the…

read the full pdfcpu overview →

About browserytools

BrowseryTools is a collection of 152 free browser based utilities — image and PDF tools, converters, formatters, calculators, generators, and on device AI tools — built for people who need to process files or text without uploading anything to a server, signing up for an account, or tolerating ads.

read the full browserytools overview →

More in Business Software

Plane ★ 60K Twenty ★ 57K Odoo ★ 54K Cal.com ★ 49K Rocket.Chat ★ 46K cobalt ★ 43K

Related comparisons

docuseal vs pdfcpu bentopdf vs pdfcpu docuseal vs bentopdf docuseal vs documenso bentopdf vs documenso docuseal vs papermark docuseal vs opensign bentopdf vs papermark plane vs rocket-chat plane vs cobalt plane vs buzz rocket-chat vs cobalt plane vs jitsi plane vs srs plane vs huly plane vs zulip plane vs anki twenty vs anki odoo vs anki cal-com vs anki plane vs tutor twenty vs tutor odoo vs tutor cal-com vs tutor

More Document Management & E-Signatures projects

Compare either of these against the rest of the Document Management & E-Signatures field.

pdfcpu vs Docuseal pdfcpu vs bentopdf pdfcpu vs Documenso pdfcpu vs Papermark pdfcpu vs OpenSign pdfcpu vs Papra pdfcpu vs mm-wiki pdfcpu vs organize pdfcpu vs community pdfcpu vs docspell pdfcpu vs PaperKnife pdfcpu vs pdfx

Frequently asked questions

Is pdfcpu or browserytools more popular?

pdfcpu has 8,842 GitHub stars and browserytools has 689. pdfcpu has the larger community by that measure.

Are pdfcpu and browserytools free?

Both are open source. pdfcpu is licensed under Apache-2.0 and browserytools under AGPL-3.0. Neither carries a licence fee.

What is the difference between pdfcpu and browserytools?

pdfcpu is written in Go and browserytools in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, pdfcpu or browserytools?

Choose pdfcpu if you want the larger community (8,842 stars) or its Apache-2.0 licence terms. Choose browserytools if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.