# Files and documents (/chat/files) Ask Sim to read an attachment, create a deliverable, or edit a workspace file. Name the output format and filename when you need a saved result. Supported generation and processing capabilities depend on your deployment. Release notes open beside Chat, with Sim summarizing shipped work and next steps ## Attach and save files [#uploading-files-to-the-workspace] Drag a supported file into the input, paste it, or select **Attach file**. Chat supports images, PDFs, text and code files, JSON, XML, and other supported document formats. Attachments are stored under `uploads/` and stay readable within the conversation. They do not automatically appear in workspace **Files** or workflow file listings. Ask Sim to save a copy when you need a workspace file: * "Summarize this document and extract the action items." Attach the document. * "Create a table from this CSV." Attach the CSV. * "Add this PDF to the Product Docs knowledge base." Attach the PDF. * "Describe this design mockup and write code for the layout." Attach the image. * "Save this attachment to workspace Files as source-data.json." Sim can also download a file from an accessible URL: "Download the JSON at \[URL] and save it as source-data.json." A successful upload does not mean every format's contents have been parsed. For a file without a supported reader, Sim may need to process the original bytes with code. ZIP archives must be extracted before their contents can be read. Direct uploads are deliberate input and are not automatically scanned for secrets. For stored files, Chat can mask tracked secret values or withhold content it cannot safely check. Your viewer can still open a file that Chat cannot read or receive as a rendered preview. Creating or returning a sharing link through Chat can also be refused. ## Create a text file [#creating-documents] Sim can write Markdown, plain text, code, CSV, and JSON files. Ask for the content and its destination: > Create test-accounts.csv with name, email, and plan tier columns. Save it to workspace Files. Saved workspace files appear in **Files** and can open in the resource panel. Text edits can appear as Sim writes; generated binary documents and media appear when their artifacts are ready. ## Edit an existing file [#editing-existing-files] Select the file through an `@`-mention or the **+** menu. It opens beside the conversation so you can review the edits. Describe the change: * "Update the pricing section with these new tiers: \[details]." * "Refactor this Python script to use async/await." * "Shorten this report's introduction and keep its findings intact." Name the existing file when you want Sim to update it rather than create another copy. Editing requires the relevant file access. ## Generate documents and presentations [#presentations] Specify a binary format such as `.pptx`, `.docx`, `.pdf`, or `.xlsx` when you need it. Availability depends on the configured document and sandbox capabilities. A request for a document can otherwise be fulfilled as Markdown. For presentations, include the audience, slide count, and contents: > Create an eight-slide Q3 review as q3-review\.pptx for the product team, covering growth, retention, and roadmap. Ask Sim to save the final file to the workspace. Open it to review the content and layout, then download it from the resource panel or **Files**. ## Generate or edit an image [#images] Describe the subject, style, size or aspect ratio, and intended use: * "Generate a feature announcement banner with a dark background and clean typography." * "Create a social card with this blog title and author name: \[details]." For a variation, attach an image or reference a workspace image: "Generate a version of this banner with a blue color scheme instead of green." Saved generated images appear in workspace **Files**. ## Create charts and diagrams [#charts-and-visualizations] Reference the data and name the chart you need: * "Plot workflow run counts from the metrics table as a weekly bar chart." * "Create a line chart of token usage over the past 30 days from this data: \[data]." * "Show the distribution of lead sources from the leads table as a pie chart." Sim can also create diagrams from a description, such as the webhook pipeline's data flow or a horizontal version of an existing diagram. Ask for a code-based diagram when exact labels and structure matter. Save the chart or visualization as a file, then inspect it in the resource panel. ## Process data [#calculations-data-processing] Sim can run code for calculations and one-off transformations: * "Extract records from this JSON where status is 'failed'." * "Calculate p95 latency from these timing values: \[values]." * "Convert these Unix timestamps to ISO 8601." * "Deduplicate this email list without case sensitivity." Results can be returned in the chat. Ask Sim to save a file when you need to reuse them. The Chat workbench holds temporary computation files while its session exists; those files become workspace files only when explicitly saved or exported. Code outputs written to the per-call `SIM_OUTPUT_DIR` are exported to workspace **Files**. If a requested stored file, folder input, or table snapshot is withheld, the code does not run. Check the excluded-input report before trying again. Later calls without that input remain available. ## View and reuse files [#file-viewer-modes] The viewer depends on the file type and your access: | File | Viewing and editing | | - | - | | Markdown | Read and edit in place | | Supported text with a rendered preview, such as HTML | Use **Edit Mode**, **Split Mode**, or **Preview Mode** when editing is allowed | | Images, PDFs, and supported Office files | Open the format's preview | | Unsupported files or files too large for an editor | Download the file or ask Sim to process it | Workspace files can be read with a File block or passed as workflow inputs. A chat attachment must first be saved to workspace **Files** when the workflow needs a reusable workspace file. ## Related docs [#related-docs] * [Files](/files) * [File editor](/files/editor) * [Generating files](/files/generating) * [Using files in workflows](/files/using-in-workflows)