The split between the free Community edition and the paid Pro Server rests on the difference between manual convenience and mission-critical automation. The impact of each varies significantly depending on who is using the tool: the publisher, who originates the file, or the print shop, which bears the financial risk of the press run.
Publisher
The file origin
Greatest fear: sending the wrong version and being charged for reprints.
Print Shop
The file destination
Greatest fear: a corrupt file reaching the plate-setter after plates are burned.
Origin Point
The publisher's greatest pain is sending an outdated PDF or one with pages out of order and later being held responsible for the print shop's reprint costs.
The Community edition is used manually at the terminal of a designer or editorial coordinator. Before uploading the final file to the print shop's FTP, the operator opens a terminal and runs a 1-to-1 comparison — for example, comparing the file exported from InDesign against the previous version approved by the editor-in-chief.
The CLI simply returns a success or error message on screen (e.g.
Differences found in page order),
forcing the operator to go back and correct the error manually.
Goal
A one-off safety check, no automation, ideal for small editorial teams.
Issuing audit reports
Larger publishers with dozens of monthly titles need legal protection. Pro Server exports a structured report (JSON or XML) listing the exact file parameters. The publisher sends this audit record together with the PDF to the print shop, proving the file left their hands structurally sound.
Batch sign-off
If a publisher is printing a collection of 50 books, they don't check them one by one. PDFJOB is configured on the publisher's server to scan the entire export folder in one pass before releasing the transfer to the print shop.
Destination Point
Print shops deal with a massive volume of files from unknown sources. A corrupt file reaching the plate-setter (CTP) can generate losses in the tens of thousands.
Manual triage
The prepress analyst uses the CLI for free on their workstation only when a specific file raises suspicion. No automation — a manual, time-consuming spot-check.
The Trojan Horse tactic
The Community edition's greatest value for a print shop is not internal use — it's getting clients to use it. The shop tells the publisher:
"To avoid delays on your print run, please download PDFJOB for free and validate your file before sending it to us."
The print shop uses free software to educate the client and reduce work for its own team.
This is where PDFJOB shines — and where the business makes money. In Pro Server, the tool acts as the print shop's automated gatekeeper.
Continuous monitoring via hotfolders
The CLI is installed on an internal server and configured to watch the network folder where all client files land via FTP. The human operator never touches the tool.
RIP integration via exit codes
As soon as a PDF lands in the folder, PDFJOB analyses it automatically.
If missing pages or broken fonts are detected, it emits an error exit code
(e.g. 3 — Needs Human Review).
Enterprise software such as Esko or Kodak Prinergy reads that exit code
and locks the file automatically, preventing it from reaching the press.
Critical data extraction
The CLI extracts trim dimensions, colour profiles, and page metadata into JSON, which the print shop feeds into its ERP system to automatically calculate quotes or ink consumption.
# File arrives via FTP from publisher
INCOMING="/ftp/inbound/cover_v4_final.pdf"
APPROVED="/archive/cover_approved.pdf"
pdfjob \
-original "$APPROVED" \
-modified "$INCOMING" \
-dpi 300 -t 0.03 \
-license /etc/pdfjob/pdfjob.lic
if [ $? -ne 0 ]; then
mv "$INCOMING" /quarantine/
# Esko / Prinergy reads exit code →
# locks job, alerts operator
else
mv "$INCOMING" /approved/
# File proceeds to CTP
fi
Community Edition
Your marketing vehicle
A manual tool with no automation, focused on the individual operator — the art director at the publisher. Its purpose is to build the habit and establish the PDFJOB name in the market. When publishers start validating files before sending them, print shops notice. That's the flywheel.
Pro Server
Your technology insurance policy
Sold to print shops on annual per-server contracts, it runs silently in the background 24 hours a day, making automated decisions to reject or approve files before they consume expensive materials. This is where the serious revenue lives.
Ready to see how PDFJOB fits into your specific workflow?