Doberman

Continuous or motion-only recordingthe trade-off that mostly stopped existing

Recording only on motion used to be the obvious way to stretch a hard drive. Modern compression has changed the sums, and the gaps were always worse than they looked. Here is the honest comparison.

The quick answer

Motion-only recording was the right answer when storage was the expensive part. It mostly is not any more. Modern compression already collapses a still scene to almost nothing, so continuous recording now costs far less than people assume while motion-only still carries the same old problem: it decides, in the moment, what was worth keeping, and it decides badly more often than the marketing suggests. The saving is also the inverse of how busy the scene is, which means it saves you least on exactly the cameras that matter most.

What this guide covers

  • How much storage motion-only actually saves, and why the honest answer is a formula.
  • Pre-buffer maths: why five seconds of buffer is not five seconds of footage.
  • What detection documentably misses, in the manufacturers own words.
  • Why every filter you add to stop false alarms also creates a blind spot.
  • How smart codecs quietly dissolved the trade-off this argument was built on.
  • Where continuous recording is actually required, and where that claim is made up.

The two modes, side by side

The storage row is the one everybody looks at. The last two rows are the ones that matter when something has actually happened.

Storage used

Continuous
Everything, though a smart codec cuts a still scene dramatically
Motion-only
Inverse of how much the scene moves. Saves least where most happens

The start of an incident

Continuous
Always there
Motion-only
Pre-buffer only, and the detection delay eats into it

Someone standing still

Continuous
Recorded
Motion-only
Not detected in standard modes

Gaps in the record

Continuous
None, so a gap means a fault
Motion-only
Constant and expected, so a fault looks normal

Explaining it later

Continuous
Nothing to explain
Motion-only
The detection settings have to be produced alongside the footage

By the Doberman install team

CCTV system designers & installers, Leicester

Last reviewed September 2026

What motion-only actually saves

There is a clean way to think about this and it removes all the guesswork. The storage saving from motion-only recording is the inverse of the motion duty cycle. If something is moving in shot a fifth of the time, you store about a fifth as much, so your retention stretches roughly five times. If something is moving half the time, you halve it.

Two published worked examples bracket the sensible range. One video management vendor sizes its own storage guidance on motion occurring 20 per cent of the time, which it says reduces load and wear on the storage system by 80 per cent. An independent industry recording guide works its example at a 33 per cent motion factor, needing roughly one third of the storage. Both are design assumptions rather than measurements, and neither is a promise about your driveway.

Which leads to the part nobody puts on a sales page. The same industry guide notes that in constantly busy scenes the savings from motion recording are minimised. Read that with the formula and the conclusion is uncomfortable: motion-only pays best on the camera watching an empty side return, and pays almost nothing on the camera watching the front of the house. You are being sold a saving that shrinks in proportion to how much you needed the camera.

You can see what continuous recording costs on your own setup with our CCTV storage calculator, and our guide to how long CCTV footage lasts covers the other three things that set your retention.

Five seconds of pre-buffer is not five seconds of footage

Every motion-triggered system keeps a rolling few seconds in memory so the recording can start slightly before the trigger. That is the pre-buffer, and it is the feature that is supposed to make motion-only safe. It is smaller than it sounds.

Typical defaults sit at three seconds on one major video management platform and five seconds in a leading camera manufacturer's own worked example. Now put that next to a second number from the same manufacturer's object detection documentation: objects need to move within the scene for at least two seconds before they are classified. Subtract one from the other. A five second buffer, minus two seconds of detection delay, leaves you about three seconds of genuine pre-event footage.

Three seconds is not much of a run-up to an incident. It does not contain the walk up the drive, the look through the window, or the second person waiting at the gate.

Two further details make it worse rather than better. The buffer is not guaranteed: the documentation states plainly that the pre-buffer time will be shortened automatically if there is insufficient memory when the recording starts. And you cannot simply turn it up. On that major platform the memory pre-buffer is capped at 15 seconds, and anything longer has to be disk based, which the vendor notes keeps the load on the storage system permanently high. At that point you are writing continuously anyway and have given up the saving.

The manufacturer's own advice, worth reading twice if you are setting one of these up, is to configure the pre-trigger so the recording includes the time the object moved in the scene before triggering the alarm. In other words: the default will not do it.

Not sure what your system is set to?

Doberman can check what your cameras are actually recording, what the detection zones cover, and what that means for how far back you can look.

What detection misses, in the manufacturers own words

