IronPdfEngine Version Mismatch and 2026.11.1 Output Changes
When the IronPDF client and the IronPdfEngine image run different versions, the client logs a warning and keeps working, so output can shift without an error being raised.
[Warning] Invalid IronPdfEngine version (Server: 2026.11.1) (This client: 2026.10.3)
The client logs that warning whenever the engine reports a different version, whichever side is newer. It often appears with :latest, when a restart or a new node pulls a newer engine than the application's client. Separately, 2026.11.1 changes some PDF output on every engine: PDF/A-1 output replaces embedded sRGB ICC v4 colour profiles with the equivalent v2 profile (only sRGB v4 profiles are affected), and PDF/UA-2 output writes the pdfuaid:rev value 2024 instead of 2020. Colours and validation results stay the same, but byte-for-byte comparisons against older files fail.
In 2026.11.1 the default tags :<version> and :latest still use Chromium 109, so changed output on a default tag comes from a version mismatch or from the PDF-side changes above, not from a new browser engine.
Solution
1. Pin the engine image to your client version
Match the engine image tag to the same version as your IronPDF client.
Docker:
docker pull ironsoftwareofficial/ironpdfengine:<version>
Docker Compose:
services:
ironpdfengine:
image: ironsoftwareofficial/ironpdfengine:<version>
ports:
- "127.0.0.1:33350:33350"
For a fully reproducible build, pin the image digest instead: ironsoftwareofficial/ironpdfengine@sha256:<digest>.
2. Upgrade the client and engine together
From now on, upgrade the client package and the engine tag in the same step.
3. Confirm which engine the image contains
Read the image labels and the first log line to see which engine and Chromium build you have:
docker inspect -f '{{ index .Config.Labels "com.ironsoftware.ironpdfengine.engine" }} {{ index .Config.Labels "com.ironsoftware.chromium" }}' ironsoftwareofficial/ironpdfengine:<tag>
docker logs <container> 2>&1 | head -1
default means Chromium 109 and updatedchrome means Chromium 146. On a default tag, the first log line reads:
IronPdfEngine Chromium engine: default (Chromium 109.0.5414.120, CEF 109.1.18+gf1c41e4)
Images older than 2026.11.1 carry no labels and are all Chromium 109.
4. Re-baseline PDF/A-1 and PDF/UA-2 comparisons
If your tests compare PDF/A-1 or PDF/UA-2 files byte for byte, regenerate the expected files with 2026.11.1 and confirm compliance with a PDF/A or PDF/UA validator rather than a byte comparison. The same change applies to the in-process default IronPdf package.
5. Opt into Chromium 146 deliberately
Choose Chromium 146 on purpose with :<version>-updatedchrome, and test your documents first, since output on that engine differs from Chromium 109.
References
- Using IronPdfEngine with Docker
- About IronPdfEngine
- Output PDF from IronPdfEngine Docker not as expected
Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.