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

# Multimodal input

> Prepare file-input limits and representative image or document examples while multimodal conversation support remains planned.

Multimodal input would let a conversation use an image or document as part of a request. Prepare the intended task and limits now, but do not depend on a released upload-to-model conversation workflow.

<Note>
  The agent contract includes file-input configuration. This does not establish working image or PDF uploads, model processing, file retention, or per-file charging. Live multimodal conversation support is not available through this guide.
</Note>

## Prepare the input contract

The fields below belong to `conversation_config.conversation.file_input` and can be reviewed as part of an [agent draft](/agents-platform/deploy/versioning).

| Field | Authoring constraint |
| - | - |
| `enabled` | Boolean; defaults to `true` in the schema. This is not a readiness signal. |
| `max_files_in_memory` | Integer from 1 to 30; default 10. |
| `max_files_per_conversation` | Default 10. Must be `-1` or at least `max_files_in_memory`. |

Prefer a small, explicit limit for your intended task. Do not interpret `-1` as an entitlement to unlimited storage or processing. These fields do not define a deletion schedule or establish how long files are retained.

## Prepare examples for later testing

<Steps>
  <Step title="Define what the file contributes">
    Write one concrete task, such as identifying the model number on a product label. Specify what the agent should do when the label is unreadable or missing.
  </Step>

  <Step title="Select a compatible model when available">
    Check the current [model catalog](/overview/models) for the exact input capability. Text generation support alone does not establish image or document understanding.
  </Step>

  <Step title="Create a small review set">
    Use synthetic files covering a clear example, a low-quality example, an irrelevant file, and conflicting text. Record the expected answer and when the agent should request clarification.
  </Step>

  <Step title="Keep file input separate from knowledge">
    A per-conversation attachment is different from a maintained workspace [knowledge document](/agents-platform/configure/knowledge-base/overview). Choose the latter for reviewed information intended to be reused across agents.
  </Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does enabled: true mean users can upload files now?" id="faq-multimodal-enabled">
    No. It is an authored setting. A supported client, upload path, model integration, and released conversation path are still required.
  </Accordion>

  <Accordion title="Does the memory limit define file deletion?" id="faq-multimodal-retention">
    No. Do not use these fields as a retention policy. Confirm the released file-storage and deletion behavior before accepting real user files.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.