Quick checks
File support basics
Every chat model accepts documents, text and code, images, audio, video, and ZIP archives. What the selected model cannot read itself, Babbily reads for it. Support depends on the file’s format and size rather than on the model you picked. Image, video, and character models are the exception. Files you attach to them are source media for that model, so those models keep their own narrower rules.Supported formats and size limits
Review the full list of formats, size limits, and what is not supported.
The file picker offers exactly the formats Babbily can read, so an unsupported file is usually filtered out before you choose it.
If a file will not upload or send
Try these steps:1
Check the format
Legacy Office files (
.doc, .xls, .ppt) are not supported. Save them as .docx, .xlsx, or .pptx. Convert GIF, BMP, TIFF, MKV, or WMA files to a supported format.2
Check the size
Images can be up to 20 MB. Documents, audio, video, and ZIP archives can be up to 50 MB. Babbily names the file and its limit when a file is too large.
3
Try one file first
Add the most relevant file before adding more context. Babbily reads a limited number of files for one message.
4
Check a ZIP archive
Remove the password from an encrypted archive, and keep the files you want read at the top level.
5
Send it again
If Babbily says a file could not be read right now, sending the message again usually works. Check your API usage budget if the message mentions usage.
6
Start a new thread
Use a clean thread when older files or instructions are no longer relevant.
Voice dictation
Voice dictation depends on browser support, device support, microphone permission, and account state. Some app surfaces may use a transcription flow when browser speech input is unavailable. If dictation fails:- Allow microphone access.
- Close other apps that may be using the microphone.
- Try a shorter recording.
- Refresh Babbily after changing permissions.
- Type or paste text if your current browser or device does not support dictation.
Notifications
Completion notifications depend on browser support, device support, notification permission, and your Babbily setting. If notifications do not appear:- Open Settings > Account > Notifications and confirm Chat completion notifications is on.
- Allow notifications for Babbily in your browser or device settings.
- On iPhone or iPad, use Share > Add to Home Screen, then open Babbily from the Home Screen and enable notifications there.
- Use Babbily in a supported browser. Push notifications may be unavailable in some embedded, private, or restricted browser surfaces.
- Refresh Babbily after changing notification permissions.
- Check whether you were already looking at Babbily when the run finished. Babbily may skip a notification when you are already active in the app.
Passkeys
Passkeys are currently available on supported web browsers. Use another sign-in method in the native app if passkeys are unavailable. If passkeys do not appear or a prompt fails:- Refresh Babbily in a supported browser.
- Confirm your device, password manager, or security key supports passkeys.
- Sign in another way and add, rename, or remove passkeys from Settings > Account.
Plugin authorization windows
Some plugin setup flows open a separate authorization window and then return you to Babbily. If the window does not open:- Allow pop-ups for Babbily.
- Choose Authorize again.
- Complete the authorization flow in the app you are connecting.
- Return to Settings > Plugins and refresh.
File attachments
Learn how to attach files and get better file results.
Voice dictation
Use the microphone in Chat and Translate.
Plugin troubleshooting
Fix plugin setup, authorization, status, and permissions.
Known limits
Understand why behavior can vary by model, file, plan, usage, and account state.