pdfToolbox
Preflight, correction and PDF standards validation, including PDF/UA accessibility checks.
Jobs Accessibility Edit
Operated by callas software GmbH
Where your files are processed
Mixed — depends on version and feature
The vendor's own documentation separates them. On the device: pdfToolbox Desktop on Windows, macOS and Linux server packages. On their servers: Server and CLI workflows, activation and update checks. A single answer for the whole product would be wrong for one of them. That is a property of the library itself: what an application built with it does with your file depends on that application, not on this.
It depends on the package. The desktop application works on files on the machine, and a Server or CLI deployment runs on a customer server, so a customer server is involved in server workflows and no server is not an accurate badge. The network behaviour has not been tested. The packaging is not four independent purchases: the vendor documentation says the Server and CLI package includes Desktop for profile configuration, and Server uses CLI in the background, with Linux under the Server and CLI package rather than as an assumed desktop platform.
What it does
pdfToolbox checks a PDF against a set of rules and then fixes what it finds. The rules come from preflight profiles, and the profiles are built on published standards — PDF/X and PDF/A for print and archiving, and PDF/UA for accessibility — so a file can be validated against a named standard rather than against a vendor's private idea of correct. It ships as a desktop application, as a plug-in inside Acrobat Pro, as a server product, and as a command line and an SDK, and it can run a chain of checks and corrections as an automated process plan. It is the tool the print and publishing industry reaches for before a file goes to press.
Best for: Production and prepress teams who need a PDF checked and corrected against PDF/X, PDF/A or PDF/UA before it is used, and organisations that want that validation to run unattended across thousands of files rather than by hand. Also the reasonable choice for anyone who needs PDF/UA conformance checked as part of a wider standards workflow rather than as a standalone accessibility tool.
Worth knowing: It is a preflight and correction engine rather than an editor or a remediator in the sense a reader might expect: it finds and fixes deviations from a profile, and a PDF/UA profile tells you whether a document meets the standard and repairs the mechanical failures, but it does not rewrite a document's tagging so that it becomes genuinely well-structured for a screen reader. Its desktop edition is built on Adobe PDF Library technology, which is a third-party dependency with its own licensing, and the product is sold through a worldwide reseller network with no published price list, so any budget figure has to come from a quote. The variants are separately licensed, which means "pdfToolbox" alone does not say what a team has bought — Desktop, Server, CLI and SDK are four purchases. The 14-day evaluation is documented separately from any ongoing free tier. An Adobe library dependency does not by itself prove that a buyer needs a separate Adobe licence. Automated preflight and semantic PDF/UA checking stay distinct, and the claims about industry-wide preference and the absence of any published price are removed rather than asserted without separate research.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Windows · macOS · Self-hosted
- Website
- callassoftware.com
- Requires an account
- Not applicable
- Free tier
- Not verified
- Watermark on the free tier
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Self-hosted
- Open source
- No
- Self-hostable
- Yes
- Licence
- Commercial, sold through resellers; Desktop, Server, CLI and SDK licensed as separate variants
- Redaction
- No redaction feature
- Programmatic access
- Command line · Embeddable library
- Last availability check
- Responded in 400 ms 16 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
What that does not establish: Recorded as `none` on absence. The product page is a detailed description of what pdfToolbox does — preflight profiles, checks and fixes, processing reports, process plans, and the Desktop, Server, CLI and SDK variants — and it never mentions redaction or removing content, so there is no feature here that this index would classify as redaction. What it does not establish: that no correction could ever delete content. A profile fix can remove or change objects in a document, which is why the absence is recorded as "no redaction feature" rather than "cannot remove anything". A reader who needs redaction should read this as "not the tool for that", not as "safe to use on a secret document".
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded — not that we tested the behaviour, unless the note says we did.
-
“Quality control in pdfToolbox is based on preflight profiles. These profiles define which checks are performed and which fixes are applied to incoming PDF files. Profiles can be created from scratch, but in practice, they are often built on established standards to avoid reinventing common rules. pdfToolbox supports ISO standards such as PDF/X, PDF/A, and PDF/UA, as well as specifications from organizations like the Ghent Workgroup.”
Checked by us — the source says this Read 1 October 2026
Confirmed. The quoted text appears in the rendered page as read on 2026-10-01. This claim was carried as reported rather than checked until this read.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- a8f8f1735c849fc6861d1bea8154ca5eec2005beb7d23db351f4e62af8db5fe6
How we checked: Read as rendered text in headless Chrome on 2026-10-01 and saved to the evidence archive, so the read can be repeated against the same file. Comparison ignores case, punctuation and hyphenation, which is why "open-source" on the record matches "open source" on the page.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked — it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.
Related reading
- Checking a PDF for accessibility — what makes a PDF accessible, and how it is checked.