Skip to main content
Skip table of contents

Release pdfHTML 6.3.1

Release date: Jan 8th 2026

pdfHTML is an iText Core add-on for Java and .NET to create PDF from HTML/XML (and associated CSS).

As well as updates to maintain compatibility with the iText Core 9.5.0 dependencies, this release includes several bug fixes.

Bug Fixes

An issue was resolved with inconsistent handling of inline elements when converting HTML tables with the page-break-inside: avoid CSS property.

A couple of NullPointerException errors when converting ordered lists were fixed. In the first, an NPE could occur when a list contained a non-standard attribute, instead of defaulting to a standard list type. The second issue related to converting an ordered list with a “circle” attribute type.

An issue where a specific layout issue would cause an infinite layout loop was fixed. In the reported issue this occurred with a list item inside a keep-together container that split across pages, and when the surrounding divs height would range between 960–970px. This was due to an interaction problem between the behavior of the layout renderers.

In addition, an issue where the font size property would be ignored if the HTML element had a size of 0 was resolved.

Finally, a regression in pdfHTML versions after 6.0.0 with Japanese charset detection was fixed by changing how characters are converted to bytes.

Downloads

Changelog

Bug Fixes

  • DEVSIX-5263 – Improved handling of page-break-inside: avoid on tables.

  • DEVSIX-9586 – Fix infinite pagination loop for lists inside keep‑together.

  • DEVSIX-9452 – Handle unsupported <ol type> values gracefully.

  • DEVSIX-6128 – NPE when converting OL with attribute type="circle"

  • DEVSIX-9584 – Fix charset detection for Shift_JIS <meta> tags.

eBooks

Converting HTML to PDF with pdfHTML

Installation Instructions

Examples (latest ones)

FAQ (latest ones)

Chapter 7: Frequently Asked Questions about pdfHTML

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.