Syncfusion WinForms DocX to PDF Conversion – Layout Rendering Mismatch
We used Syncfusion Winforms c# Version 30.146.38. Docx convert to PDF Not rendering Properly
Title:
DocX to PDF Conversion Produces Incorrect Layout Rendering
Description:
When converting a Microsoft Word document (.docx) to PDF using Syncfusion WinForms Version 30.146.38, the resulting PDF does not preserve the original document layout. The converted output differs significantly in formatting, structure, and positioning of elements compared to the source .docx file.
Code
using DocToPDFConverter converter = new DocToPDFConverter();
converter.Settings.EmbedFonts = true;
converter.Settings.EmbedCompleteFonts = true;
using (var pdfDoc = converter.ConvertToPDF("MappedTablesNormalizedNrm.docx"))
{
//Save and close the document
FileStream outputStream = new
FileStream("MappedTablesNormalizedNrm.pdf", FileMode.Create,
FileAccess.ReadWrite, FileShare.ReadWrite);
pdfDoc.Save(outputStream);
converter.Dispose();
pdfDoc.Close();
outputStream.Flush();
outputStream.Dispose();
}
Attachment: Attached_5233586c.zip
Hi VijayMohan,
We have reproduced
the reported issue “Table column width is not preserved properly during Word
to PDF conversion” in our end. We will validate this issue and update you
with more details on August 6, 2026.
Regards,
Althaf.
Hi VijayMohan,
We have confirmed that the reported issue with “Autofit table grid columns are calculated improperly while converting a Word document to PDF” is a defect and we have logged a defect report. We will include the fix for this defect in our weekly NuGet release, which is estimated to be available on 25th August 2026.
The status of this bug can be tracked through the below link:
Autofit table grid columns are calculated improperly while converting a Word document to PDF in WinForms | Feedback Portal
Disclaimer: Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.
Regards,
Sushma.
Hi VijayMohan,
Due to a testing failure, this fix could not be included in this week's NuGet
release. We are currently working on resolving the issue. The fix will be
included in our upcoming weekly NuGet release, scheduled for September 1,
2026, without any further delay. We appreciate your patience and
understanding.
Regards,
Sushma.
- 3 Replies
- 3 Participants
-
VI vijaymohan
- Aug 4, 2026 09:45 AM UTC
- Aug 25, 2026 10:12 AM UTC