This article describes the salient features of file conversion API using C#.
GroupDocs.Conversion main feature is the ability to convert any document from any of supported source document formats into any supported target format (check the list of supported formats). All these conversions are possible without any additional software installed (like Microsoft Office, Apache Open Office, Adobe Acrobat Reader and others).
GroupDocs.Conversion provides a flexible set of settings to customize the conversion process to fulfill your needs:
Convert specific document page(s)
Along with the whole document conversion to the desired target format, it could be useful to convert specific document pages or page ranges. For such partial document conversion, you should specify desired page numbers to convert using the Pages property of the ConvertOptions class.
Auto-detect source document format
In some cases, the source file could be presented in a form of a byte stream, so the file extension is unknown.
Luckily GroupDocs.Conversion for .NET is smart enough to detect source document format on the fly.
Load source document with extended options
There are lots of modifications that are possible during the file conversion process:
It is a common use case when a source document references some specific fonts that are not present in the environment where you launch your application. GroupDocs.Conversion for .NET provides a solution - you can substitute missing fonts with fonts of your choice that will preserve your document appearance.
Watermarking converted document
You can add a text or an image watermark to any page of the converted document and choose its desired dimensions, color and font size.
Document information extraction
GroupDocs.Conversion allows to obtain basic information about source document - file type, pages count etc. Dependent on the source file type some format-specific information can be extracted, for example:
CAD - list of layers and layouts in a CAD document;
GroupDocs.Conversion supports conversion result caching to local disk by default. However, any type of cache storage can be supported by implementing appropriate interfaces – Amazon S3, Dropbox, Google Drive, Windows Azure, Redis or any other.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.