Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
During MHTML-to-PDF conversion, Aspose.HTML for Java renders supported image attachments as additional PDF pages. The attachments appear after the pages generated from the main HTML content and retain their order from the MHTML document.
MHTML documents may contain image attachments in addition to the HTML content that is displayed by a browser. These attachments are stored within the MHTML document but are not necessarily referenced by the main HTML page. During MHTML-to-PDF conversion, Aspose.HTML for Java detects such image attachments and includes them in the generated PDF as additional pages.
Currently, the following image formats are supported:
If an MHTML document contains multiple supported image attachments, all of them are rendered. There is no predefined limit on the number of attachments that can be processed. Each supported attachment is added as a separate page after the pages generated from the main HTML content.
Attachments are rendered in the order in which they appear in the MHTML document. This order is preserved in the generated PDF.
Attachment rendering is currently automatic. There is no option to disable it, limit the number of rendered attachments, or choose specific attachments to include in the output.
As a result, every supported image attachment contained in the MHTML document is rendered, even if it is not required for a particular scenario. Documents with a large number of attachments or high-resolution images may therefore require additional processing time, consume more memory during conversion, and produce larger PDF files.
No. Supported image attachments are rendered as additional PDF pages; they are not added as downloadable file attachments inside the PDF.
No. Attachment rendering is automatic, and the current Java API does not provide an option to disable it, limit the number of rendered attachments, or select individual attachments.
PdfSaveOptions.Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.