Assembling PDFs from the command line: cpdf, qpdf, pdfcpu and pdftl

qpdf is our choice for local page-assembly scripts, with a narrow lead over pdfcpu. Consider cpdf for bookmark-aware work, or our Rising Star pdftl for PDFtk-style pipelines and form commands.

PRACTICAL PICKSPreferredPickOur Preferred PickScripted page assembly · narrow lead$0

qpdf

Page selection, interleaving, splitting and rotation, with official Windows, macOS and Linux binaries. Scores 4.10 against pdfcpu’s 4.05.

Bookmarks come from the first input only, and malformed files with repeated dictionary keys can lose images without a --check warning.

Why qpdf is our Pick
PRACTICAL PICKSRisingStarOur Rising StarPDFtk-style pipelines$0

pdftl

Local assembly, chained operations and documented FDF form filling, powered by pikepdf and qpdf.

Python dependencies add upkeep, and an open report describes trouble with equals signs in filenames.

Why consider pdftl

Who is this article for? People writing or maintaining a terminal script that combines, selects, reorders or splits pages of PDF files on their own computer, sometimes filling forms or producing page images along the way.

About 19 min read

What Preferred Pick, Rising Star and Ready to Rock mean

The quick list

Start with qpdf for page assembly; compare pdfcpu for broader commands, cpdf for bookmark-aware work and pdftl for PDFtk-style pipelines. All four have a free open-source route for local scripts.

All four offer a no-charge open-source route for local scripts, checked November 1, 2026: Apache-2.0 for qpdf and pdfcpu, AGPL for cpdf and MPL-2.0 for pdftl. Setup and maintenance take your time. Commercial integration and redistribution may need different terms.

The comparison at a glance

Compare page handling, what happens to forms and bookmarks, page rendering and the build each script will depend on.

qpdf is our Pick, with a narrow advantage over pdfcpu for local page assembly. Columns follow assessment scores: cpdf, qpdf, pdfcpu and pdftl; scores describe documented fit, not measured speed or fidelity.

Command-line tools for assembling PDFs
Featurecpdfqpdfpdfcpupdftl
Best fitBookmark-aware splitting and document controlsPreferred Pick: local scripted page assembly; narrow leadBroader document scripts with forms and bookmarksRising Star: PDFtk-style commands and pipelines
Overall assessment out of five4.184.104.053.98
Select and combine pagesMaker documents merging with bookmark preservation--pages with ranges, exclusions and odd/even selectionmerge; trim and collect commands also listedcat with per-input ranges; operations can be chained
Forms and annotationsAnnotation controls advertised; form survival needs checkingForms copied per input in most cases; check shared fieldsForm and annotation commands; no blanket preservation guaranteefill_form and generate_fdf; release notes describe fixes to signature fields
Bookmarks after assemblyMaker claims preservation and splitting by bookmarksFirst input only; omitted destinations stop workingBookmark commands; recent fixes to named destinationsBookmark controls; release notes say non-GoTo actions now preserved
License and local-use chargeAGPL source route · $0; commercial license availableApache-2.0 · $0Apache-2.0 · $0MPL-2.0 core · $0
Main limitForm and signature preservation needs checking; macOS not notarizedOpen repeated-key regression can remove page images without warningRecent reading, encryption and resource-exhaustion fixes; keep currentOpen equals-sign filename report; dependency upkeep

qpdf is our Pick, narrowly ahead of pdfcpu for this reader; our Rising Star is pdftl. Columns follow assessment scores: cpdf, qpdf, pdfcpu and pdftl. All four have a free local-use route. Keep signed originals: a visible signature is not proof of validity after assembly. Pin versions and check images, fields and links after upgrades. Public-source research; no tools installed or PDF processing performed. Incumbent evidence checked October 19, 2026, with candidate and cost information checked November 1, 2026. Next substantive review: December 18, 2026, or sooner after a material release or security finding.

All features and sources 15 criteria

Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.

Page handling and document behavior

