Skip to main content
Upload source files before generation when the deck must use documents, spreadsheets, presentations, or images. Keep returned identifiers and use them only with the deployment that created them.

​
Choose the content path

​
Cloud

Cloud v3 provides file upload, uploaded-image management, generation from documents, and generation from structured JSON. Managed storage and processing limits apply.

Generate from documents

Upload source material and reference it during generation.

Generate from JSON

Build a presentation from structured slide content.

Cloud file-upload endpoint

Inspect the multipart request and response.

Cloud image endpoints

List uploaded assets, then open the upload or delete operation from the reference sidebar.

​
Self-hosted

Self-hosted v1 provides file and image upload routes used by the generation endpoints. Supported formats and file persistence depend on the release and /app_data configuration.

Document processing

Review storage paths, parsing behavior, limits, and persistence.

Open Source file-upload endpoint

Inspect the multipart request and response.

Open Source image endpoints

List local uploaded assets, then open the upload or delete operation from the reference sidebar.

​
Operational rules

  • Upload and generate with the same deployment, account, and credentials.
  • Preserve returned file values exactly; do not derive storage paths.
  • Treat uploaded content as sensitive and avoid logging request bodies.
  • Verify factual claims and calculations in the generated deck against the source.
  • Use the endpoint reference for supported media types, multipart fields, limits, and response schemas.

See both deployment-specific file flows

Open the Cloud or Open Source tab and follow its numbered source-file sequence.