Storage

Connect your S3 bucket to keep the original files of your documents.

By default the platform extracts a document's text, indexes it and discards the file. If you want to keep the originals and be able to download them later, you need to register an S3-compatible storage here.

It is your bucket: the files are kept in your account, not on the platform.

Which providers work

Any one compatible with the S3 API: Amazon S3, Cloudflare R2, Backblaze B2 and similar. The provider field does not change the platform's behaviour; it is there to show you that service's specific help while filling in the form, because each one names things its own way.

Filling in the form

The values come from your provider's dashboard: the endpoint, the bucket name and the pair of access keys.

Two fields that often cause trouble:

Endpoint. Only the scheme and the host, for example https://abc123.r2.cloudflarestorage.com. No bucket at the end, no paths and no username or password inside the URL. If you write too much, the field itself warns you. On Amazon S3 the endpoint depends on the region; on Cloudflare R2 the dashboard gives it to you directly.
Region. Amazon needs it. R2 and B2 ignore it, so there you can leave it empty.

The secret key is only visible when you save it, just like in Provider credentials. It cannot be retrieved afterwards: if you lose it, generate a new pair at your provider.

Using it in a knowledge base

Registering the storage does not switch anything on by itself. You have to go to the knowledge base and turn on keeping originals there, choosing this credential — see Knowledge bases.

Remember the option only affects documents you upload from then on.

Deleting a storage

If any knowledge base has it assigned, the dialog detects it when it opens, lists those bases and does not offer the delete button.

It triggers even if that base has keeping originals switched off: it is enough that it still points at this credential. If you turned the option off but the credential is still selected, you will have to clear it from the base before you can delete it here.

Deleting it does not remove the files from your bucket either: the platform loses access, but the content stays in your account until you delete it yourself.

Updated on Aug 05, 2026