Supported Document Formats Leave feedback

The following tables contain the file formats supported by GroupDocs.Assembly for Python via .NET. A template of any of these formats can be loaded and filled with data. The report is saved in the format of its file extension, or of the format named by LoadSaveOptions(FileFormat....); which report formats a template can be saved to depends on its family, as the last table shows.

The package runs the same engine on every platform, so the tables below hold on Windows, Linux and macOS, with these exceptions:

• Presentations on Linux and macOS need libgdiplus. Without it no presentation template (PPT, PPTX, ODP and the others) can be filled: the call raises “The type initializer for ‘Gdip’ threw an exception”. Word processing, spreadsheet, email, HTML and text templates do not need it. See System Requirements.
• On Linux, a presentation cannot be saved as TIFF (“Not implemented”); save it as PDF instead.
• Text and HTML templates should start with a UTF-8 byte order mark. A text or HTML template without one, that holds only ASCII characters, is read as an ANSI document, and the report is written in the Windows-1252 code page on every platform: “Café” becomes a single byte that a UTF-8 reader cannot show. With the mark the report is UTF-8. The sample templates of this documentation have it.

Each template family can be saved to the formats below. Saving to another format raises an error (“The document cannot be saved to the given format”).

An MHTML template can also be saved as an email message (MSG, EML). An EML template whose message has only a plain-text body loses that text when it is saved to HTML, Markdown, plain text, XPS, OXPS, XAML, EPUB or DOCX; save it as an email, MHTML or PDF instead. A Markdown template saved as MHTML loses its text too; save it as HTML instead.

Can’t find your file format? Please post a request on our Free Support Forum, and our team will assist you.