Attachments
Put a file, a recording or something you already made into a conversation — and know who can see it afterwards.
Anything you attach to a message becomes part of the conversation: Endless looks at it, works from it, and can come back to it later in the same chat.
Four ways to attach something
The add menu
"Open add menu" next to the composer, then "Photos & files" — described as "Upload or pick a generation".
Drop it on the page
Drag files anywhere over the chat: "Drop files to attach", "Drop anywhere to add them to your prompt".
Paste it
Paste a screenshot or a copied image straight into the composer. A copy that also carries text — a spreadsheet selection, say — pastes as text instead.
Pick something you already have
The same "Photos & files" row opens a picker with an "Assets" tab over your workspace library, next to a "Device" tab for a fresh upload.
The picker is titled "Attachments" — "Browse your assets or upload from your device to attach to the prompt." — and its library side filters by "All", "Images", "Videos", "Audio" and "Docs".
Existing work is reached through that picker, not through @. Mentions bring
in projects, transcripts and models; files come from the add menu. See
Mentions.
What you can attach
Images, video, audio, and documents and text files — PDF, Word, Excel, csv, markdown, plain text, JSON and similar. The device drop zone states the ceiling as "Images, video, audio, and documents up to 100 MB", and you can attach up to 20 files at once; ask for more in one go and the whole batch is refused with "You can upload up to 20 files at a time". Attach another batch after it and they add up — there's no cap on how many end up on one message.
Documents have a much lower ceiling than that hint suggests, and a document that's too big can be left out of the message without an error saying so. If Endless answers as though a document wasn't there, its size is the first thing to check — split it or attach the part that matters.
What Endless does with each kind
Images
Seen directly — Endless reads the picture itself, so you can ask about what's in it, edit it, or use it as a reference for a new one.
Documents and text
Read as text. PDFs, Word files and spreadsheets are extracted and handed to the conversation as reference material. A scanned PDF with no text layer can't be read this way — Endless will say it can see the file but not read it.
Video and audio
Not watched automatically. Endless is told the file is there and looks at it when the question needs it — and for speech, the better route is a real transcript.
An attachment stays available for the rest of the conversation, not just the message you attached it to. You don't need to attach the same file again to ask a second question about it.
Working with recordings
For anything speech-heavy, make a transcript — it's searchable, has speakers and timestamps, and the chat can read it back on demand.
Not every model reads images
If the model powering the conversation can't look at pictures, sending is blocked with "…can't analyze images — pick another model". Switch model and send again.
What happens to an attachment afterwards
This is the part worth reading twice, because attaching a file has consequences beyond the message.
Uploaded media becomes an asset
Images, video and audio you upload are saved to the workspace library and show up in Assets — the same as anything you generate. They're private to you the moment they land.
Documents from your device don't
A PDF or spreadsheet you drag in from your computer is used by the conversation but is not added to your Assets library. If you want a document kept, upload it in Assets first and attach it from the "Assets" tab of the picker instead.
The chat carries its own access
An attachment is linked to the conversation, and that link is one of the ways someone else can end up seeing it: anyone who can open the chat can see what's attached to it. Share a chat with your workspace and its attachments come along, without those files themselves changing.
Attaching doesn't make a file public, and sharing a chat never makes its attachments editable by anyone else — only whoever created a file can rename, re-share or delete it. The complete list of ways someone can see your work is in Assets and visibility.
Who can see it
The five paths to an asset — you made it, it's shared, or it's in a chat, a canvas or a project they can reach.
Where it lives
Assets in the sidebar, filterable by type, project, creator and date.
If an attachment won't send
Endless checks attachments before it sends, and says which one is the problem:
- "Wait for the upload to finish before sending" — the file is still going up. The message keeps everything you typed; send again in a moment.
- "An attachment failed to upload — retry or remove it first" — the chip itself becomes the retry control. Select it to try the same file again, or remove it.
- "An attached file can't be sent — remove it and try again" — an older library item that Endless can't hand to a model. Remove it and attach a current one.
Uploading needs your workspace to have Assets turned on, and it needs permission to create content — a Viewer has neither the upload nor the generate half. If every upload fails immediately, that's the thing to check with an admin. See Roles and permissions.