<p>I don't think there is anything native in Craft that is going to help you here.</p>

<p>FTP is probably the best bet.  Only images get downloaded from external sources during indexing, so it's a simple as FTP'ing up the files and rebuild the asset source indexes (which could be automated via cron job).</p>

CC BY-SA 3.0
2015-11-17T22:50:45.507Z
For what it's worth, [anecdotal evidence](http://stackoverflow.com/a/5828654) seems to dispute the [php docs](http://php.net/manual/en/ini.core.php) that ``memory_limit`` actually needs to exceed whatever file size you want to upload. Not sure how that affects Craft though since that may affect image processing...
RitterKnight
CC BY-SA 3.0
2015-06-17T19:01:43.960Z
2015-06-17T19:01:43.960Z
Brad Bell
<p>I’m building a site that needs to upload large video files to Amazon S3. We have run into limitations with our host where they will only increase the memory_limit to 512mb and it’s likely that there will be video files in excess of this. It seems that Craft stages the video file on the server before sending it to S3. Is there a way around this so we can bypass the hosting limits on file uploads and memory and not make the user use an FTP client to upload bigger files?</p>

<assets><server><s3>
Bypass server memory_limits for Cloud Asset resources
# Bypass server memory_limits for Cloud Asset resources

(Asked by: username_0 on 2015-06-17)

I’m building a site that needs to upload large video files to Amazon S3. We have run into limitations with our host where they will only increase the memory\_limit to 512mb and it’s likely that there will be video files in excess of this. It seems that Craft stages the video file on the server before sending it to S3. Is there a way around this so we can bypass the hosting limits on file uploads and memory and not make the user use an FTP client to upload bigger files?

**Tags:** assets, server, s3

---

## 1 answers

### Answer by username_1 on 2015-06-17. Score: 1

I don't think there is anything native in Craft that is going to help you here.

FTP is probably the best bet. Only images get downloaded from external sources during indexing, so it's a simple as FTP'ing up the files and rebuild the asset source indexes (which could be automated via cron job).

> **Comments:**
> **username_2**: For what it's worth, [anecdotal evidence](http://stackoverflow.com/a/5828654) seems to dispute the [php docs](http://php.net/manual/en/ini.core.php) that ``memory_limit`` actually needs to exceed whatever file size you want to upload. Not sure how that affects Craft though since that may affect image processing...  

---

