File type support
Document Engine supports importing documents in different file formats:
-
PDFs (available for all licenses)
-
Image documents (JPEG, PNG, TIFF etc. — requires a specific license component)
-
Office files (Word, Excel, PowerPoint etc. — requires a specific license component)
-
HTML files (including associated assets such as images, CSS, and web fonts — requires a specific license component)
-
Email files (EML, MSG — requires a specific license component)
-
CAD files (DWG, DXF — requires a specific license component)
The following table shows the allowed file extensions, their MIME types, and the expected Document Engine license.
| File extension | MIME type | Required license |
|---|---|---|
| application/pdf | Any | |
| HTML | text/html | HTML conversion |
| DOC | application/msword | Office files |
| DOCX | application/vnd.openxmlformats-officedocument.wordprocessingml.document | Office files |
| XLS | application/vnd.ms-excel | Office files |
| XLSX | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet | Office files |
| XLSM** | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet | Office files |
| PPT, PPS | application/vnd.ms-powerpoint | Office files |
| PPTX | application/vnd.openxmlformats-officedocument.presentationml.presentation | Office files |
| PPSX | application/vnd.openxmlformats-officedocument.presentationml.slideshow | Office files |
| RTF | application/rtf | Office files |
| ODT | application/vnd.oasis.opendocument.text | Office files |
| BMP | image/bmp | Image conversion |
| JPG/JPEG | image/jpeg | Image conversion |
| PNG | image/png | Image conversion |
| TIFF | image/tiff | Image conversion |
| HEIC | image/heic | Image conversion |
| GIF | image/gif | Image conversion |
| WEBP | image/webp | Image conversion |
| SVG | image/svg+xml | Image conversion |
| TGA | image/x-tga | Image conversion |
| EPS | image/postscript | Image conversion |
| EML | message/rfc822 | Email conversion |
| MSG | application/vnd.ms-outlook | Email conversion |
| DWG | image/vnd.dwg | CAD conversion |
| DXF | image/vnd.dxf | CAD conversion |
**To convert an XLSM file to PDF using Document Engine, refer to the documentation.
Currently, PostScript implementation is experimental.
You can create a document in any of the supported file formats and then use the functionality of both Web API and Document Engine API.
For example, you can create a document starting with an Office file, add some form fields to it, and then digitally sign it.
To guarantee compatibility with all features included in Nutrient Web SDK and Document Engine, it’s only possible to export a document in PDF format. However, you can download the originally uploaded file via the PDF download API endpoint using the source=true query string parameter.
For instructions on how to upload documents in one of the supported formats, refer to the API reference.
Conversion on mobile clients
If you’re also using Nutrient Android SDK or Nutrient iOS SDK, you can use your running Document Engine instance to convert Office documents for use in your mobile application. This works by allowing the mobile application to upload Office files to your server and then downloading the converted PDF file. To use this, your mobile application needs to provide a JSON Web Token (JWT) as described here. For more information, check out our Android and iOS guides.
When using this, keep in mind the performance considerations outlined below, as every request will result in a conversion process being started since there’s no caching involved.
Performance considerations
To operate on an Office file, Document Engine needs to convert the file to a PDF during the document import process. For documents created by uploading a file and documents with a remote URL, conversion happens completely transparently.
No matter the document source, Document Engine will store the PDF counterpart of the original file in its configured asset storage. This is particularly relevant if you plan to use documents with remote URLs that point to Microsoft Office files.
Depending on the size and complexity of the file, the conversion from Office to PDF can use a significant amount of CPU and memory. We recommend testing your setup with a wide range of documents and using the monitoring facilities offered by your deployment solution to make sure the load is compatible with your current infrastructure.