Skip to main content
Start with a private writable S3 disk. Configure this guide only if the browser should send large parts directly to the provider.

Upload directly to private S3

Install the Laravel S3 filesystem adapter in the application. Configure a private S3 disk and use it as the storage disk when creating the workspace. Existing workspaces keep their configured disk. Enable direct multipart on the server.
Serve the app over HTTPS so the browser can checksum each part. Studio signs the part size and checksum and sends the bytes directly to S3. The app completes the multipart upload and streams the assembled object once to verify its type and digest before publishing it in the library. Keep thumbnail generation on a background queue for large files. Configure the bucket to allow PUT from the application origin and expose the part response’s ETag to the browser.
The application role needs scoped permissions to create, list parts, complete, abort and read uploads, and to remove failed objects in the configured prefix. Set an S3 lifecycle rule to abort incomplete multipart uploads after a period longer than the maximum session duration. This also covers interrupted initialization where the application never receives an upload ID.

When Studio chooses direct transfer

For a new session, Studio selects this transport when the client requests direct transfer, the file meets the threshold, and the workspace resolves to a writable private S3 adapter. A client should branch on the returned transport field. The part size must be between 5 and 32 MiB. Signed URLs are bounded to 30–900 seconds and may expire sooner when the session expires. Upload API for custom clients

IAM and lifecycle

For multipart operations on the Studio object prefix, review s3:PutObject, s3:ListMultipartUploadParts, s3:AbortMultipartUpload, s3:GetObject, and s3:DeleteObject. If S3 bucket versioning is enabled, the cleanup path can also remove a specific version and needs s3:DeleteObjectVersion. Additional permissions depend on the rest of your storage features and on KMS. AWS multipart permissions For a one-day Studio session TTL, a bucket lifecycle rule can abort incomplete uploads under the managed prefix after three days. Schedule Studio session pruning as well. The bucket rule covers abandoned multipart uploads at the provider, including those Studio could not record.

Verify and diagnose

Test from the real browser origin. Upload a file above the threshold, confirm the part PUTs target the bucket, and verify the file appears in Studio only after completion. Test resuming an interrupted part and downloading the verified original. AWS CORS configuration