Show 10 criteria
Page handling and document behavior
Featurecpdfqpdfpdfcpupdftl
Best fitBookmark-aware splitting and document controlsPreferred Pick: local scripted page assembly; narrow leadBroader document scripts with forms and bookmarksRising Star: PDFtk-style commands and pipelines
Overall assessment out of five4.184.104.053.98
Local-use cost score out of five5.005.005.005.00
Select and combine pagesMaker documents merging with bookmark preservation--pages with ranges, exclusions and odd/even selectionmerge; trim and collect commands also listedcat with per-input ranges; operations can be chained
Separate output filesMaker documents splitting by size, page count or bookmarks--split-pages: single pages or groupssplit, including bookmark modeburst
Interleaving and rotationRotation documented; interleaving not established here--collate and --rotaterotate; interleaving details not established hereshuffle and rotate
Forms and annotationsAnnotation controls advertised; form survival needs checkingForms copied per input in most cases; check shared fieldsForm and annotation commands; no blanket preservation guaranteefill_form and generate_fdf; release notes describe fixes to signature fields
Bookmarks after assemblyMaker claims preservation and splitting by bookmarksFirst input only; omitted destinations stop workingBookmark commands; recent fixes to named destinationsBookmark controls; release notes say non-GoTo actions now preserved
Digital signaturesValidity after assembly not establishedNo signing; removing restrictions invalidates signatures but keeps appearanceSignature inspection and removal; assembly validity not establishedOptional signing and signature inspection; saving can invalidate signatures
RenderingProduct page advertises PNG/JPEG page exportNo page renderingImage extraction is not page renderingOptional render operation
Sources for page handling and document behavior

Checked November 1, 2026: qpdf repository, release notes and image-loss report; pdfcpu project, releases, security, OSV and Homebrew; cpdf product, source, 2.9.3 manual, desktop binaries and Homebrew; pdftl project, releases, security and issues. qpdf command details come from its manual, checked October 19, 2026. Capabilities are documented claims, not results with your files.

Setup, cost and maintenance

Show 5 criteria
Setup, cost and maintenance
Featurecpdfqpdfpdfcpupdftl
License and local-use chargeAGPL source route · $0; commercial license availableApache-2.0 · $0Apache-2.0 · $0MPL-2.0 core · $0
SetupDependency-free Windows, macOS and Linux binaries; macOS codesigned, not notarizedOfficial Windows, macOS and Linux binaries; macOS not notarizedStandalone CLI; current release and Homebrew package listedPython 3.10+; pipx recommended for Windows, macOS and Linux
Release evidence2.9.3 binaries, October 21, 202612.4.2, September 26, 20260.16.4, October 27, 20260.29.0, September 23, 2026
Main limitForm and signature preservation needs checking; macOS not notarizedOpen repeated-key regression can remove page images without warningRecent reading, encryption and resource-exhaustion fixes; keep currentOpen equals-sign filename report; dependency upkeep
Maintainer recordJohn Whitington / Coherent GraphicsJay Berkenbilt and Manfred HolgerHorst Rutterpdftl-dev public handle
Sources for setup, cost and maintenance

Checked November 1, 2026: qpdf repository, release notes and image-loss report; pdfcpu project, releases, security, OSV and Homebrew; cpdf product, source, 2.9.3 manual, desktop binaries and Homebrew; pdftl project, releases, security and issues. qpdf command details come from its manual, checked October 19, 2026. Capabilities are documented claims, not results with your files.

What matters when choosing

qpdf is our Practical Pick for someone writing or maintaining a terminal script that combines, selects, reorders or splits pages from PDF files on their own computer. It is free under the Apache-2.0 license. One --pages command handles page ranges, exclusions and interleaving from any number of files, and --split-pages writes one page or a fixed group of pages per file. Since version 12.4.2, released September 26, 2026, the project publishes its own binaries for Windows, macOS and Linux on both x86-64 and ARM64, and its download notes say virtually every Linux distribution packages it. Its manual is also particularly explicit about what page assembly does not carry over, and that is the most important compromise: qpdf copies pages, not whole documents. Bookmarks and structure tags come only from the first input file, and bookmarks that point to pages you leave out stop working. qpdf manual, release notes, download notes

Check what is on each output page, not only how many pages there are. An open report filed October 3, 2026 says that since 12.4.0, qpdf discards a dictionary that repeats the same key several times, which is a defect in the input file. When that dictionary lists a page’s images, the images disappear from the output. In the reporter’s own document, 170 image placements vanished from four pages on a plain rewrite or split, and qpdf --check gave no warning. The maintainer called the report high quality and said the proposed fix looked sensible; the November 1 release notes still ended at 12.4.2. qpdf also does not render pages or fill forms, and its manual warns that a file passing --check may still contain errors in page content. Issue 1787, qpdf manual

