LADLE reads files you attach to a chat or a project and answers questions grounded in them. The specifics — what formats, how big, how many — are the numbers below. These are contractual: if the product allows more or less than what's stated here, the docs page is the source of truth and the discrepancy is a bug.
Supported file types
Files attach via the composer + button, drag-and-drop into a chat, or from a project's file panel.
Per-file and per-chat size limits
Files are chunked by the model when they exceed the context window, but the limits below are hard caps at the upload layer.
How attachments count against context
Every file attached to a chat consumes context tokens on every message you send in that chat. A 200-page PDF re-processes with each of your prompts, which counts against your plan's usage tier. Projects attach files once at the project level so every chat within the project inherits them; this is more efficient if you're referencing the same files across sessions. For heavy multi-file workflows, the /docs/usage-limits page explains the token math.
Unsupported file types
Video (MP4, MOV) — not yet. Audio (MP3, WAV) — not yet; transcribe externally and attach the transcript. Archives (ZIP, TAR) — must be unzipped before attaching. Encrypted or password-protected files fail at upload with a specific error. Extremely rare formats (proprietary CAD, legacy office docs) will attach but may produce poor output.
Edge cases and known behaviours
OCR quality on hand-scanned PDFs varies; if a scan is illegible, LADLE will say so rather than fabricate. Images embedded inside PDFs are read via vision but with lower fidelity than a directly-attached image. A file uploaded to a Project and then deleted from that Project is removed within 30 seconds; the underlying storage record is purged within 24 hours.