This is not a criticism from outside the industry. Camera manufacturers document these limits openly, in the technical pages installers are supposed to read and homeowners never see.

  • Objects approaching in a straight line towards the camera need to move a longer distance before they are detected than objects crossing the view. That is precisely the path someone takes walking up to your front door.
  • Standard AI detection does not detect stationary people or vehicles. Someone who stops and stands still, or a car that parks up, stops producing events.
  • There is a minimum size. One manufacturer gives a human minimum of 4 per cent of image height, then recommends at least 8 per cent to minimise missed detections. The gap between the stated minimum and the recommended figure is the manufacturer telling you the minimum is not safe.
  • Detection needs people roughly upright, and accuracy drops when objects are only partially visible or the scene is crowded with overlapping objects. Crouching, crawling or moving low behind a wall or a parked car is a documented miss.
  • Small and distant objects might not be detected at all.
  • Heavy rain or snow reduces both detection distance and accuracy.
  • Excessive camera vibration causes false alarms rather than missed ones.

None of this means detection is bad. It means detection is a filter, and every filter has a pass band. The question is whether you want your evidence decided by one.

The false alarm paradox

Anyone who has lived with a motion-triggered camera knows the other failure, which is the opposite one. Headlights sweeping a wall, a shadow crossing a lawn, foliage moving in wind, a cat, a spider setting up shop in front of the lens overnight.

Manufacturers deal with this by giving you filters: one for short-lived objects, aimed at light beams from a passing car and quickly moving shadows; one for swaying objects, aimed at foliage, flags and their shadows; one for small objects, aimed at small animals. You can also shrink the detection area and drop the sensitivity, which is the standard advice for the spiderweb problem.

Here is the part that follows logically and that nobody states. Every one of those filters is a category of real event you have taught the system to ignore. Turn on the short-lived object filter and you have told it to disregard brief movement. Turn on small objects and you have set a size below which nothing is real. Shrink the detection area to stop the tree triggering it, and you have created a corridor of your property where nothing will ever be recorded. The documentation is even explicit that short-lived-object filtering can delay event detection, which eats further into the pre-buffer maths above.

That inference is ours, drawn from the documented behaviour rather than quoted from it. The filters and what they target are documented. What they cost you is arithmetic.

Detection zones deserve a specific mention because they are invisible once set. On a mainstream recorder motion detection ships enabled across the whole frame, and narrowing it is something an installer chooses to do. An object only triggers when part of it is inside the include area. So an incident that begins outside the zone, which is where approach, observation and preparation happen, is simply never recorded, and the pre-buffer reaches back only a few seconds from the moment of entry.

Smart codecs quietly ended this argument

The whole continuous-versus-motion debate assumes that recording a still scene costs the same as recording a busy one. On a modern camera it does not, and that is what has changed.

Smart codecs watch the scene and compress it according to what is happening in it. When nothing is moving, the camera sends the bandwidth-heavy reference frames far less often, and in a completely static scene the effective frame rate between those frames drops to almost nothing, snapping back the instant motion appears. You are still recording continuously. You are simply not spending much to record nothing.

The measured effect is large. One manufacturer publishes per-scene reductions for constant recording ranging from 25 per cent on a well-lit scene with occasional motion, through 73 and 85 and 90 per cent on various real scenes, up to 99.7 per cent on a night-mode scene with very infrequent motion. Those are vendor figures with vendor caveats, and the reduction varies with light, movement and scene detail. Even discounted heavily, they change the decision.

The same manufacturer states the conclusion outright in its own white paper: the technology enables continuous recordings because of the low bitrate used for static scenes, and it reduces the number of missed triggers by allowing longer recording segments for each motion-triggered event without generating excessive data. When the company selling the compression tells you it makes continuous recording viable, the storage argument for motion-only has largely gone.

There is a wrinkle worth knowing if someone quotes you a storage figure. Manufacturer guidance warns that bitrate limits are often set to a very low default, that most storage calculators base their sums on that low limit, and that systems get built with insufficient storage for high quality recording as a result. A quoted retention figure is only as good as the bitrate assumption under it.

What happens when the footage has to stand up

This is the argument that gets left out entirely, and it is the strongest one.

Government guidance on police requirements for CCTV is blunt that quality should not be reduced to fit the available storage capacity of the system, and that recordings should cover a sufficiently long period to assist investigations. There is no fixed admissibility threshold, and a court decides on relevance and reliability.

Reliability is where a gapped record gets awkward. The national police framework for video based evidence lists, as a specific risk, insufficient recording of system settings including overwrite times and motion detect settings, and gives the consequence as wasted investigative time, relevance being raised at court, and loss of evidence. Put plainly: the gaps in a motion-only record are only interpretable if somebody can produce the detection configuration that created them. A continuous record needs no such explanation, and a gap in one means a fault rather than a judgement call.

If you do end up handing footage over, how you export it matters at least as much as how you recorded it. That is covered in our guide to exporting CCTV footage for the police.

Is continuous recording ever required

No national UK law requires CCTV at all, and none specifies a recording mode. Where a continuous obligation exists, it exists because a licensing authority attached it as a condition to an individual premises licence.