pdftl is our Rising Star for readers who want familiar PDFtk-style commands and can manage Python dependencies. Its documentation shows page assembly, interleaving, splitting, rotation and FDF form filling, with operations chained without intermediate files. It runs on Windows, macOS and Linux. Check filenames containing =: an October 22 report says they cause trouble, and merging still needs checks on fields and links. Its documented breadth earns the recommendation; we did not measure fidelity or speed. Project and license, releases, filename report, checked November 1, 2026.

The scores are close: cpdf 4.18, qpdf 4.10, pdfcpu 4.05 and pdftl 3.98 out of five. qpdf is our Pick, with a narrow advantage over pdfcpu for this script-writing reader. Choose pdfcpu for its broader document commands, or cpdf when bookmark-aware splitting matters more than the simplest setup. qpdf remains our choice for the core assembly script because of its explicit limitations and official builds. All four offer a no-charge open-source route for local scripts; embedding them in distributed software is a different licensing decision.

These are researched judgments from manuals, release and package records, vulnerability databases and public issue reports checked October 19, 2026, with the additional sources dated November 1 below. We did not install or run any tool, and nothing here measures page fidelity, speed or security. A visible signature is not proof that the signature is still valid: qpdf documents an option that keeps the appearance while invalidating the signature, and none of these tools establishes that page assembly keeps a signature valid. Keep signed originals and treat an assembled copy as a new document. Three conditions would change our recommendation: the script fills forms from FDF or XFDF data (keep PDFtk where it already works), it must also produce page images (consider mutool), or your input files come from producers that repeat dictionary keys and the qpdf fix has not shipped (check images on every output, or stay on a version you have checked). Whichever you choose, pin the version, keep the original PDFs and form data outside your scripts, and rerun a small set of sample files after each upgrade.

cpdf

Bookmark-aware assembly

$0AGPL · dependency-free desktop binaries

Consider cpdf for bookmark-aware assembly and document controls. Use version 2.9.3 binaries or a package route; check forms and links after assembly.

Reasons to choose it

  • Maker documents bookmark-aware merging and splitting
  • Rotation, metadata, annotations and AES-256 encryption
  • Dependency-free Windows, macOS and Linux binaries

What to watch

  • Detailed form and signature preservation needs checking
  • macOS executable is codesigned but not notarized
  • Commercial integration may require a different license

Coherent PDF’s command-line toolkit advertises merging and splitting by page count, bookmarks or file size while preserving bookmarks, plus rotation, annotations, metadata and AES-256 encryption. Choose it when those document controls save more work than a minimal page assembler. Its source repository identifies John Whitington and offers AGPL-3.0 software; Homebrew independently lists an AGPL package. Commercial licensing is available for uses that cannot comply with the AGPL. Product, source and build instructions, Homebrew, checked November 1, 2026.

Version 2.9.3 has dependency-free binaries for Windows, macOS and Linux, plus package-manager routes. The macOS executable is codesigned but not notarized, so its instructions say you may need to allow it in system settings. Use a versioned release rather than the unstable development branch. The October 2026 manual documents page selection and chained operations, but does not establish how every form or signature survives assembly. Treat bookmark preservation as the maker’s claim and check fields and links on your files. Binaries and installation, 2.9.3 manual, source instructions, checked November 1, 2026.

Used cpdf? Share your experience to help other readers choose.

qpdf

Preferred Pick · scripted page assembly

$0Apache-2.0 · official binaries

Choose qpdf for a script that combines, selects, reorders or splits pages. Its lead is narrow: 4.10 against pdfcpu’s 4.05. Pin the version and check output images, fields and links.

Reasons to choose it

  • Page ranges, interleaving, splitting and rotation
  • Official Windows, macOS and Linux binaries
  • Explicit documentation of assembly limits

What to watch

  • Bookmarks and tags come from the first input only
  • Repeated dictionary keys can cause image loss without a --check warning
  • No page rendering or form filling

qpdf describes itself as a program and C++ library for “structural, content-preserving transformations” on PDF files, and says it is not a viewer or a converter. For page work, --pages selects page ranges from any number of inputs, counted from either end and with exclusions; --collate interleaves pages in groups; --split-pages writes one page or groups of pages per file; and --rotate turns selected pages. It can also overlay or underlay pages, flatten annotations, generate missing form-field appearances and describe a file as JSON. Output can be encrypted with 256-bit AES; the manual calls 40-bit encryption and 128-bit encryption without AES insecure and requires --allow-weak-crypto for them. We verified that qpdf is licensed under Apache-2.0 and that its README names Jay Berkenbilt and Manfred Holger as its copyright holders and release signers. Overview, manual, repository

