On this page
Use the conversion-host font report
DOCX declares font families in document, style and font-table parts. Nexynto compares those declarations with family labels reported by the conversion host without exposing server file paths.
A likely substitution is a review warning, not proof of failure. Theme fonts, embedded subsets and renderer mappings can still influence the final choice.
Keep suitable source images
Word may store original image data while displaying a cropped or scaled view. Avoid repeated recompression before conversion, and check floating-image anchors near page and section breaks.
The fidelity profile does not enable optional image downsampling. The Office renderer controls the final PDF representation.
Design tables for the source page
Tables wider than the section content area can reflow, clip or push rows to another page. Review nested tables, merged cells, repeated header rows and row-splitting behavior in Word first.
The converter renders tables through the Office engine rather than reconstructing them manually. Analysis reports table count for review and quality assurance.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Word to PDFFrequently asked questions
Clear answers before you merge
Does font detection expose server paths?
No. Only normalized family labels and readiness classifications are returned.
Are images downsampled?
No optional optimization is enabled in the fidelity-first profile.
Can a table row move to another page?
Yes. Page width, font metrics and row-splitting settings can change pagination.