For content that doesn’t live at a URL — PDFs, exported docs, spreadsheets — create a Files source and upload directly. Each file is normalized to markdown, chunked, and embedded like any other source, and becomes a document you can inspect, restrict, or delete individually.

Data ingested

Every file becomes one document titled after the filename, converted to markdown by format: The filename is kept as its path within the upload, so handbook/auth.pdf and sdk/auth.pdf stay two documents.

Upload files

1

Create a Files source

In the dashboard, open Knowledge Base → Sources → Add source and choose Files. Optionally add a description (e.g. “Product manuals”) to keep multiple file collections organized.
2

Upload your documents

Drag and drop files onto the source, or click Upload. You can upload several at once; each file reports success or failure individually.
3

Verify

Uploaded files appear under Knowledge Base → Documents once processed. Ask a question answered only in an uploaded file to confirm it’s retrievable.

Accepted formats & limits

A folder of any size still uploads: the dashboard splits it into requests that fit and reports progress across all of them.
Uploading from a script or CI job? Files can also be pushed via the API’s multipart upload endpoint on the source — handy for publishing generated PDFs automatically. Send at most 10 files and 32 MB per request; anything over comes back listed with the reason, so you can retry just those.

Updating content

There’s no crawl to re-run — a Files source changes only when you upload new files or delete documents. To replace a stale file, delete its document and upload the new version.
A Files source has no Sync button: there is no upstream to fetch from, since the uploaded bytes are discarded once they have been indexed. Uploading again is the sync.

Good to know

  • PII masking applies at upload time too, so sensitive identifiers in uploaded documents are masked before storage.
  • Mark internal files restricted so they answer only for workspace members — see Roles & Permissions.