# Files (/files) **Files** stores your workspace's documents and media. Ask Sim to create, summarize, or edit a file, and open it beside the conversation to review the result. See [Files in Chat](/chat/files) for attachments and supported formats. Sim reviewing a release brief in Chat, with its Markdown checklist, owner table, and JSON code block open beside the conversation Use [Tables](/tables) for structured rows and fields, and a [knowledge base](/knowledgebase) when an agent needs to search across documents. Adding a file to Files does not automatically add it to a knowledge base. ## Upload or create a file [#upload-or-create-a-file] 1. Open **Files** in the workspace sidebar. 2. Select **Upload**, or drag files into the list. Open a folder first to upload into it. 3. Select **New file** to create a Markdown document, or **New folder** to organize files. 4. Open a file to view it. Members with edit access can edit supported text files. Workspace uploads support files up to 5 GiB each, subject to available workspace storage. This storage limit does not mean every viewer, workflow block, or external service can process a file that size. See [file limits](/files/passing-files#file-limits) before using a large file in a workflow. ## Preview, edit, and download [#preview-edit-and-download] The viewer depends on the file's format, size, and your access: | Format | Available view | | - | - | | Markdown | Rich editing, with source editing when rich editing cannot preserve the document | | Text and code | Text editor | | CSV, HTML, SVG, Mermaid, and chart files | Format-specific previews; supported text files can also be edited | | PDF, DOCX, PPTX, and XLSX | Document, slide, or spreadsheet preview | | Common images, audio, and video | Image view or browser playback | | Unsupported formats | Download the file to open it elsewhere | HEIC and HEIF previews use server conversion. TIFF files are download-only. Browser media support and viewer size limits still apply. See [Editor](/files/editor) for Markdown formatting, source editing, and export behavior. Use **Download** in the file menu or viewer. Downloading multiple files or a folder produces a ZIP archive, subject to the [archive download limits](/api-reference/files/bulkDownloadFiles). A generated document's download can contain rendered bytes whose size and type differ from its stored generation source. ## Organize files [#organize-files] Use folders to group related files. The list can be searched, filtered, and sorted by properties such as type, size, owner, and last update. Open a file's menu to **Rename**, **Move to**, or **Pin** it. **Delete** removes the file from active Files and makes it eligible for the workspace's deletion lifecycle. Recovery and later cleanup depend on the effective [data retention policy](/platform/enterprise/data-retention); deletion does not promise immediate removal of every stored byte. ## Access and sharing [#access-and-sharing] Workspace files are private to members and callers with the required workspace access. Read access allows viewing and downloading; write access is required to upload, create, edit, rename, move, or delete files. Enterprise permission groups can restrict Files and sharing. To share a file outside the workspace: 1. Open its menu and select **Share**. 2. Choose an available access mode. 3. Select **Share**, then **Copy link**. | Access mode | Who can view and download | | - | - | | **Public** | Anyone with the link | | **Password** | Anyone with the link and password | | **Email** | Allowed emails or domains after verification with a one-time code | | **SSO** | Allowed emails signed in through SSO, when this mode is available | An administrator can disable public sharing or particular access modes. Sharing requires write access and a user identity; a workspace API key cannot enable a file share. To revoke a link, reopen **Share** and select **Unshare**. **Copy Link** in the file menu copies the workspace URL; it does not enable public sharing. ## Reuse files in agents [#reuse-files-in-agents] A workflow can read a workspace file when its execution identity has access. See [Using files in workflows](/files/using-in-workflows) for a read → summarize → save example. A file produced during a workflow run can remain an execution artifact without appearing in Files. [Save it to Files](/files/generating) when later runs need it. Execution files follow the run's lifecycle and are not retained indefinitely. [Chat attachments](/chat/files) stay private to the conversation until explicitly saved to workspace Files. Saving an attachment makes it a workspace resource; it does not create a public share link. ## Related docs [#related-docs] * [Editor](/files/editor) * [Using files in workflows](/files/using-in-workflows) * [Generating files](/files/generating) * [Passing files](/files/passing-files)