Bring the useful context.
Attach a supported file using the control beside the chat input. File support depends on the selected model and route. The information control shows the current limits.
Current attachment limits
The workspace accepts up to four attachments per message and up to 3 MB of attachments across a conversation. A longer chat can reach the file budget even if the latest attachment is small. Start a new conversation when needed.
Text expansion and individual models can impose tighter request limits. Splitting a task into smaller parts often helps.
Supported ZKR file workflows
| File | Protected workflow |
|---|---|
| Plain text | Detected values can be masked before supported requests |
| Supported readable text is prepared for review | |
| DOCX | Text-only content is supported; complex embedded content may not be |
| Receipt or screenshot | Readable text can be recognized and reviewed |
English printed receipts are the current reference case. Other languages, handwriting, charts and complicated layouts may not be read correctly.
Images and visual detail
With ZKR enabled, a protected image is rebuilt from reviewed text. It does not retain the complete original scene, chart, signature, QR code or layout.
With protection off, a compatible cloud image request can send the original image. Make that choice deliberately. An image attached to chat can support a text answer. Use the separate Images page to generate or edit an image, or Video for a supported reference-to-video task. Media creation has its own limits and privacy controls.