The short answer
Thirty days is the common starting point for commercial video retention, and most commercial systems are sized for it. The right number comes from the obligations that apply to the property: insurer and lender requirements, public records and records retention duties for public agencies, housing program rules, license conditions for regulated premises, and the duty to preserve footage once a claim or investigation is reasonably foreseeable. California licensed cannabis premises are one of the few categories with a length written into regulation: a minimum of 90 calendar days under California Code of Regulations title 4, section 15044. Once the policy is set, retention becomes a storage calculation. Multiply camera count by bitrate, hours recorded and days, then adjust for H.265, variable bitrate and motion based recording.
| Common starting point | 30 days for commercial properties |
|---|---|
| Cannabis premises | 90 calendar days minimum, 4 CCR 15044 |
| City departments | Gov. Code 34090.6 destruction after one year |
| Storage rule | 30 days at 1 Mbps is about 324 GB per camera |
| Audio | Microphones off unless counsel reviews the use |
| License | CSLB #472017, C-7 Low Voltage Systems |
Why 30 days is the common starting point
Most commercial video retention policies start at thirty days. It’s a reasonable default, and the reason has nothing to do with regulation. Most incidents that anyone pulls footage for get reported within a few weeks: a slip and fall, a package theft, a vandalized vehicle, a dispute between employees, a break-in discovered the next morning. Thirty days covers that window with some margin, and at typical commercial camera counts it’s affordable.
Several things push retention longer: a lender or insurer that names a period in writing, a public agency records schedule, a housing program requirement, a licensing condition, an anchor tenant lease exhibit, or a history of claims that surface late. A couple of things push it shorter: a bandwidth or storage constraint that can’t be solved economically, or a deliberate privacy decision to keep footage no longer than the operation needs.
The number should be a policy decision the owner makes, ideally with counsel, and then carries out as a storage calculation. It shouldn’t be a technical default inherited from the recorder’s factory settings. A system left to overwrite at 14 days because that’s what fit on the drives still has a retention policy. The drive capacity just chose it instead of the owner.
The obligations that set the retention period
| Driver | Who it applies to | What it usually requires | Where to confirm it |
|---|---|---|---|
| Insurance policy or lender covenant | Owners with a policy or loan that names security systems | Commonly 30 days, sometimes 60 or 90 for higher risk classes | The policy or loan document, in writing from the carrier or lender |
| Public records and agency retention schedules | State and local public agencies | No universal length; the agency’s adopted records retention schedule governs, and existing footage that is a public record is subject to the California Public Records Act at Government Code section 7920.000 and following | The agency’s adopted schedule and its counsel |
| Housing program requirements | HUD assisted and other subsidized properties | Set by the program, the regulatory agreement, the management plan or the owner’s own policy rather than one federal number | The regulatory agreement, management plan and program guidance |
| State licensing conditions | Regulated premises, such as licensed cannabis operations | A specific minimum written into the licensing agency’s regulations | The regulations for that license type, verified at design time |
| Litigation hold and preservation duty | Any party once a claim or investigation is reasonably foreseeable | Preserve the relevant footage immediately, regardless of the routine period | Counsel; the hold overrides the schedule |
| Labor agreements and employment policy | Employers whose agreements address surveillance | Notice, access and retention terms as negotiated | The agreement and employment counsel |
| Lease and brand standards | Landlords, anchor tenants, franchise operators | Whatever the lease exhibit or brand standard specifies | The lease exhibit or franchise operations manual |
Two of these get missed a lot. The first is the lender covenant, because it lives in a loan document nobody on the facilities side has read. The second is the preservation duty, because it isn’t a retention setting at all. It’s an obligation to stop the normal overwrite for specific footage as soon as a claim becomes foreseeable. A property with a perfectly compliant 30 day policy can still lose the case if the relevant clip was overwritten on day 31 after the owner knew a claim was coming.
California specifics worth checking
There’s no single California statute that sets a retention period for commercial video surveillance. Several specific programs do set one, though, and a property can fall under one without realizing it.
Licensed cannabis premises are the clearest example. Under the Department of Cannabis Control regulations at California Code of Regulations title 4, section 15044, surveillance recordings must be kept for a minimum of 90 calendar days. So any design for a licensed cultivation, distribution, manufacturing or retail premises should be sized to that floor, not to a 30 day default.
Public agencies work differently. For a city or city and county department, Government Code section 34090.6 permits destruction of recordings of routine video monitoring after one year, with the approval of the legislative body and the written consent of the agency attorney. The section defines routine video monitoring to include building security recording systems. Recordings that are evidence in a pending claim or litigation are excepted. Counties, special districts and state agencies work from their own adopted records retention schedules, so check the schedule instead of assuming. On agency projects, settle this before the recorder is sized. Our government and public works page covers the other procurement items that come with agency work.
For everyone else, the retention number is set by contract and policy. That isn’t a loophole. It means the obligation comes from the insurer, the lender, the lease, the program or the owner’s own written policy, and each of those is worth reading.
Storage math: from retention policy to terabytes
One simple conversion turns a retention policy into capacity. A 1 Mbps stream running continuously writes about 10.8 GB a day. So the raw requirement is bitrate times 10.8, times camera count, times retention days.
The table below uses these planning assumptions: H.265 compression, 15 frames per second, continuous 24 hour recording, moderate scene motion, decimal terabytes, and raw video before array parity and free space. Add roughly 20 to 25 percent of installed capacity on top for parity and headroom. Real bitrates come from the manufacturer’s calculator for the specific model and scene, and you should swap those figures in before anyone writes a purchase order.
| System | 2 MP cameras at 2 Mbps | 4 MP cameras at 3 Mbps | 8 MP cameras at 6 Mbps |
|---|---|---|---|
| 8 cameras, 30 days | 5.2 TB | 7.8 TB | 15.6 TB |
| 16 cameras, 30 days | 10.4 TB | 15.6 TB | 31.1 TB |
| 24 cameras, 30 days | 15.6 TB | 23.3 TB | 46.7 TB |
| 24 cameras, 60 days | 31.1 TB | 46.7 TB | 93.3 TB |
| 24 cameras, 90 days | 46.7 TB | 70.0 TB | 140.0 TB |
Two of those assumptions do a lot of the work in the table, and two other settings can move the result either way. Check each one against the project before you treat a figure as a budget.
- H.265 is assumed. On most scenes it roughly halves bitrate compared with H.264 at the same visual quality, so a fleet that can’t run it will need close to double the figures above. Confirm that the recorder and every camera support it, because a mixed fleet falls back to the lowest common codec.
- Fifteen frames per second is assumed. Storage scales almost linearly with frame rate, so a project specified at 30 fps roughly doubles the table, and one that accepts 10 fps takes about a third off it. Fifteen frames per second rarely costs an investigator anything useful.
- Variable bitrate with a quality target lets quiet scenes drop to a fraction of the ceiling while busy scenes keep their detail, so the real number comes in below the table. Constant bitrate wastes storage on an empty corridor at three in the morning and pushes the number above it.
- Motion based recording isn’t assumed here, because the table is sized for continuous 24 hour recording. It helps a lot on cameras that see nothing overnight, and very little on a busy lobby or a windy exterior view where trees keep triggering it. Avoid sizing a whole system as if every camera benefits.
None of those settings moves the total as much as adding a camera or raising the resolution, so settle the count first. Our guide on how many security cameras a building needs walks through the method.
Why calculated retention and real retention differ
The retention a system delivers often differs from the retention it was designed for, and it usually falls short.
Bitrate assumptions are the main cause. A parking lot camera watching an empty lot at 2 a.m. produces very little data. The same camera in wind, rain or heavy snow produces a great deal, because noise and motion both raise bitrate. Cameras facing traffic, foliage or a busy corridor run above their planning bitrate all day. On many models, infrared at night adds noise, which raises bitrate too. Two cameras of the same model on the same recorder can differ by a factor of three based on the scene alone.
The rest of the causes are operational. Cameras get added and nobody resizes the array. Someone raises a camera from 15 to 30 frames per second to chase a detail problem. A firmware update changes the default encoder profile. A drive fails, and the array runs degraded with less usable capacity.
The fix is more a habit than a design change. Two weeks after the system goes live, open each camera, note the oldest recording available, and compare it to the policy. Adjust bitrate ceilings, frame rate, recording schedule or capacity while the project is still open, and record the verified retention in the closeout package. Then repeat the check every year. That’s one of the items a service and maintenance agreement should spell out. Where the recording lives also changes how you correct it: adding capacity to an on-premise recorder is a purchase order, while cloud retention is a subscription tier. Our guide on where recorded video should live compares those options.
Audio is a separate decision in California
Video retention and audio retention aren’t the same question, and the answers are usually different.
California treats the recording of private conversations differently from video. Penal Code section 632, part of the California Invasion of Privacy Act, makes it unlawful to intentionally record a confidential communication without the consent of all parties to that communication. A camera in a lobby or corridor may record conversations that participants reasonably believed were private, and a video surveillance sign doesn’t resolve consent for audio.
For that reason, microphones on commercial camera systems are commonly left disabled unless the owner’s counsel has reviewed the intended use and the owner has decided how notice and consent will be handled. Cameras often ship with microphones enabled by default, so turning them off is a deliberate configuration step. The setting belongs in the closeout documentation for every camera, so the owner can show what was and wasn’t recorded. Our security camera systems page describes how that’s documented.
Where audio has a real purpose, such as an intercom station or a call point, it’s generally handled as a live intercom function rather than a continuously recorded stream. That keeps the question narrower.
Don’t keep footage longer than the policy requires
There’s a practical case for the shortest retention that meets your obligations, and it has nothing to do with drive cost.
Every extra day of retained video is more material that can be requested in discovery, requested under a public records law, exposed in a breach of the recording platform, or misused by someone inside the organization. A property that keeps 365 days of footage for no reason has built a year long, searchable record of where residents, employees and visitors went, and it may be asked to produce it. Residents in multifamily and affordable housing are especially sensitive to this. A written policy that states the retention period and who may review footage is easier to defend than an open ended archive.
A workable policy covers four things: the retention period and the reason for it, who’s authorized to review footage and under what circumstances, how an export is requested and logged, and how a preservation hold is placed when a claim becomes foreseeable. Writing it down costs very little, and it gives the owner a clear way to explain what the camera system does and why.
Next step
Send us the camera count, the resolution you’re planning and the retention the property has to meet. We’ll send back the storage sizing and a recording recommendation with the assumptions shown. You can start at request a bid. General contractors bidding Division 28 can find our prequalification packet on the for general contractors page.