Paste images into a Complexity message
Use images beside prose and annotations in a Complexity message. Select an allowed model with image input support.
Paste an image
- Place the cursor in the composer.
- Press Ctrl+V with an image file on the clipboard.
- Wait for Uploading and scanning to finish.
- Check the inline image token and the thumbnail above the composer.
- Add your question and send the message.
The token and thumbnail refer to the same attachment record. Repeated tokens keep the same stable image_<attachment-id> reference. The thumbnail strip shows each record once. Removing a thumbnail removes every occurrence of that image from the draft.
Keep the draft and cursor unchanged during upload. If either changes, the application rejects the late insertion. An upload failure leaves the existing draft intact.
Model support and limits
The selected model must advertise image input and use a supported provider API. Completion APIs do not support this input. Anthropic and Google require chat APIs. Other supported adapters can use chat or Responses APIs. A configured capability does not guarantee that the provider accepts the request.
| Limit | Value |
|---|---|
| Image formats | PNG, JPEG, WebP |
| Size per pasted image | At most 5 MiB |
| Width and height | At most 8,000 pixels each |
| Total pixels per image | At most 16,000,000 |
| Animation | Not supported |
| Image occurrences per message | At most 10, including repeated references |
| Distinct attachments per message | At most 10, including other files |
| Prose, image, and annotation segments | At most 61 |
| Total prose, selection, and comment characters | At most 200,000 |
The server checks the decoded format against the declared MIME type. Corrupt images and animated images fail admission. Request limits also include encoded images, repeated occurrences, and history. Several valid images can therefore exceed the request budget.
Scan and send failures
Uploads require a clean virus scan. Before a run starts, the server checks attachment ownership, the chat, scan status, image validity, and model support. An image reference does not grant access to another chat or account.
If admission fails, correct the reported problem before sending again. Choose an image-capable model, remove an unavailable reference, or use fewer or smaller images. Provider processing can still fail after admission.
Order, history, and copy
The message stores prose, annotations, and image references in their authored order. Provider content keeps that order and includes the image bytes with their stable references. The application resolves bytes from the authorized attachment record.
Reopening the same chat uses its saved attachment references. Access checks still apply. A fork does not carry the original images into the new thread.
Ctrl+C and Ctrl+V within the composer preserve supported image tokens and their order through rich clipboard content. Copy formatted on a user message also carries these tokens. The clipboard contains references, not image bytes or storage URLs. Pasting a reference into another chat does not copy or authorize its attachment.
Copy Markdown and plain-text copy contain aliases such as [image_<attachment-id>]. Those aliases alone do not restore an image. Copy the image file itself when you need a new upload.