pdfToolbox
Commercial PDF preflight, correction and standards validation, including PDF/UA checks.
Jobs Accessibility Edit
Operated by callas software GmbH
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
Accessibility
Browse all accessibility toolschecking PDF/UA accessibility conformance with pdfToolbox, where the product's profiles support PDF/UA checks and fixups alongside PDF/X and PDF/A, and the Desktop, Server, CLI and SDK variants can run those profiles manually or in automated process plans. The scope records PDF/UA conformance checking/validation and profile-driven mechanical corrections/fixups, and makes clear that mechanical preflight fixes do not guarantee semantic accessibility, do not rewrite tagging into genuinely screen-reader-ready structure, and do not replace human remediation or establish legal accessibility; it is not a screen-reader authoring or full remediation editor
Edit
Browse all edit toolsapplying documented PDF preflight corrections and processing operations with pdfToolbox, where profiles define checks and fixups and process plans automate validation, correction, optimization and conversion; the REST API preflight operation can validate, correct, optimize or convert PDFs, and Server/CLI/SDK provide customer-managed automated workflows while Desktop provides manual correction. The scope records profile-driven correction/fixup, process-plan and documented validation/optimization/conversion operations, keeps manual Desktop correction distinct from automated Server/CLI/SDK processing, and makes no generic body-text PDF-editing, OCR, redaction, signing, arbitrary content-authoring or semantic-accessibility-remediation claim
Where your files are processed
Mixed - depends on version and feature
The vendor's own documentation separates them. On the device: pdfToolbox Desktop (standalone or Adobe Acrobat Pro plug-in), pdfToolbox Server, CLI and SDK (customer-managed). On their servers: pdfToolbox in the Cloud / OEM API. 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.
Desktop, Server, CLI and SDK are normally local or customer-managed: Desktop works on local files, and Server/CLI/SDK run on the customer's own hardware, including Linux server/CLI/SDK deployments and Docker/REST API installations. The optional pdfToolbox in the Cloud/OEM API at api.callassoftware.io is an AWS-managed callas service requiring an x-api-key and is a separate product, not the normal local product.
Activation and update checks do not make the Desktop or Server product vendor_cloud.
What it does
pdfToolbox is callas software's commercial PDF processing platform. The current release is 17.1.692, dated 1 October 2026.
It checks PDFs against configurable preflight profiles built on standards such as PDF/X, PDF/A and PDF/UA, then applies fixes; process plans can automate validation, correction, optimization and conversion. The product has four normal variants: Desktop (standalone or an Adobe Acrobat Pro plug-in) for manual preflight and correction on Windows and macOS; Server for customer-managed automated workflows; CLI for command-line batch processing; and SDK for embedding the engine through C/C++ libraries with .NET and Java wrappers.
Linux is supported through the server/CLI/SDK packages, not as a Desktop platform. The normal Desktop/Server/CLI/SDK product is self-managed and local or customer-hosted, including REST API and Docker deployments on customer hardware.
Separately, pdfToolbox in the Cloud is an OEM-only, AWS-managed API at api.callassoftware.io with x-api-key authentication; it is not the normal self-managed product and is not required for Desktop/Server/CLI/SDK use. All variants have a 14-day trial; pricing is commercial and not published.
The product is associated with, but not dependent on a separate Adobe licence merely because Desktop uses Adobe PDF Library technology.
Best for
Production and prepress teams who need PDF/X, PDF/A or PDF/UA checked and corrected before use, and organisations that want validation and correction to run manually in Desktop or unattended through customer-managed Server/CLI/SDK workflows.
Worth knowing
The current release is 17.1.692, dated 1 October 2026. The normal product is not a hosted SaaS: Desktop runs locally on Windows/macOS, and Server/CLI/SDK run on customer-managed hardware, including Linux server/CLI/SDK packages, Docker and a REST API.
Activation and update checks do not turn those workflows into vendor cloud. The optional pdfToolbox in the Cloud/OEM API at api.callassoftware.io is a separate, OEM-only, AWS-managed service with x-api-key authentication; it is not the normal Desktop/Server/CLI/SDK product and its availability does not make the normal product hosted.
Linux is supported for Server/CLI/SDK, not as a Desktop platform. The Desktop variant is built on Adobe PDF Library technology, a third-party dependency with its own licensing; that alone does not prove a buyer needs a separate Adobe licence.
The variants are licensed separately, though the Server/CLI package includes Desktop for profile configuration and Server uses CLI behind the scenes, so the packaging is not four unrelated purchases. All variants have a 14-day trial, not a permanent free tier; pricing is quote-based and no public price is invented.
PDF/UA profiles validate conformance and fix mechanical issues, but they do not rewrite the document's tagging into genuinely well-structured, screen-reader-ready content; semantic accessibility still needs human remediation. The product is a preflight/correction engine and process-plan tool, not a generic body-text PDF editor, and it does not replace Acrobat-style authoring or guarantee legal accessibility.
Automated Server/CLI/SDK processing is distinct from the manual Desktop correction workflow.
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 · Linux · API · Self-hosted
- Website
- callassoftware.com
- Requires an account
- Not applicable
- Free tier
- No
- Watermark on trial output
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Self-hosted
- Open source
- No
- Self-hostable
- Yes
- Licence
-
Commercial, sold through callas software GmbH and its reseller network.
Commercial, sold through callas software GmbH and its reseller network. Desktop, Server, CLI and SDK are separately licensed variants; the Server/CLI package includes Desktop for profile configuration and Server uses CLI in the background, so they are not four completely independent purchases.
The SDK is separately licensed. All variants have a documented 14-day free trial, but there is no permanent free tier.
The optional pdfToolbox in the Cloud/OEM API is a separate OEM-only AWS-managed service with its own licensing. No public price list is published.
- Redaction
- No redaction feature
- Programmatic access
- Command line · Embeddable library · HTTP API
- Last availability check
- Responded with HTTP 503 21 October 2026
Checked automatically by our own runner, not reported by the vendor. The site answered, but not with a success status.
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.