> ## Documentation Index
> Fetch the complete documentation index at: https://docs.presenton.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Files and content

> Upload files, manage images, and generate presentations from source 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

| Input                 | Use it when                                              | Workflow                                     |
| --------------------- | -------------------------------------------------------- | -------------------------------------------- |
| Prompt                | The model can create the narrative from instructions     | Generate directly                            |
| Uploaded documents    | Claims and structure must be grounded in source material | Upload files → generate with returned values |
| Uploaded images       | The application supplies approved visual assets          | Upload image → reference or manage the asset |
| Structured slide data | The application owns exact layout-compatible content     | Inspect schema → validate → create from JSON |

## Cloud

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

<CardGroup cols={2}>
  <Card title="Generate from documents" icon="file-arrow-up" href="/cloud/guides/generate-from-documents">
    Upload source material and reference it during generation.
  </Card>

  <Card title="Generate from JSON" icon="brackets-curly" href="/cloud/guides/create-from-json">
    Build a presentation from structured slide content.
  </Card>

  <Card title="Cloud file-upload endpoint" icon="cloud-arrow-up" href="/api-reference/v3-files/upload-source-files">
    Inspect the multipart request and response.
  </Card>

  <Card title="Cloud image endpoints" icon="images" href="/api-reference/v3-images/list-uploaded-images">
    List uploaded assets, then open the upload or delete operation from the reference sidebar.
  </Card>
</CardGroup>

## 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.

<Card title="Document processing" icon="file-lines" href="/self-hosted/configuration/storage-and-processing">
  Review storage paths, parsing behavior, limits, and persistence.
</Card>

<Card title="Open Source file-upload endpoint" icon="server" href="/api-reference/files/upload-source-files">
  Inspect the multipart request and response.
</Card>

<Card title="Open Source image endpoints" icon="images" href="/api-reference/images/list-uploaded-images">
  List local uploaded assets, then open the upload or delete operation from the reference sidebar.
</Card>

## 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.

<Card title="See both deployment-specific file flows" icon="route" href="/api-guides/presentation-generation-flows">
  Open the Cloud or Open Source tab and follow its numbered source-file sequence.
</Card>