Will the viewer work with really large docx files. My client can have documents with over 200 pages and lots of tables. Thanks!
Thanks for taking interest in GroupDocs.Viewer.
Yes, GroupDocs.Viewer has the ability to render the large documents without any limitation on the number of pages. In case you would have any other questions or queries, please feel free to let us know.
I have a similar question with regards to large files.
What are the performance implications of rendering a preview for very large documents (up to 500Mb – typically scanned Docx/Pdf/Tiff)?
Is the viewer going to try and load the entire file into the server’s memory when processing a preview?
What’s the viewer’s response time for large documents (how soon will the user see the first page of a 500MB document)?
Could the viewer be configured to allow incremental loading of document content (pages are loaded only if/when the user attempts to view them)?
Thanks for your inquiry.
The performance of the API and the document rendering time, as well as resource consumption, depends on multiple factors such as document’s content which can include text, images, tables; the number of resources that application can use; server specification and so on. There are no limitations on the size of the document to be rendered, however, rendering of the larger document may take more time than rendering a smaller one.
Yes, GroupDocs.Viewer first loads the complete document and then renders it to get the HTML or image representation of its pages. To get information about the document processing time of the API, please have a look at the performance profile.
Yes, you can implement the incremental loading of the pages using page by page rendering. GroupDocs.Viewer allows rendering a single page or a range of the pages. This feature helps to render only the desired/requested page of the document.
In case you would have any other question, please feel free to let us know.