I've written a blog on how to implement this: Uploading Videos for Use in Remotion. Adding this directly into the code wouldn't work for everyone since it's hard to pick the "right" external storage solution for each use case. Instead, I've created a simple guide on how it can be implemented. This guide uses Supabase, but if you'd like guides for other options, let me know! Implementing something like this shouldn't take much work, as many of the inner workings are already in place. 😊
Santosh S
•
Nov 29, 2024
beautiful sam!
Sam Bowen-Hughes
Team•
Nov 7, 2024
I've spent some time looking into this and will work on a functional implementation. However, I'm still undecided on the best approach for storing the uploaded video, as both your AWS Lambda and site will need access to it when rendering the final output. A storage solution will be necessary. Potential options include:
AWS S3 Storage
Supabase Storage
Azure Storage
I'm open to any suggestions on this
Emiliano
•
Jan 4, 2025
I recommend Tigris Storage. They have a globally-distributed unique endpoint and they don’t charge for egress so you won’t get a crazy bill if your assets are downloaded multiple times per render (like when rendering with Remotion Lambda).
Tigris is S3-compatible so you should be able to just let the user define the S3 settings via environment variables and use the AWS S3 Node SDK to upload files. Supabase also has an S3-compatible layer so it will also work for it.
Comments4
Sam Bowen-Hughes
Nov 29, 2024
I've written a blog on how to implement this: Uploading Videos for Use in Remotion. Adding this directly into the code wouldn't work for everyone since it's hard to pick the "right" external storage solution for each use case. Instead, I've created a simple guide on how it can be implemented. This guide uses Supabase, but if you'd like guides for other options, let me know! Implementing something like this shouldn't take much work, as many of the inner workings are already in place. 😊
Santosh S
Nov 29, 2024
beautiful sam!
Sam Bowen-Hughes
Nov 7, 2024
I've spent some time looking into this and will work on a functional implementation. However, I'm still undecided on the best approach for storing the uploaded video, as both your AWS Lambda and site will need access to it when rendering the final output. A storage solution will be necessary. Potential options include:
AWS S3 Storage
Supabase Storage
Azure Storage
I'm open to any suggestions on this
Emiliano
Jan 4, 2025
I recommend Tigris Storage. They have a globally-distributed unique endpoint and they don’t charge for egress so you won’t get a crazy bill if your assets are downloaded multiple times per render (like when rendering with Remotion Lambda).
Tigris is S3-compatible so you should be able to just let the user define the S3 settings via environment variables and use the AWS S3 Node SDK to upload files. Supabase also has an S3-compatible layer so it will also work for it.