Conversion API - Convert files with Cloud SDKs and REST API
Aspose.HTML Cloud v4.0 provides the simplest API to convert HTML files to one of the fixed-layout document formats including PDF, XPS and DOC, DOCX; to raster image formats including JPEG, PNG, TIFF, BMP, and GIF; to MD and MHTML formats. You can convert the HTML document to any supported formats either from the storage by its name or from the web by its URL.
In this documentation chapter, also you find out in detail how to convert EPUB, XHTML, MHTML, MD and SVG files to the most popular formats by calling directly the REST API by HTTP requests or using a set of SDKs. Convert HTML, XHTML, MHTML, EPUB, MD and SVG formats with our powerful file conversion API!
- HTML Converter - the article provides information about various scenarios for converting HTML files to other popular formats, including PDF, XPS, DOCX, JPEG, PNG, TIFF, BMP, GIF, Markdown, and MHTML.
- EPUB Converter you find out how to convert EPUB files to different formats including PDF, XPS, DOCX, JPEG, PNG, TIFF, BMP, and GIF.
- SDK Conversion Options - you will learn how to apply conversion options to convert HTML to PDF, XPS, and Images with a set of SDK examples.
The main differences from conversion API v3.0 are:
- conversion is considered as potentially long time operation, so new API provides an asynchronous mode of conversion;
- many options that were available in conversion API v3.0 have been reduced to only three possible REST API calls; this makes development more straightforward.
SDK vs REST API
The application developer can use Aspose.HTML Cloud v4.0 conversion functionality calling directly the REST API by HTTP requests or using a set of SDKs.
- SDK is a preferable choice for faster development; the SDKs provide a convenient set of methods for the most typical cases and hide many routine operations from a developer. SDKs are available in Java, Python, PHP, Perl, Android, Swift, Node.js, C#, and more.
- REST API is a low-level interface to work directly with the Aspose.HTML Cloud product service by HTTP requests. It provides full control over the HTTP operation results, but it requires more routine work to prepare HTTP requests and handle responses.