Files
The upload rules on this page apply to three places at once:
- Files (personal),
- project documents,
- chat attachments.
That matters: if a file type is supported here, you can normally upload it in a project or through chat as well.
Supported file families
Section titled “Supported file families”| Family | Formats | What the app does with it | Practical notes |
|---|---|---|---|
| Documents | .pdf, .doc, .docx, .odt, .txt, .md, .json, .xml, .xlsx, .xlsm, .xls, .ods | stores the original, extracts text, and indexes it for search/chat | Inline preview is limited; Office files usually go through download or “Read text”. |
| Presentations | .pptx, .ppt | processes slide content for search/chat | Upload is supported. Inline preview is not. Translate supports .pptx only. |
.eml, .msg | processes message content for search/chat | Useful for matter emails and mailbox exports. | |
| Images | .png, .jpg, .jpeg, .gif, .tif, .tiff, .bmp, .webp, .ico, .jfif, .pjpeg, .pjp, .svg, .heic, .heif | stores the image and uses OCR/image extraction where possible | Images preview inline. When OCR text is thin, processing falls back to Gemini Vision to still extract meaningful content. |
| Audio | .mp3, .wav, .flac, .m4a, .m4b, .aac, .3gp, .caf, .ogg, .oga, .opus, .mp4, .webm, .amr, .wma, .aif, .aiff, .mpeg, .mpga | turns audio into transcript text and indexes that transcript | .mp3 is supported. Use this for dictations, WhatsApp audio, and phone recordings. Long recordings are chunked through Speech v2 (chirp 3); if that fails, processing falls back to a Vertex AI transcript. |
| CAD | .dxf, .dwg | attempts to extract searchable content | Results depend on source quality and converter support. |
| BIM | .ifc | extracts building model semantics: storeys, spaces, elements, materials, and property sets | IFC 2x3 and IFC 4 are supported. Large models produce summarised text, not raw geometry. |
| BIM coordination | .bcfzip | extracts issue topics, comments, status, priority, and referenced IFC element GUIDs | BCF (Building Collaboration Format) clash reports and quality reviews. BCF 1.0–3.0 supported. |
| Archive | .zip | extracts supported contents and processes them individually | Supported inner files are processed; unsupported ones are skipped. Nested ZIPs are allowed within limits. |
Upload behavior
Section titled “Upload behavior”What you see in the UI:
- ZIP files are uploaded separately and then extracted in the background.
- Other files are uploaded afterwards.
- In chat you can drag files in or use the paperclip.
- Files you pick in chat via
@mention are auto-attached to the conversation. - Outside project chat, the shell asks whether the upload should go to personal files, an existing project, or a new project.
- Filenames containing em-dashes, smart quotes, and other non-ASCII characters are supported.
Processing statuses
Section titled “Processing statuses”| Status | Meaning |
|---|---|
pending | upload received, processing not started yet |
processing | general processing is running |
chunking | the document/transcript is being split into searchable chunks |
embedding | search vectors are being created |
indexing | the file is being committed to the knowledge layer |
completed | the file is ready for search, chat, and citations |
failed | processing failed; review the file and retry with a cleaner source if needed |
Important:
- the assistant can only use a new file reliably once it reaches completed / processed;
- in chat, the composer blocks sending while new attachments are still processing.
Preview, read-text, and download
Section titled “Preview, read-text, and download”The preview page is intentionally safe and conservative.
| Behavior | File types |
|---|---|
| Inline preview | .pdf, images, .txt, .md, .json, .xml |
| No inline preview, but useful fallback actions | Office files, presentations, email files, audio, CAD |
| Available fallback actions | Download, Read text, and where supported Translate |
Practical impact:
- Office, presentation, audio, and CAD files usually do not open inline.
- Use Read text when you want the extracted content.
- Use Download when you need the original binary file.
Metadata
Section titled “Metadata”Through Info you can review and often edit metadata such as:
- title,
- classification,
- tags,
- document date,
- duration,
- comments.
Good metadata improves:
- summaries,
- timelines,
- retrieval quality in chat.
Document actions
Section titled “Document actions”Per file you can normally expect actions such as:
- Preview or open in SharePoint if the file is linked there;
- Info for metadata;
- Download of the original file;
- Chat to start a conversation with the file as an
@mention; - Translate when the file format supports it;
- Delete if your permissions allow it.
Search, sort, and columns
Section titled “Search, sort, and columns”Document tables support:
- search/filtering,
- sorting,
- toggling visible columns.
Column choices are remembered locally in your browser.
Important caveats
Section titled “Important caveats”- Not every supported upload format also has inline preview.
- Translate only supports part of the upload matrix; see Translate.
- ZIP uploads can take longer because extraction happens before the inner files become usable.
- Unsupported files inside a ZIP are not partially converted; they are skipped.
- Project-specific review statuses belong to the project document table, not personal Files.