It genuinely varies. Westminster's model conditions require that the CCTV system shall continually record whilst the premises is open for licensable activities and during all times when customers remain on the premises, with recordings stored for a minimum of 31 days. The City of London uses near-identical wording. Essex Police's model CCTV condition, by contrast, requires a recordable system of evidential quality, specified coverage, correct time and date stamping and 31 days of retention, and says nothing at all about recording continually.

All three publish the same warning about their own documents, which is the real lesson here. Westminster says its conditions are not standard conditions and should be used as a guide. Essex Police says they are not standard conditions it seeks to have applied to each premises of a certain type. So if you run a licensed premises, the answer is on your licence, not in an article.

On insurance, be sceptical. We looked for an insurer document, a policy wording or a trade body standard requiring continuous recording and did not find one. Some commercial policies require a working CCTV system as a condition of cover, which is a different thing. If someone tells you your insurer demands continuous recording, ask them to point at the clause.

Pulling the other way, data protection law asks you to record no more than you need, and to keep it no longer than necessary. That genuinely favours motion-only in some settings. It sits against the evidential case, and the thing that resolves the two is the purpose you installed the cameras for, which is also what the regulator says should set it.

About this guide

Who wrote this

Written by Doberman, a CCTV system designer and installer working with homes and small businesses across Leicester and Leicestershire. Recording mode is a decision made at commissioning that most people never revisit, which is why it is worth setting out properly once.

How this guide was produced

The detection limits, pre-buffer figures and compression measurements are taken from manufacturer and platform technical documentation rather than from review sites: Axis Communications' object analytics and video motion detection documentation and its Zipstream white paper of July 2026, and Milestone Systems' storage architecture paper. The evidential material comes from GOV.UK police requirements for CCTV systems and the NPCC Framework for Video Based Evidence. The licensing conditions are quoted from the published model conditions of Westminster City Council and Essex Police, both read directly. Naming those manufacturers is a citation, not a recommendation of a particular brand.

What we have deliberately not said

No figure is given for how much of the day a typical garden or road is in motion, because no primary source for it exists and the numbers repeated online are untraceable. No insurance requirement is asserted. Vendor claims of 95 per cent storage reduction and vendor false alarm rates are left out, in the first case because the same page contradicts itself and in the second because no test conditions are given.

Disclosure

We install CCTV for a living, and we specify continuous recording on most jobs, so this page argues for something we already do. The reasoning and the sources are laid out above so you can check the argument rather than take our word for it, and the honest counterweight, the data minimisation duty, is in the section above rather than buried.

Common questions

Does motion-only recording really save that much storage?

It saves exactly as much as the scene is still. The multiplier is the inverse of how much of the day something is moving, so a camera seeing movement a fifth of the time stores about a fifth as much, and a camera pointed at a road saves almost nothing. One video management vendor works its own examples at 20 per cent motion, giving an 80 per cent reduction. An independent industry guide uses 33 per cent, giving a threefold saving. Both are design assumptions rather than measurements of your garden.

How much footage do you lose before a motion recording starts?

More than the pre-buffer setting suggests. Typical pre-buffer defaults are three to five seconds. But AI object detection documentation states that objects need to move within the scene for at least two seconds before they are classified, so a five-second buffer minus a two-second detection delay leaves roughly three seconds of genuine pre-event footage. On a major video management platform the memory pre-buffer is capped at 15 seconds, and going beyond that means writing to disk continuously, which removes the saving you were chasing.

What does motion detection actually miss?

Manufacturer documentation is candid about it. Someone walking straight towards the camera has to travel further before being detected than someone crossing it, which is the exact approach path to a front door. Stationary people are not detected at all in standard modes, so somebody standing still produces nothing. Small or distant figures fall below the minimum object size. Crouching, partial visibility, crowding, heavy rain and snow all reduce accuracy.

Is continuous recording required by law in the UK?

No. There is no national law requiring CCTV at all, let alone a particular recording mode. Where an obligation exists it is a condition attached to an individual premises licence, and it varies by authority. Westminster and the City of London both publish model conditions requiring the system to continually record while the premises is open. Essex Police's CCTV model condition contains no such requirement. All of them state they are guidance rather than standard conditions.

Do insurers require continuous recording?

We could not find a single insurer document, policy wording or trade-body standard that requires it, and we looked. Claims of the form "insurers require CCTV" trace back to security installer blogs rather than to underwriters. Some commercial policies do require a working CCTV system as a condition of cover. We have found nothing that specifies the recording mode, so treat anyone who tells you otherwise as needing to show you the clause.

So which should I choose?

On a modern system with a smart codec, record continuously and stop thinking about it. The compression now does what motion-only used to do, without the gaps: a camera manufacturer measured reductions from 25 per cent on a well-lit busy scene up to 99.7 per cent on a quiet night scene, for constant recording. Motion-only still earns its place where storage is genuinely fixed and the scene is genuinely still, such as an indoor store room. It is a poor choice on an entrance.

Want a system set up to catch the whole incident?

We visit, map the blind spots, and quote one fixed price on the spot.