Skip to main content
Explainer

Supported file types and limits

Learn which files Ampere accepts for Knowledge Base uploads, project context, and prompt attachments.

Last verified 2 days ago

Ampere accepts different file types depending on where you add context. Use the Knowledge Base for reusable organization knowledge, project files for campaign or client-specific material, and prompt attachments for files that only need to guide the current request.

The limits are different on each surface, so choose the upload path that matches how long the file should stay useful.

Quick reference

SurfaceSupported file typesCurrent limitBest for
Knowledge Base.pdf, .doc, .docx, .rtf, .md, .mdx, .txt, .csv, .json10 files per upload session, 10 MB eachReusable team knowledge, shared documents, research, and source material
Project files.txt, .md, .markdown, .mdx, .html, .htm, .rtf, .docx, .pptx, .xlsx, .pdf, .png, .jpg, .jpeg, .webp, .svg25 MiB per file by defaultFiles that belong to one project, campaign, client, or workstream
Prompt attachmentsDocuments: .pdf, .doc, .docx, .txt, .md, .csv, .json; images: .png, .jpg, .jpeg, .gif, .webpUp to 5 attachments per message, 10 MB eachOne-off files that should guide the current prompt

Knowledge Base uploads

Use the Knowledge Base when the file should become reusable source material for your organization. It is the right place for evergreen product information, positioning, messaging notes, research, and documents your team may need across more than one project or session.

The Knowledge Base upload dialog accepts up to 10 files at a time, with a 10 MB limit per file.

Knowledge Base upload dialog listing supported formats and the max file count and size
Knowledge Base uploads support common document formats and show the current limit directly in the upload dialog.

After upload, browser preview behavior depends on the file type. PDF, Markdown, MDX, text, CSV, and JSON files can be viewed in the browser. DOC, DOCX, and RTF files can be uploaded and processed, but they show a preview-unavailable state instead of an in-browser preview.

Project files

Use project files when the source material belongs to one project. Project files can sit alongside the project brief, saved project assets, project-specific chats, and other context for that workstream.

Project file uploads support text, Markdown, HTML, RTF, DOCX, PPTX, XLSX, PDF, and common image formats. They use a 25 MiB per-file default cap.

Project Uploaded Files area with a launch-notes markdown file saved
Project files live in the project Uploaded Files area, where they can be reused with the rest of the project context.

Legacy .doc and .ppt project files are not accepted in the project upload flow. Export those files to DOCX, PPTX, PDF, or another supported format before adding them to a project.

Prompt attachments

Use a prompt attachment when the file only needs to guide the current request. Attachments are useful for quick reference images, screenshots, one-off documents, or source files that do not need to become reusable project or Knowledge Base context.

Prompt attachments support common document and image formats, with a 10 MB limit per file and up to 5 attachments per message. The Home composer currently exposes an image attachment path, so use the file picker available on the surface where you are working.

Joule home composer with a project reference image attached
Prompt attachments are best for files that only need to guide the current request.

If the same file will help future work, add it to a project or the Knowledge Base instead of attaching it repeatedly.

If a file is not accepted

Check these details first:

  • The file extension matches the surface where you are uploading it.
  • The file is under the size limit for that surface.
  • You are not adding more files than the current upload flow allows.
  • Legacy project files such as .doc or .ppt have been exported to a supported format.
  • The file belongs in the place you are uploading it: Knowledge Base for reusable source material, project files for project-specific context, or prompt attachments for one request.

If a large file is blocked by the limit, split it into smaller source files or export only the section Joule needs for the current work.

Was this article helpful?

Related articles