Help and guides

Manage files

Browse folders, upload files, and check your storage limits.

Before you start

Select the organization and storage resource you want to use. Your role must allow the action.

Steps

Open Storage, then Files for the resource you want to manage.
Choose New folder to organize files.
Choose Upload files and select the files to add.
Wait for the upload to finish and check the file list.
Use View limits to check the allowances shown for your resource.

What to expect

Completed uploads appear in the file list. A file upload does not automatically make the file public.

If something goes wrong

If an upload fails, check the file size, available limits, and your access. Keep your original file until the uploaded copy is confirmed.

Technical reference

Files and Buckets share one allowance

Files provides folders and sharing. Buckets exposes private developer objects at https://s3.thora.cloud, region us-east-1, with path-style addressing. Public buckets, ACLs, policies, and website hosting are not supported.

Administrators create buckets and bucket-scoped keys.
Keys independently grant read, upload, and delete, may restrict an object prefix, and expire in 1–90 days.
Secrets are shown once. Signed GET and PUT links expire in at most one hour.
Revoking the signing key invalidates its signed links.

Configure a supported S3 client

Supported operations include bounded bucket listing, object listing, PUT, GET, HEAD, DELETE, byte-range GET, conditional reads, and multipart upload. This is an S3 subset, not full Amazon S3 parity.

AWS SDK for JavaScripttypescript

const storage = new S3Client({
  endpoint: "https://s3.thora.cloud",
  region: "us-east-1",
  forcePathStyle: true,
  requestChecksumCalculation: "WHEN_REQUIRED",
  responseChecksumValidation: "WHEN_REQUIRED",
  credentials: {
    accessKeyId: process.env.THORA_ACCESS_KEY_ID!,
    secretAccessKey: process.env.THORA_SECRET_ACCESS_KEY!
  }
});

Stay inside the data-plane limits

10 buckets and 20 active keys per workspace.
Three active uploads per workspace and 25 GiB per object.
Single PUT is limited to 16 MiB; use 8 MiB multipart chunks for larger objects.
Use one upload connection during beta and known Content-Length bodies.
Pending, replaced, cleanup, and incomplete multipart allocations can continue counting until exact cleanup succeeds.