Know what page selection carries over. Since version 10.2 in 2021, --pages and --split-pages copy form fields from each source file, and the release notes say form behavior is preserved “in most cases”, with exceptions such as fields shared across pages. The manual’s limitations section still lists form fields with bookmarks and tags as document-level data “copied in their entirety from the primary input file”, so check fields from every input after a merge. Bookmarks to pages you omit stop working, page labels are kept from all files, and --empty as the first input avoids carrying over the first file’s metadata. Selecting the same page twice makes both copies share their data, which the manual warns may not work correctly with form fields. Page-selection limits, 10.2 and 10.3 release notes

Read the full qpdf analysis and sources

The October 3 regression, still open when checked November 1, is the reason to check output content now. It affects 12.4.0 to 12.4.2 and only input files that repeat dictionary keys, which the PDF specification does not allow but some producers write. Until a fix ships, compare page images or counts of images on a sample of files from unfamiliar sources, rather than relying on page count or --check. Issue 1787

Releases are frequent and change details. 12.4.0 (August 9, 2026) tightened checks on damaged and malicious input, adding depth limits to reduce stack overflows. 12.4.1 (August 27) fixed a denial-of-service flaw in the linearization check that had been reported publicly in August, according to the maintainer. 12.4.2 (September 26) added the macOS, Windows ARM64 and Linux ARM64 binaries, changed linearized output for some files, and made numeric options reject trailing characters, which can break a script that relied on the old leniency. The macOS binaries are not signed or notarized, so you must clear Apple’s quarantine flag before running them. Debian 13 packages 12.2.0, and Homebrew 12.4.2. Release notes, issue 1750, download notes, Debian qpdf, Homebrew qpdf

Choose mutool if the same job needs page images, and PDFtk if an existing script fills forms from FDF or XFDF data; qpdf does neither. --remove-restrictions “invalidates and disables any digital signatures but leaves their visual appearances intact”, so do not judge a signed copy by how it looks. Manual

Used qpdf? Share your experience to help other readers choose.

pdfcpu

Broader document scripts

$0Apache-2.0 · use a current build

Consider pdfcpu when assembly is one part of a broader script covering forms, bookmarks, attachments or encryption. Use 0.16.4 for the documented crafted-input fixes.

Reasons to choose it

  • Merge, split, trim and rotate commands
  • Forms, bookmarks and attachments in the same CLI
  • Current release addresses resource exhaustion during reading and migration

What to watch

  • Recent releases corrected content and encryption defects
  • Upgrading does not repair output from earlier versions
  • Preservation on your files still needs checking

pdfcpu combines a Go library with a standalone CLI. Its documented commands cover merging, splitting, trimming, rotation, forms, bookmarks, attachments and encryption; the README gives a direct two-file merge example. Choose it if assembly is one part of a larger document script. It is Apache-2.0 software maintained by Horst Rutter. The repository lists 0.16.4, released October 27, 2026; Homebrew independently lists the package. Project, releases, Homebrew, checked November 1, 2026.

Use the current release. Version 0.16.4 addresses crafted PDFs that could exhaust CPU or memory or terminate the process during reading, validation and page migration. Version 0.16.2 fixed plaintext strings left in some encrypted output and recursive stream references; upgrading does not repair earlier output. OSV’s High-severity recursion advisory identifies versions through 0.11.1, rather than the current release. These fixes are project statements, not results we reproduced. They explain why we give qpdf a small advantage on maintenance risk despite pdfcpu’s broader commands. Release details, security notices, OSV advisory, checked November 1, 2026.

Used pdfcpu? Share your experience to help other readers choose.

pdftl

Rising Star · PDFtk-style pipelines

$0MPL-2.0 · Python 3.10 or later

Choose pdftl for PDFtk-style commands, chained operations and documented FDF form filling. Keep originals and check fields and links.

Reasons to choose it

  • cat, shuffle, burst and rotation commands
  • Pipelines without intermediate files
  • Local core runs on Windows, macOS and Linux

What to watch

  • Python dependencies add setup and update work
  • Open report of trouble with equals signs in filenames
  • Optional signing and rendering need extra dependencies

