A 12 wedding season at ProRes 422 writes about 7.94 TB of raw footage. I rebuild the storage plan from the camera hour up, with the backup copies counted.
The Quote On The Desk
The scene was a desk in Multan the night before wedding season opened: two cameras charging, a stack of memory cards in a rubber band, a laptop, and a quote for twelve weddings that my friend, a wedding videographer, was about to send to a venue manager.
I had gone over to help him price the season, and the storage line in his quote stopped me. He had allowed a few hundred gigabytes for the whole season. He had reached that figure by multiplying the size of a delivered wedding film by twelve, which felt tidy and was wrong by more than two hundred times.
Here is the answer I put together with him that night, and the one this guide rebuilds step by step. Raw capture, not the delivered film, sets the storage bill. Two cameras shooting ProRes 422 at 1080p write about 132 GB for every hour of event coverage. Across a twelve wedding season at ten camera hours a wedding, that is about 7.94 TB of raw footage, and about 15.88 TB of drives once a single backup copy exists. Every figure below is the multiplication behind those totals, at rates any shooter can swap for their own.
Start From The Camera Hour
Apple's published target rate for ProRes 422 at 1080p is 147 Mbps. Run that through the only formula storage planning needs, bitrate times seconds divided by eight, and one hour of footage weighs 66.15 GB. His main camera alone therefore fills a 256 GB card in a little under four hours of recording. A 128 GB card holds a little under two hours. On a wedding day with a baraat, a rukhsati and everything between, card capacity is not an errand to run mid-event; it is a number to know before the first card goes in.
I recognized his mistake because I had made its smaller cousin in my own course work, pricing a shared drive from the size of finished lessons instead of the masters behind them. The delivered file is the tip of the project. Under it sits every take, every angle and every false start, all written at camera bitrates. The video file size calculator exists for this exact translation: enter the rate a camera writes, read the gigabytes per hour, and plan in hours instead of hopes.
He had priced the wedding films his clients would watch. He had not priced the footage his cameras would actually write.
One Wedding On Paper
His typical wedding runs two cameras: the main camera records about six hours across the day, the second camera about four. Ten camera hours, at 66.15 GB per hour, is 661.5 GB of raw footage for one wedding. Against that, set the film the couple receives: a 45 minute edit delivered at the 1080p upload rate of 8.32 Mbps weighs about 2.81 GB. The delivered film is less than half of one percent of the raw day. That gap, between 2.81 GB and 661.5 GB for the same event, is the entire planning error in one comparison.
The codec decision moves the raw figure hard, which is why the season plan has to name a capture format and not just a camera count. At ProRes 422 LT, 102 Mbps, an hour weighs 45.9 GB and the wedding lands at 459 GB.
At ProRes 422 HQ, 220 Mbps, the hour weighs 99 GB and the wedding reaches 990 GB. A high-bitrate H.264 camera setting at 100 Mbps writes 45 GB an hour, close to the LT line. In The 1080p Size Article I showed the same spread for a single ten minute file; here it is wearing a season's worth of consequences.
The Season Table
Raw footage per wedding at ten camera hours, by capture format
Data: format bitrate times 36,000 seconds (ten camera hours) divided by eight, using Apple's published ProRes target rates.
Plan line
Per wedding
Twelve weddings
Raw footage, ProRes 422, two cameras
661.5 GB
7,938 GB, about 7.94 TB
Working copy plus one backup
1,323 GB
15,876 GB, about 15.88 TB
Delivered films at 1080p
2.81 GB
33.7 GB
His original storage line
priced from delivered size
short by a factor of about 235
On a shelf, the two-copy plan looks like four 4 TB drives: a working pair holding one copy of the season between them, and a backup pair holding the second. That shelf is what the quote has to carry. Priced as its own line, storage stops looking like an overhead the videographer absorbs and starts looking like what it is, a material the job consumes, no different from fuel for the generator.
The backup line is not padding. The standard guidance for irreplaceable files is the 3-2-1 rule: three copies, on two different types of media, with one copy off site. Wedding footage is the definition of irreplaceable; a hard drive failure in week nine cannot be reshot.
My friend's workable version of the rule is the working drive, a backup drive that lives at his home, and finished projects copied to a drive at his brother's house across town. Three copies of everything would take the season past 23 TB, so he applies the full rule to delivered films and current projects, and two copies to raw archives. That is a judgment call, made with the numbers visible, which is all a plan can ask for.
Pricing Storage Into The Quote
For a videographer or photographer pricing a season, the deliverable from that night is a repeatable routine. Count camera hours honestly, including the second camera and the getting-ready footage nobody lists. Convert at the capture format's rate, using the calculator, never at the delivery rate. Multiply by the number of events, then by the copies the backup rule demands. The result is a storage figure that belongs in the quote as its own line, next to transport and editing, instead of hiding inside a margin that twelve weddings will eat by November.
The same method scales down to a solo shooter with one camera, and it is worth running manually once to feel the shape of it. A single camera shooting ProRes 422 LT for five hours at a smaller event writes 45.9 times 5, which is 229.5 GB.
Across eight such events in a season, that is 1,836 GB of raw footage, and about 3.67 TB of drives with one backup copy. No spreadsheets, no software: hours times the format's gigabytes per hour, times events, times copies. If the total surprises the person holding the calculator, the surprise arrived at the right moment, before the season did.
One more variable belongs in the same conversation with the client: capture format is a quality and storage decision at once. ProRes 422 gives the editor the most forgiving footage and the heaviest season; the LT line nearly halves the drives at a small quality cost most wedding films never show. And how the camera meters its own bitrate, constant against variable, changes real card life on the day, which is the subject of The CBR Vs VBR Article. Plan the season from the camera hour outward, and storage stops being the line that ruins the quote.
Questions People Ask About This Page
How Much Storage Does One Wedding Take?
At ProRes 422 at 1080p, one camera hour weighs 66.15 GB. A two camera wedding with about ten camera hours across the day therefore writes about 661.5 GB of raw footage, before any backup copy. The delivered 45 minute film at 1080p weighs only about 2.81 GB, which is why planning from delivered sizes fails so badly.
How Many Hours Fit On A 256 GB Memory Card?
At ProRes 422's 66.15 GB per hour, a 256 GB card holds a little under four hours of footage. At ProRes 422 LT, 45.9 GB per hour, the same card holds about five and a half hours. I divide card size by the format's GB per hour before every shoot day, using the calculator on this page.
Can I Plan Storage From The Size Of Delivered Wedding Films?
No. In the worked example in this article the delivered film is 2.81 GB against 661.5 GB of raw footage for the same wedding, a ratio of more than 200 to 1. A season priced from delivered sizes came up short by a factor of about 235. Plan from camera hours at the capture format's bitrate instead.
How Much Does ProRes 422 LT Save Against ProRes 422 Over A Season?
LT runs at 102 Mbps against 147 Mbps, so an hour weighs 45.9 GB instead of 66.15 GB. Across ten camera hours a wedding and twelve weddings, that is 5,508 GB against 7,938 GB of raw footage, a saving of about 2.43 TB before backup copies multiply both figures.
Facts, Checked Against Trusted Sources
Apple's ProRes documentation sets a target bit rate of about 147 Mbps for ProRes 422 at 1920 by 1080, which works out to 66.15 GB of footage per recorded hour. Source: Apple ProRes White Paper
The 3-2-1 backup strategy keeps three copies of important data, stored on two different media, with at least one copy off site, and it is the baseline Backblaze recommends for data that cannot be replaced. Source: Backblaze, cloud backup and the 3-2-1 strategy
Written By
Talha Kayani
Talha Kayani is the founder of Trivexa Digital, Multan, and the owner and developer of Ti-84calculator.com. A digital marketing specialist in SEO, social media and Meta Ads, he builds and personally tests every calculator and converter on this site before it goes live, so the figures you read here are the ones he trusts in his own daily work.