Shopify hosted video limit by plan: 250 to 100,000 videos

A Shopify store can hold a fixed number of Shopify-hosted videos and 3D models, and the number depends on the plan: 250 on Starter, Pause and Build, Retail and Basic, 1,000 on Grow, 5,000 on Advanced, 50,000 on Plus and 100,000 on Enterprise. Separately, the Shopify Help Center lists video storage from 50 GB to 10 TB, and a single product can carry at most 250 images, 3D models or videos.

The other Shopify video posts here cover per-file limits and the weekly upload cap. This one is about the store-wide ceiling that a catalog of AI product clips can hit months after launch, and how to budget Sume clips so you do not.

What are the caps by plan?

Both tables come from Shopify's Add media to products page. The count table covers Shopify-hosted videos and 3D models together, so each 3D model you add takes a slot a clip could have used.

Which limit do you hit first?

Divide storage by the count cap and you get the average file size at which both limits run out together. This is my arithmetic, in decimal units, not a Shopify figure. Above that average, storage ends first; below it, the count does.

What other limits sit next to these?

The same Help page says a store can upload at most 1,000 videos in a week and that the Files page takes at most 200 files per upload. Shopify's developer page for product media gives the per-file limits: 1 GB, 10 minutes and up to 4K, in MP4, MOV or WebM, and it lists YouTube and Vimeo as external video sources. Whether external videos count toward the hosted cap is not stated on the pages I read, so check before you rely on it. The weekly cap has its own batch plan and the per-file rules are in Shopify product video limit.

How do I budget Sume clips against the cap?

Spend slots on products, not variants: one clip per product, reused across its variants, uses a tenth of the slots of one clip per variant for a product with ten. Keep the files small by asking for what the page needs. Video Router says Sume's Auto model defaults to 720p and 8 seconds, and GET /v1/videos/models lists the resolutions and durations each model accepts, so a 6-second 720p clip does not have to be a 12-second 1080p one.

If a clip is too long, Video trim cuts a range into a new MP4 for $0.02 per job (the docs say to confirm the live price in GET /v1/catalog), and an optional output of { width, height, fps } between 256 and 2160 pixels conforms the size. When a clip is replaced, remove the old one and re-check your count against the plan cap. Send one Idempotency-Key per product so a retried job never makes a second clip that takes a second slot.

LIMITS = {"Basic": 250, "Grow": 1000, "Advanced": 5000, "Plus": 50000, "Enterprise": 100000}

def headroom(plan, hosted_videos, models_3d, new_clips):
    free = LIMITS[plan] - hosted_videos - models_3d
    return free - new_clips

# A Basic store with 180 videos and 12 models adding 40 clips:
print(headroom("Basic", 180, 12, 40))  # 18 slots left

What to do before a launch

Count the hosted videos and 3D models you already have, subtract them from your plan's cap, and size the Sume batch to the remainder with a margin. A batch larger than the free slots can stall partway through, after the clips are already made and paid for. Plan the cap first, then the weekly upload rate, then the per-file limits.

The per-product ceiling of 250 images, 3D models or videos is a separate limit and rarely the one that bites for clips: a product that needs one clip and a few photos is nowhere near it. The store-wide count and storage are the ceilings that grow with the catalog, which is why they are the ones to track.