pdftl is a Python CLI powered by pikepdf and qpdf. Its README demonstrates cat, shuffle, burst, rotation and filling a form from FDF data, and shows operations chained with --- without intermediate files. It also lists bookmark editing, annotations, AES-256 encryption and optional signing and rendering. These are documented capabilities, not a promise that every form or bookmark survives a merge. Project, checked November 1, 2026.

Choose it for a new script that benefits from PDFtk-like syntax and several operations in one pipeline. The first public release recorded in the package history checked October 19 makes it a recent entrant; the current repository lists 0.29.0 from September 23, 2026. The MPL-2.0 core requires Python 3.10 or later, with pipx recommended on Windows, macOS and Linux. Extra features add dependencies, and some need Java. The core assembly job does not require its server or those extras. Repository, release notes, checked November 1, 2026; first-release evidence checked October 19, 2026.

Read the full pdftl analysis and sources

Keep original PDFs and check output, especially forms and links. Release notes describe fixes for dropped non-GoTo bookmark actions and signature-field corruption, and warn that saving can invalidate a signature. An open October 22 issue reports trouble with = in filenames. There is no published security policy or advisory on its security page, and the maintainer uses the handle pdftl-dev rather than a named legal operator. Published local source reduces reliance on a hosted operator, but it does not prove security or fidelity. We prefer qpdf’s simpler installation for ordinary assembly; pdftl’s pipeline and form commands earn the newcomer recommendation. Releases, issue list, security page, checked November 1, 2026.

Used pdftl? Share your experience to help other readers choose.

Which product are we missing?

Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.

Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.

Suggest a product

Opens an email draft with this article attached as a link. Nothing is sent until you send it.

No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.

What people are saying

Public reports are a check on project claims, not a measured reliability score. qpdf’s issue tracker shows what to watch for. Besides the October regression described above, a September 27, 2026 report says qpdf decodes and recompresses image streams whose filter is written as a one-element list, which the reporter says iText and pdftk produce, and that this removes their predictors; in the reporter’s example a scanned file grew 31%. --stream-data=preserve avoided it, and a proposed fix was open on October 19. A September 22 report describes files that Chrome, MuPDF and pdftk-java opened but qpdf refused because of one wrong generation number; the reporter accepted that qpdf was following the specification. Recompression report, refused file report

An August 10, 2026 public issue said that a privately reported flaw in qpdf’s linearization check, endless recursion on a crafted file that hangs release builds, was still unfixed in 12.4.0. The maintainer acknowledged it and on August 28 said it was fixed in 12.4.1. We did not reproduce the flaw or the fix. Issue 1750

For PDFtk, a 2020 Stack Overflow question describes difficulty filling a form and merging in one command, consistent with the manual’s one operation per run; we last read it on September 7, 2026. pdftk-java’s tracker had 76 open issues on October 19, including 2026 reports about how dates and localized numbers are written in metadata; we did not verify them. Stack Overflow question, pdftk-java project

We found no representative sample of user experience for these versions. Our October 19 searches for vulnerabilities, abandonment notices, disputes and lawsuits involving qpdf, PDF Labs, pdftk-java and Artifex found nothing beyond the items in this article that changed our conclusions; a search that finds nothing is not proof that nothing exists.

How we researched

This is public-source research. We did not install or run any tool, assemble or encrypt any file, test a signature or reproduce any reported bug. No project supplied access, payment or input, and we use no affiliate links. We first compared these tools on September 7, 2026, and rechecked every material claim on October 19, 2026: releases, binaries and packages, licenses, documented page, form and encryption behavior, vulnerability records and open reports. We read project manuals and release notes, GitHub and GitLab repository records, Debian and Homebrew package records, the OSV vulnerability database and GCC’s release notes. The Stack Overflow question did not load for our automated check, so it is cited from our September 7 reading.

We wrote this for someone maintaining a terminal script that combines, selects, reorders or splits pages of local PDF files, sometimes filling forms or producing page images along the way. We fixed five criteria and their weights before comparing: page-assembly fit (30%), behavior with forms, bookmarks and signatures (15%), change and maintenance risk (25%), setup and portability (15%), and local-use cost (15%). qpdf remains our recommendation for the core assembly script, with a narrow advantage over pdfcpu. Rendering is a reason to consider mutool separately. We expanded the original comparison to include pdfcpu, cpdf and relevant newer tools. The chart shows the four leading options in our assessment. No tool was credited with preservation behavior that its documentation did not establish.

