Skip to content

Conversion capabilities overview ​

This section summarizes the main conversion capabilities of Foxit PDF SDK (desktop/server), grouped by whether an additional conversion engine must be deployed.

For the standalone Foxit Conversion SDK product (PDF ↔ Office / Markdown), see Foxit Conversion SDK overview.

Engine-backed conversion ​

Requires a third-party Office install, or a Foxit conversion engine / engine directory (for example HTML, DWG, or the standalone Conversion SDK library).

Engine / libraryAPI moduleDescriptionPlatformsDocs
Foxit Conversion SDKOFFICE2PDF
PDF2OFFICE
PDF2MD
MD2PDF
Bidirectional PDF ↔ Office (.docx, .xlsx, .pptx); PDF ↔ MarkdownWindows / LinuxOffice→PDF, PDF→Office, Markdown
Microsoft Office → PDFconversionWord, Excel, PowerPoint → PDF; requires Microsoft Office (e_Office2PdfEngineMicrosoft)WindowsOffice to PDF
LibreOffice → PDFconversionWord, Excel, PowerPoint → PDF; requires LibreOfficeLinux (x86 / x86_64)Office to PDF
WPS → PDFconversionWord, Excel, PowerPoint → PDF; requires WPS (Windows: e_Office2PdfEngineWps; Linux armv8 via engine path)Windows; Linux armv8Office to PDF
Web/HTML → PDFconversionFoxit engine; HTML from file, string, or URL → PDF with page size and format controlWindows / Linux / MacHTML to PDF
DWG → PDFconversionDWG → PDF; 2D drawings onlyWindows / Linux / MacDWG to PDF

Built-in Convert APIs ​

Use Convert without deploying Office / HTML / DWG engines. Details and samples: Image / text / XML conversion.

CapabilityAPINotesDocs
Image → PDFConvert::FromImageCommon bitmaps → PDFImage → PDF
TXT → PDFConvert::FromTXTPlain text → PDF (TXT2PDFSettingData)TXT → PDF
PDF → XMLConvert::ToXMLStructured XML export; optional force-tagPDF → XML

PDF page ↔ image import/export via rendering (not Convert::FromImage) is documented under Image conversion.

Rendering pages to PDF or PostScript via print-device settings is provided by the render module (Renderer and PrintDeviceSettingData), not the Conversion module. See Print to PDF / PostScript.