Word to PDF Table Formatting Broken: Causes and Fixes

Different symptoms point to different root causes, and the fix for each is different. Before you start making changes, identify exactly what went wrong in the converted PDF by opening it and systematically checking the table against the original Word document. Missing or inconsistent borders usually trace back to how Word stores border definitions — particularly the difference between paragraph borders and table borders, and whether the conversion tool reads both correctly. Column width shifts and text overflow are almost always caused by font substitution or page margin differences during conversion. Cell merging or reflow issues typically come from complex merged cells, split cells, or nested tables that the conversion engine struggled to interpret. Having a clear diagnosis prevents you from making unnecessary changes. If your problem is only border rendering, you do not need to rebuild the entire table — you just need to fix how borders are defined.

1. 1Step 1 — Open both documents side by side. View the Word original at 100% zoom and the converted PDF at the same scale. Identify every specific discrepancy: which borders are missing, which columns shifted, which cells overflowed. Take notes or screenshots for each problem.
2. 2Step 2 — Check the page setup in Word before converting. Go to Layout > Page Setup and note the exact margins, page size, and orientation. Then open the PDF and check the same in its document properties. If they differ, the conversion tool may have used different page dimensions, which causes column width recalculations.
3. 3Step 3 — Check whether the table uses custom fonts. Go to the Table Design tab in Word and look at whether the table cells use a non-standard font. If that font is not embedded in the PDF or available on the conversion system, the PDF renderer substitutes a different font with different character metrics, causing text to reflow and overflow cells.
4. 4Step 4 — Look for nested tables or complex merged cells in the Word document. These are the most common sources of cell-merging artifacts in converted PDFs. In Word, click inside any problem cell and check whether it is part of a nested table (Table > Select > Table will show you the bounds of the innermost table).
5. 5Step 5 — Try a different conversion method. If you are using Print to PDF (the Windows virtual printer), try instead using Word's built-in Save As PDF (File > Save As > PDF). These use different rendering engines and often produce different results. If one approach corrupts tables, the other may preserve them correctly.

Borders disappearing in PDF conversion is one of the most common table problems and fortunately one of the most fixable. The root cause is almost always how the borders are defined in the Word document. Word has two overlapping systems for rendering table borders: the table's own border properties (accessed via Table Design or Table Properties > Borders and Shading) and paragraph-level borders applied to individual cells. When these two systems conflict, or when a conversion tool reads one but ignores the other, borders that appear in Word do not appear in the PDF. The most reliable fix is to consolidate all borders using the Borders and Shading dialog rather than relying on Word's visual table design controls. Select the entire table (click the table move handle in the top-left corner), then go to Table Design > Borders > Borders and Shading. In the dialog, explicitly set the border style, width, and colour for inside and outside borders. Apply and convert again. Also check whether the borders use a very light colour that looks fine on screen but does not survive conversion. Borders set to a grey that is too light — particularly anything below 20% black — may render as invisible in PDF output depending on the conversion engine's colour handling. Switch to solid black (100%) for critical table borders and see if that resolves the issue. Another common source of the problem is 'No Border' cells mixed with bordered cells. If some cells explicitly have no border while adjacent cells do, the rendering can look correct in Word (where zero-width borders have a visual hint) but incorrect in PDF (where they simply do not exist).

When columns in a converted PDF are narrower than in the original Word document — causing text to wrap unexpectedly or overflow cell boundaries — the problem is almost always one of two things: font substitution or page margin mismatch. Font substitution occurs when a font used in the Word document is not available to the PDF conversion engine. The engine falls back to a substitute font (often Times New Roman or Arial) that has different character widths. Even small differences in character width compound across a full cell of text and across columns, shifting the entire table layout. The fix is to embed the fonts or use universally available fonts. In Word, go to File > Options > Save and check 'Embed fonts in the file'. This ensures the fonts travel with the document and are available to the conversion engine. Page margin mismatch is simpler to diagnose and fix. If the Word document uses custom margins (say, 1.5 cm on each side) but the PDF conversion tool defaults to standard margins, the printable width changes. Tables set to 100% of the available width will recalculate their column widths accordingly, and columns that fit before will not fit after. Check your margins before converting and make sure they are explicitly set in the PDF output settings if your conversion tool supports this. For tables with fixed-width columns (set in inches or centimetres rather than percentages), margin mismatches cause the table to extend beyond the page edge rather than reflow — resulting in the right columns being clipped. You can verify this by scrolling to the right in the PDF viewer; if the clipped content is there but off-page, the margin settings are the culprit.

The most effective fix for Word-to-PDF table problems is prevention. A handful of table design habits make documents convert reliably and remove the need for post-conversion corrections. First, use percentage-based column widths rather than absolute measurements when the document will be converted on different systems. Absolute pixel or centimetre widths assume a specific page size and margin; percentage widths adapt correctly if those settings shift during conversion. Second, avoid nested tables whenever possible. A table inside a table cell is a frequent source of conversion errors across all tools. If you need complex multi-level data organisation, consider using cell merging and splitting to achieve the same visual result within a single table structure. Third, use only universally available fonts for table content, or explicitly embed fonts before conversion. Stick to fonts like Arial, Calibri, Times New Roman, or Georgia for any document that will be converted to PDF through an automated process. These fonts are available on virtually every system and will not trigger substitution. Fourth, use Word's built-in Save As PDF rather than Print to PDF. The Save As PDF path uses the same layout engine as the screen renderer, which gives more accurate results for complex table layouts. Print to PDF uses a virtual printer driver that introduces additional variability. Finally, after converting, always do a quick visual check of every table in the output PDF before sending it. A 30-second review catches problems that would be embarrassing to have a client or colleague notice first.