Make file size caps 5, 100, 250, 500 MB: pass a Sume URL, not the file

The caps

Make's pricing page lists a file size limit per plan: 5 MB on Free, 100 MB on Core, 250 MB on Pro, 500 MB on Teams and 1,000 MB on Enterprise. Core also lists 5 GB of data transfer. A finished video can exceed the Free limit quickly, so do not download it into the scenario unless you must.

Why a URL is enough

A Sume result is a public media.sume.com artifact URL, and Sume accepts inputs as public HTTPS URLs too. Nothing in a Sume to Sume or Sume to Sheets chain needs the bytes: pass the string. The size cap only applies once a Make module downloads or uploads the file itself.

So where does the file need to move? Only for destinations that insist on an upload, such as a storage module. For those, check the size first with a HEAD request and the Content-Length header, and route files above the plan cap to a different path, such as saving the link.

Steps

Inputs to Sume must be public HTTPS URLs, so signed or private links will not work as sources. See the asset library docs.

• Submit the Sume job and keep its id.
• On job.completed, read /v1/jobs/:id/result and take the URL.
• Write the URL into the destination cell, record or message.
• Only download when the destination needs the file, and test the length first.

Caveat

The Make page does not say which limit applies to a single module or to a whole execution, so test with a file just above your plan cap before you build around it.