# Youtube uploads automation **URL:** \ **Category:** Questions\ **Tags:** youtube\ **Created:** [July 31, 2026, 6:06am UTC](https://community.make.com/t/youtube-uploads-automation/112783 "2026-07-31T06:06:19Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![DILSHER](https://avatars.discourse-cdn.com/v4/letter/d/e95f7d/32.png) [@DILSHER](https://community.make.com/u/DILSHER)\ **Post date:** [July 31, 2026, 6:06am UTC](https://community.make.com/t/youtube-uploads-automation/112783/1 "2026-07-31T06:06:19Z")
### 🎯 What is your goal? I want to upload at least 50 videos on youtube daily. Each video file size is around 200MB. ### 🤔 What is the problem & what have you tried? Hi everyone, I’ve built a simple YouTube upload automation in [Make.com](http://Make.com) with the following workflow: The user enters the video details (Google Drive link, title, description, etc.) into a Google Sheet. The Google Drive – Download a File module downloads the video. The YouTube – Upload a Video module uploads it to YouTube. The workflow itself works perfectly. However, I’ve run into what seems like a major limitation. My understanding is that all paid [Make.com](http://Make.com) plans include 5 GB/month of data transfer. In my use case, I expect to process around 20 GB of video data per day, so I’d exceed that limit very quickly. Am I misunderstanding how the data transfer limit works, or is [Make.com](http://Make.com) simply not designed for high-volume video upload workflows like this? Has anyone built a similar system at scale? If so: How did you handle the data transfer limitation? Is there a better architecture that still uses [Make.com](http://Make.com)? Or is this the point where a custom uploader (using the YouTube API) becomes the better solution? I’d really appreciate any advice from people who have tackled similar workflows. Thanks! ### 📸 Screenshots (scenario flow, module settings, errors) ![Screenshot 2026-07-31 111322.png](https://europe1.discourse-cdn.com/flex013/uploads/make/optimized/3X/a/1/a1c53258c61d48f184a41024350fa74a7d66894b_2_690x46.png) ---
**Author:** ![Stoyan\_Vatov](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Stoyan\_Vatov](https://community.make.com/u/Stoyan_Vatov)\ **Post date:** [July 31, 2026, 6:57am UTC](https://community.make.com/t/youtube-uploads-automation/112783/3 "2026-07-31T06:57:21Z")
Its 5GB for every 10k operations. You’d see it if you hover over the question mark next to Data transfer. ---
**Author:** ![Dmitrkoliga](https://avatars.discourse-cdn.com/v4/letter/d/65b543/32.png) [@Dmitrkoliga](https://community.make.com/u/Dmitrkoliga)\ **Post date:** [August 5, 2026, 10:51am UTC](https://community.make.com/t/youtube-uploads-automation/112783/5 "2026-08-05T10:51:31Z")
> [@DILSHER](#): > > ### What is your goal? > > I want to upload at least 50 videos on youtube daily. Each video file size is around 200MB. > > ### 🤔 What is the problem & what have you tried? > > Hi everyone, > > I’ve built a simple YouTube upload automation in [Make.com](http://Make.com) with the following workflow: > > The user enters the video details (Google Drive link, title, description, etc.) into a Google Sheet. > The Google Drive – Download a File module downloads the video. > The YouTube – Upload a Video module uploads it to YouTube. > > The workflow itself works perfectly. > > However, I’ve run into what seems like a major limitation. My understanding is that all paid [Make.com](http://Make.com) plans include 5 GB/month of data transfer. In my use case, I expect to process around 20 GB of video data per day, so I’d exceed that limit very quickly. > > Am I misunderstanding how the data transfer limit works, or is [Make.com](http://Make.com) simply not designed for high-volume video upload workflows like this? > > Has anyone built a similar system at scale? If so: > > How did you handle the data transfer limitation? > Is there a better architecture that still uses [Make.com](http://Make.com)? > Or is this the point where a custom uploader (using the YouTube API) becomes the better solution? > > I’d really appreciate any advice from people who have tackled similar workflows. Thanks! For that volume, I’d seriously consider using Make only for orchestration and letting a custom service handle the actual YouTube uploads through the API. It keeps the automation simple while avoiding potential bottlenecks with large file transfers. ---
**Author:** ![Vu\_Nguyen\_Long](https://avatars.discourse-cdn.com/v4/letter/v/c2a13f/32.png) [@Vu\_Nguyen\_Long](https://community.make.com/u/Vu_Nguyen_Long)\ **Post date:** [August 15, 2026, 4:25pm UTC](https://community.make.com/t/youtube-uploads-automation/112783/6 "2026-08-15T16:25:35Z")
good catch from stoyan on the real limit, it’s 5gb per 10k operations, not a flat monthly number, so the math changes depending on how your scenario counts operations per video. either way at 20gb a day you’re going to hit a wall eventually. dmitrkoliga’s right that keeping make for orchestration and pushing the actual upload to a custom service is the cleanest fix. a couple things worth checking before you build that: - if you want to avoid rewriting the whole leg, see whether your drive files can go through a signed url instead of a full file download inside the module, some setups count that differently against transfer limits and it’s a smaller change than a full custom uploader - youtube’s own upload api has its own daily quota completely separate from make’s transfer limit, so once the transfer issue is sorted you may still hit a ceiling on the youtube side at 50 videos a day, worth checking your quota usage now so it’s not a second surprise building the custom upload step is probably the right call long term either way, just wanted to flag the two things that tend to bite people right after they think they’ve fixed it.