Question 1

What exactly is a 'Direct-to-Cloud' upload?

Accepted Answer

It means file bytes go directly from the user's browser to your cloud storage (like S3 or GCS) using a presigned URL. This bypasses your application backend, preventing OOM crashes, timeout failures, and bandwidth bottlenecks on your servers.

Question 2

Can I automatically process files after they are uploaded?

Accepted Answer

Yes. The Media service includes built-in async pipelines for OCR, video transcoding, image thumbnail generation, and AI-powered transcription. These are triggered automatically once an upload is marked as complete.

Question 3

How do I ensure private files stay secure?

Accepted Answer

All files are private by default. Access is managed through short-lived signed URLs generated on-demand after your backend performs a permission check. You can also create governed 'Share Links' with passwords and expiry dates for external users.

Question 4

Does the service support very large files?

Accepted Answer

Absolutely. We support resumable multipart uploads for files up to 1TB. This ensures stable transfers even on unreliable networks, as interrupted uploads can be resumed from the exact byte offset where they stopped.

Common Questions & Answers

Related services

Related use cases