On November 1, 2026, we revisited the newcomer candidates using project and package records. pdftl earns our Rising Star for documented pipeline and form commands. pdq provides range extraction and rendering but does not restructure interactive document features; pdf-cli provides convenient single-binary assembly commands but leaves merge behavior for forms and bookmarks less explicit. Neither pre-1.0 numbering nor a small review count counted against a tool. The directories did not provide usable discovery results, so discovery remains limited. pdq, pdf-cli, checked November 1, 2026.

Other complete scores were PyPDFForm 3.75, pdf-cli 3.63, pdfly 3.60, pdq 3.53, MuPDF mutool 3.38, pdfjam 3.28, Ghostscript 3.23, oxidize-pdf-cli 3.23, pdfer 3.15, and PDFtk Server and pdftk-java 3.08 each. pdfly documents concatenation and page extraction; PyPDFForm combines forms with extraction and merging. pdfjam requires LaTeX and a Unix shell and explicitly loses interactive features. Ghostscript interprets and recreates PDF output; its documentation lists losses and exceptions for non-page content, including Link and Widget annotations. pdfly, PyPDFForm, pdfjam, Ghostscript output documentation, pdfer, oxidizePdf, checked November 1, 2026.

MuPDF remains worth considering when the script must render pages. As checked October 19, 2026, Debian 13 packages MuPDF 1.25.1 and the checked vulnerability records list unresolved issues for that package: use a current build for unfamiliar PDFs. Keep PDFtk where an existing FDF or XFDF pipeline works, but multi-input assembly omits XFA data, and need_appearances cannot be combined with flatten; check filled forms in the recipient’s viewer. Debian MuPDF, vulnerability record, PDFtk manual, checked October 19, 2026.

We exclude pdf-cli from recommendations because its 2.0.0 dependency file pins pdfcpu 0.11.1, covered by the High-severity recursion advisory for parsing untrusted PDFs. The current standalone pdfcpu release is outside that affected range. Dependency file, OSV advisory, checked November 1, 2026.

We could not confirm Poppler’s local-use cost from readable product pages. Poppler, the older pdf_merge script and Bulk-Ebook-Merger-Converter have no complete score because command, preservation or license-cost evidence is incomplete. pdfly’s first-release date and desktop support were not established; PyPDFForm was already presented publicly in 2023. Presse lacked readable product evidence, while Stet, BlazePDF and Nano PDF did not establish this local page-assembly job. Programming libraries alone, browser editors and hosted tools do not meet the standalone local command-line requirement. Poppler, pdf_merge, Bulk-Ebook-Merger-Converter, PyPDFForm, checked November 1, 2026.

ToolPublic sourcesWhat remains uncertain
pdfcpuRepository, 0.16.4 release notes, security notices, OSV and Homebrew.Behavior on your files; release fixes are not independently reproduced.
cpdfProduct claims, source README, Homebrew, 2.9.3 manual and desktop binary instructions.Detailed preservation behavior for forms and signatures.
pdftlREADME, releases, security page and an external filename issue.Merge fidelity, dependency versions and maintainer identity beyond a public handle.
qpdfOverview, manual, release notes, repository, download notes, issue tracker, Debian and Homebrew package records.When the October 3 regression will be fixed, how often real files repeat dictionary keys, how fully form fields survive merges in your files.
MuPDF mutoolCommand documentation, license, change log and 1.28.5 changes, OSV vulnerability records, Debian and Homebrew package records.What merge keeps of forms, bookmarks and annotations; commercial license terms and price; rendering accuracy and speed.
PDFtk ServerProduct page, manual, license, version history, pdftk-java releases and commit history, Debian and Homebrew records, GCC release notes, a 2020 user question.Behavior of the 2013 build on current systems, differences between PDF Labs’ build and pdftk-java, the 128-bit encryption algorithm.

None of this establishes page fidelity, speed, signature validity or security with your files. Next substantive review is due December 18, 2026, or sooner after a fix for the qpdf regression, a major release of a compared tool or a license change. Found a changed release or behavior? Contact the editors.

Sources and evidence

Incumbent sources were checked October 19, 2026 unless another date is given; new candidate, pricing and qpdf regression sources were checked November 1, 2026. Project manuals establish documented behavior, not behavior with your files. Release, package and license records establish their stated versions, dates and terms. Issue reports are the reporters’ claims unless a maintainer response is noted. Workflow fits are editorial judgments.

This is a researched comparison, not a product review. Method: evidence standard, editorial picks.