Attachments no longer depend on the model you picked. Every chat model now accepts documents, text and code, images, audio, video, and ZIP archives. When the selected model cannot read a file itself, Babbily reads the file first and gives the model what it found, so you do not have to switch models before attaching something or start over because a thread has the “wrong” model for a file. See what you can attach.
More formats are supported. Excel (.xlsx) and PowerPoint (.pptx) files, RTF, HWPX, HEIC and HEIF photos from an iPhone, and a wider range of audio and video formats now work alongside PDF, Word, text, code, and images.
ZIP archives work as one attachment. Attach a ZIP and Babbily reads the supported files inside it, up to 10 files per archive, and tells you which ones it skipped. Encrypted archives still need their password removed first. Attach a ZIP archive.
Each file is read once. Follow-up questions, message edits, and retries reuse what Babbily already read instead of reading the file again, so they are faster and do not spend your API usage budget on the same file twice. How reading uses your budget.
You can see what Babbily is doing. While a file is being read, the activity line shows Reading with the file name instead of a bare spinner.
Clearer answers when a file cannot be used. Babbily now names the file and the reason before the message is sent, and points to the fix: save a legacy .doc as .docx, remove a ZIP password, or send a smaller file. An old attachment that can no longer be read no longer blocks the rest of the thread. Troubleshoot a rejected file.
Long files fit better. File content now counts toward the context indicator as the text the model actually receives. When several files would not fit, Babbily shows the most recent ones in full and shortens the rest rather than failing your message. Understand the context window.