How to Convert HTML to Word in C#

a. Use a CSS style “page-break-before: always” in your HTML source. For example:

public void GenerateMultiPageReport()
{
    Document doc = new Document();
    Section section = doc.AddSection();

    // We use a CSS style 'page-break-after:always' 
    // This inserts a physical page break in Word
    string htmlContent = @"
        <html>
            <h1>Page 1</h1>
            <p>This content is on the first page.</p>
            <br style="page-break-before: always" />
            <h1>Page 2</h1>
            <p>This content starts on a fresh page!</p>
        </html>";

    section.AddParagraph().AppendHTML(htmlContent);
    doc.SaveToFile("MultiPageReport.docx", FileFormat.Docx2013);
}

b. Manually insert page breaks after adding the HTML using the library’s AppendBreak method:

doc.Sections[0].Paragraphs[1].AppendBreak(BreakType.PageBreak);

4.2 Adding Professional Touches: Headers, Footers, and Page Numbers

To make the output look like a formal report rather than a simple print-out, you can add headers and footers programmatically. You need to handle this via the C# API rather than the HTML string itself.

// Add a header
HeaderFooter header = section.HeadersFooters.Header;
Paragraph headerPara = header.AddParagraph();
// Format the header (e.g., right-aligned)
headerPara.Format.HorizontalAlignment = HorizontalAlignment.Right;
headerPara.AppendText("Internal Project Report");

// Add a Footer with Dynamic Page Numbers
HeaderFooter footer = section.HeadersFooters.Footer;
Paragraph footerPara = footer.AddParagraph();
footerPara.Format.HorizontalAlignment = HorizontalAlignment.Center;
footerPara.AppendText("Page ");
footerPara.AppendField("page", FieldType.FieldPage); // Current page
footerPara.AppendText(" of ");
footerPara.AppendField("numPages", FieldType.FieldNumPages); // Total pages

5. Key Considerations

When converting HTML to Word, remember that Word is not a web browser. Word’s rendering engine is closer to an old version of Internet Explorer than a modern browser. HTML content looks good in a browser, but may not look the same in Word. Addressing these areas can prevent rendering errors:

5.1 Fixing Image Path Issues

In HTML, images often use relative paths like <img src="logo.png">. When the conversion runs, the library might not know where that file is. The most reliable fix is to resolve the absolute path before passing the HTML to the library.

// Define your base directory (e.g., your project's assets folder)
string baseDirectory = AppDomain.CurrentDomain.BaseDirectory;
string fullImagePath = Path.Combine(baseDirectory, "assets", "logo.png");

// Replace the relative path with a full local path so the library can find it
string finalHtml = htmlString.Replace("logo.png", fullImagePath);

5.2 Managing Fonts and Consistency

Word will render a font correctly only if it is installed on the machine opening the document. For maximum compatibility, stick to "Web Safe" fonts like Arial, Times New Roman, or Calibri.

If your branding requires specific non-standard fonts, you can embed them directly into the document. Note that this will increase the final file size.

// Enable font embedding for cross-platform consistency
document.EmbedFontsInFile = true;
// Manually add a private font to the document's font list
document.PrivateFontList.Add(new PrivateFontPath("CustomFont", @"C:\Fonts\CustomFont.ttf"));

5.3 Compatibility Rules

To ensure your layout doesn't break, follow these rules:

• Avoid Modern Layouts: Word does not support CSS Flexbox or Grid. For side-by-side content or complex alignments, use standard HTML <table> elements. They are the most stable way to manage structure in Word.

• Better to Use Inline Styles: While external stylesheets are sometimes supported, Word may ignore complex CSS selectors. For critical formatting (like background colors or specific widths), use inline styles: <td style="background-color: #f2f2f2;">.

• Stick to Basic Tags: Modern semantic tags like <nav>, <article>, or <section> are often ignored or stripped. Stick to the "classics": <p>, <h1>–<h6>, <table>, and <img>.

• No Interactivity: Remember that JavaScript, buttons, and video elements will be stripped out or rendered as static, non-functional placeholders.

Conclusion

Converting HTML to Word in C# is a practical solution for turning web content into editable, professional documents. This article explored how to handle both static HTML files and dynamic HTML strings, manage layout elements like page breaks, and enhance reports with headers, footers, and page numbers. By applying these techniques, you can streamline document generation and ensure your Word outputs accurately reflect the original HTML content.

Just remember: always validate the output with your real HTML content to ensure the final Word document matches your expectations.