PDF-XChange Core API SDK
Windows SDK for creating and manipulating PDFs, now sold only to approved developers on application.
Operated by Tracker Software Products
Where your files are processed
No server involved
A compiled library embedded in the application you build, licensed by licence strings compiled in at release time. There is no vendor service in the path and no account: Tracker Software operates no processing endpoint in that path. 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.
A compiled library that runs inside the application you build, on machines you control. There is no vendor service in the path and no account to sign in to: licensing works by licence strings compiled into the application, which the demo limitations page describes as what removes the watermark. That is a structural fact about an embeddable SDK rather than a measurement, and the same reasoning the index applies to the other embedded libraries.
What it does
The PDF-XChange Core API SDK is the foundation library in Tracker Software's developer range: a Windows API and set of libraries for creating and manipulating PDF files, used by the same company that sells the PDF-XChange Editor. The documented feature set is broad and practical — page insertion, deletion, re-ordering and cropping, merging, overlaying pages as stationery, watermarks, bookmarks, compression and optimisation, AcroForm creation and field extraction, text and image extraction, raster rendering, encryption and digital signatures — and the licensing is by distribution volume rather than by developer seat. The reason this record exists at all is the notice on the product page: the vendor has stopped almost all sales of its developer kits, and the SDK is now available only to approved developers who apply.
Best for: Teams with an existing licence and a Windows deployment who need a PDF library they can embed without a server dependency, and who value the same engine as the editor their users already know. For anyone starting fresh the practical question is not which SDK is better but whether this one can be bought at all, which is why the sales notice is the first thing to read.
Worth knowing: The product page carries a notice that the vendor has stopped almost all sales of its developer kits and now offers them to approved developers on application. The practical effect is case-by-case sales approval rather than a closed door, and this record does not guess at the reason. The evaluation watermark is documented as evaluation output, not a free production tier: documents created or modified in evaluation mode carry a demo watermark and a licence string removes it. Core API, Editor SDK and Viewer SDK are separate products, and a rendering capability does not amount to a packaged viewer. The current pdf-xchange.com domain is the source rather than the tracker-software.com redirects, dated 2 October 2026.
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
- Website
- tracker-software.com
- Requires an account
- Not applicable
- Free tier
- Not verified
- Watermark on the free tier
- Yes
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Not verified
- Open source
- No
- Self-hostable
- Yes
- Licence
- Commercial, licensed by distribution volume: client desktop install tiers of 25K, 50K, 100K, 250K and 1 million are published as available, and sales of developer kits have stopped except by application
- Redaction
- No redaction feature
- Programmatic access
- Embeddable library
- Last availability check
- Responded in 627 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, and the absence is unusually well documented: the vendor's own feature matrix for the whole developer range lists 40-odd capabilities — page operations, merging, overlaying, watermarks, compression, AcroForm creation and extraction, text and image extraction, raster rendering, encryption, digital signatures and comment support — and **no row in it mentions redaction at any point**, for any of the six SDKs. What it does not establish: the matrix's per-SDK tick columns did not render as text, so this rests on the feature list rather than on reading the Core API SDK's own column, and the separate PDF-XChange Editor record has its own verdict on its own evidence. Also absent from that trace: whether content removal exists under another name the matrix does not use.
https://www.tracker-software.com/pdf-creation-and-manipulation-sdks-comparison-chart
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.
-
“Please note that PDF-XChange has now stopped almost all sales of software developer kits. Available to approved developers on application - please contact sales@pdf-xchange.com for further information.”
Checked by us — the source says this Read 22 September 2026
Present verbatim on the product page, immediately beneath the sentence describing what the SDK is, which is the most prominent position on the page. Recorded because it is the single fact that determines whether this record is actionable: the SDK is versioned, documented and demoable — current version 11.0.1.0 — while being closed to ordinary purchase. The page does not give a reason, a date, or a list of what "almost all" excludes, and none of those is inferred here. discontinued is left false because the product has not been discontinued: that field is for products that are gone, and the difference between "withdrawn from sale" and "discontinued" is exactly the kind of distinction this index exists to keep.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 5da0ee7bd1139043ba58a3610623d12c29a39230d19f45e4156b003f1548efd7
How we checked: https://www.tracker-software.com/product/pdf-xchange-core-api-sdk rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 2202 bytes) and the notice read from that rendered text. sourceHash is the SHA-256 of that text.
-
“Evaluation versions of our SDK software are fully functional, allowing the testing and full utilization of all SDK features, Developers need to be aware that any test documents will have a demo watermark placed on every page of any PDF created or modified with the evaluation versions”
Checked by us — the source says this Read 22 September 2026
Confirmed verbatim, and it is a more interesting limitation than a page cap. Nothing about the evaluation is reduced: every feature works, which means an evaluation can pass every functional test and still be unusable in production, because the watermark is applied to any PDF the build creates or modifies. The same page adds that the vendor "does not offer refunds subsequent to issuing licensing information", so the documented remedy is to test extensively before purchase and to recompile with a licence string afterwards — a build step that has to be planned for, not a setting. It sits in watchOutFor with the licence-string detail because a reader who discovers this after shipping has already shipped.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- aae533cb902b1b4804483d0c27ac68c896950948eae224706dc91ad57d69a4bc
How we checked: https://www.tracker-software.com/product/pdf-xchange-core-api-sdk/demo-limitations rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 2567 bytes); the claim was checked against that text, including the sentence about refunds that follows it. sourceHash is the SHA-256 of that text.
-
“PDF-XChange CORE API SDK V8 supports all Windows (32/64 bit) operating systems from Windows 10 and later”
Checked by us — the source says this Read 22 September 2026
Confirmed verbatim as the system requirements statement, and platforms is set to windows on its authority. The same session found the chart disagreeing with it: the chart's Windows Version Compatibility row reads "All 32/64 bit - XP & Later", which is a wider claim than Windows 10 and later and cannot be true of V8 as specified. One of the two is stale, and the version-specific page is the better authority for a current release, so the record follows it and records the contradiction rather than picking silently. The system requirements page also names versions V5 through V8 as Terminal Server compatible and V5, V6 and V7 as supporting XP and Vista, which is the version history behind the chart's older wording.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 08cf18afdf42168a1d7a4a1734cf9c6eea9fc02925a6e3d6acadf1c07efc1146
How we checked: https://www.tracker-software.com/product/pdf-xchange-core-api-sdk/system-requirements rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 2898 bytes) and cross-checked against the vendor's own comparison chart at https://www.tracker-software.com/pdf-creation-and-manipulation-sdks-comparison-chart (visible text 3882 bytes) in the same session. sourceHash is the SHA-256 of the system requirements text.
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
- Which PDF tools keep your file on your machine — what we count as processing on your own device.