Converting Word document to PDF does not render correctly

Aspose.Words Product Family
1

Please find attached the word document that does not render correctly when converted to PDF. Some of the pages are not rendered correctly and new page is added at the end.

Input Word file
Employee evaluation form - 5 page.docx (679.7 KB)

Output PDF file
Employee evaluation form - 5 page - converted.pdf (303.7 KB)

2

@nfrancis

You mentioned that converting Employee evaluation form – 5 page.docx to PDF skips some pages and adds a blank page at the end [1].

Steps to try

  1. Update Aspose.Words – A rendering issue was fixed in Aspose.Words for .NET 24.7 (issue WORDSNET‑27093) [3]. Updating to version 24.7 or a later release may resolve missing‑content or extra‑page problems.

  2. Save with explicit PDF options – Use PdfSaveOptions to preserve the original layout and images:

    var doc = new Aspose.Words.Document("Employee evaluation form - 5 page.docx");

var pdfOptions = new Aspose.Words.Saving.PdfSaveOptions
{
    OptimizeOutput = true,
    ImageCompression = Aspose.Words.Saving.PdfImageCompression.Auto,
    DownsampleOptions = new Aspose.Words.Saving.DownsampleOptions
    {
        DownsampleImages = false // keep vector graphics and image resolution
    }
};

doc.Save("Employee evaluation form - 5 page - converted.pdf", pdfOptions);

    This configuration disables down‑sampling and keeps vector graphics, which can help avoid missing pages and the extra blank page [2].

  3. Check the source DOCX – Open the document in Microsoft Word and verify that all pages appear correctly and that there are no hidden section or page breaks.

  4. If the issue remains –

    • Confirm the exact Aspose.Words version you are using.
    • Provide a minimal reproducible sample (code snippet and the DOCX) so the problem can be examined further.

These actions—updating to a recent version and saving with the shown PdfSaveOptions—are common ways to address rendering defects observed during DOCX‑to‑PDF conversion.

3

@nfrancis The problem is not reproducible on my side. Most likely the problem on your side occurs because fonts used in your source document are not available in the environment where document is converted to PDF. The fonts are required to build document layout. If Aspose.Words cannot find the font used in the document, the font is substituted . This might lead into fonts mismatch and document layout differences due to the different fonts metrics. You can implement IWarningCallback to get notifications when font substitution is performed.
Please see our documentation to learn where Aspose.Words looks for fonts:
https://docs.aspose.com/words/net/specifying-truetype-fonts-location/
https://docs.aspose.com/words/net/installing-truetype-fonts-on-linux/