How to resolve the issue of iFrame, Embed, and Object entities being automatically removed?

The version of Google Chrome releasing on 8 January 2025 removes headless functionality. If you’re using Nutrient Document Converter (formerly Muhimbi PDF Converter) or Nutrient Document Converter Services (formerly Muhimbi PDF Converter Services) on-premises applications, configured to use Chrome, this may have an impact on your HTML-to-PDF conversions. To resolve this, switch to Blink Binaries or Chrome headless shell.

If your conversions rely on iFrame, Embed, and Object entities and you’re confident about their safe use, it’s possible to configure the document conversion process to keep them.

<!-- Remove the following (potentially malicious) nodes from any HTML file converted.
     * Comma-separated list of HTML tags (for example, "iframe, embed, object"). All objects with the listed tag names will be removed even if they were dynamically created.
     * Leave empty for default behavior. The HTML source will not be modified. -->
<add key="HTMLConverterFullFidelity.RemoveNodes" value="iframe,embed,object"/>

This feature is only available when Chromium HTML engine is used. Furthermore, the feature isn’t available for Windows Server 2008 R2 and Windows Server 2012 R2 when a URL is converted, but it is available when a string is converted.