Working with Presentations


Presentation documents are presented by many formats: PPT, PPTX, PPTM, PPS(X/M), POT(X/M) and others, which are supported by GroupDocs.Editor Cloud as a separate format family among all others. Same as for all other family formats, the Presentation family has its own load and saves options. There several steps that usage of GroupDocs.Editor Cloud consists of:

  1. Upload input document into cloud storage
  2. Load the document into editable representation in the cloud storage (HTML file and resources)
  3. Download HTML document (and resources, if needed) from storage
  4. Edit HTML document at client side
  5. Upload HTML document back into the storage
  6. Save the edited document into Spreadsheet format in the storage
  7. Download saved document

Steps 1, 3, 4, 5 are storage operations, please refer to this Storage Operations) for usage details. Step 4 is a custom edit operation that can be performed with the programming language or 3rd party tools.

Below is a detailed description of steps 2 and 6.

Loading Presentations Documents

This REST API provides an ability to load the input documents into an editable representation.


HTTP POST ~/load

Swagger UI lets you call this REST API directly from the browser. The following properties of loading Presentation documents may be customized:

FileInfo.FilePathThe file path in the storageRequired property
FileInfo.StorageNameStorage nameCould be omitted for default storage
FileInfo.VersionIdFile version IdUseful for storages that support file versioning
FileInfo.PasswordThe password to open fileShould be specified only for password-protected documents
OutputPathThe full output pathThe directory in storage, where editable files will be stored
SlideNumberAllows to specify the slide number, which should be opened for editingRequired
ShowHiddenSlidesSpecifies whether the hidden slides should be included or not. Default is false

cURL Example

* First get JSON Web Token
* Please get your Client Id and Client Secret from Kindly place Client Id in "client_id" and Client Secret in "client_secret" argument.
curl -v "" \
-d "grant_type=client_credentials&client_id=xxxx&client_secret=xxxx" \
-H "Content-Type: application/x-www-form-urlencoded" \
-H "Accept: application/json"

* cURL example to load document
curl -v "" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer
<jwt token>"
-d "{
    'FileInfo': { 'FilePath': 'Presentation/sample.pptx' },
  'OutputPath': 'Output',
  'SlideNumber': 0
* Response will contain storage path to resultant documents
  "resourcesPath": "output\sample.files",
  "htmlPath": "output\sample.html"


Using an SDK (API client) is the quickest way for a developer to speed up the development. An SDK takes care of a lot of low-level details of making requests and handling responses and lets you focus on writing code specific to your particular project. Check out our GitHub repository for a complete list of GroupDocs.Editor Cloud SDKs along with working examples, to get you started in no time. Please check the article to learn how to add an SDK to your project.

Working with Presentations Examples