Loop recording means the camera never stops and never fills up. It writes video in fixed-length segments, and when the card is full it overwrites the oldest segment that is not protected. That is the whole mechanism. The consequences are what people get wrong: a loop is not a backup, the segment you care about has a shelf life measured in days, and a camera that loses power mid-segment can lose the file it was writing.
Why segments instead of one long file
A camera could in principle write one enormous file and trim the front of it. Nobody does, for three reasons. Deleting from the front of a file is expensive on flash storage. A single corrupted file would take the whole ride with it. And overwriting in fixed blocks is what flash memory is good at.
So the camera picks a segment length — one, three or five minutes are the usual options — and treats the card as a ring of those segments. When it reaches the end it goes back to the beginning. Shorter segments mean less loss if one file is damaged and more files to sift through. Longer segments mean fewer, larger files and more at risk each time something goes wrong. Three minutes is a reasonable default for most riders; one minute suits anyone who expects to be pulling clips out often.
The write speed problem, which is where loops actually fail
Continuous video is a sustained sequential write, and it does not tolerate pauses. The SD Association is explicit that recording video requires a constant minimum write speed to avoid dropped frames, which is why the Speed Class marks exist at all: Speed Class 2, 4, 6 and 10, UHS Speed Class 1 and 3, and Video Speed Class V6 through V90, each guaranteeing a minimum sequential write rate under the conditions defined in the standard.
Two things follow. First, a card whose class is below what the camera needs will drop frames rather than fail outright, so the footage looks fine until you examine a fast-moving moment and it is a smear. Second, the guaranteed speed applies to writing into unfragmented free space. The same source notes that repeated deletion and writing fragments the card, that fragmented writing is slower, and that reformatting may be needed to restore the rated performance. A loop recorder does nothing but repeatedly delete and write, so this is its normal condition, not an edge case.
Bus mode matters too, because a card can only deliver its class if the connection is fast enough to carry it. The SD Association's bus speed overview sets out which bus modes each class needs. In practice this means matching the card to what the camera supports, rather than assuming the fastest card available is automatically better. Card selection is covered properly in our guide to memory cards for motorcycle cameras.
What protection actually does
| Mode | What it writes | What overwrites it |
|---|---|---|
| Normal loop | Continuous segments while powered and recording | Itself, oldest first, once the card is full |
| Impact-triggered event | The current segment, often plus the one before | Nothing, until the event folder is full |
| Manual lock | The current segment, from a button or app press | Nothing, until the event folder is full |
| Parking or motion | Short clips when the sensor triggers with the bike off | Its own separate loop, usually a capped share of the card |
| Pre-record buffer | A few seconds held in memory before the trigger | Continuously, until a trigger commits it to the card |
Protection is the only thing standing between an incident and the loop. It works by moving or flagging the segment so the overwrite logic skips it, which is why the event folder eventually fills and why a full event folder can silently stop protecting new clips. That failure mode is the single most common way riders lose footage they thought was safe, and it is covered in our guide to dash cam file management.
Protection also assumes the file got finished, and that is the second way footage disappears. A video file is not complete until the camera closes it. Cut the power in the middle of a segment and you get a partial file that some players will open and some will not, or an entry in the file table pointing at data the camera never finished writing. Cameras handle this differently — some recover the partial segment on next boot, some discard it.
On a motorcycle this matters more than in a car, because the accessory circuit is more likely to drop. Three situations cause it:
- Ignition off mid-segment. Normal, and handled well by cameras with a small internal reserve that lets them close the file. Cameras without one lose the last segment routinely.
- A voltage dip during cranking if the camera is on a circuit that sags. The camera reboots and the segment in progress is lost.
- A connector working loose under vibration, which produces the same result intermittently and looks like a card fault.
The last segment before an incident is often the one you want, and a crash is exactly the event most likely to interrupt power. That is the argument for a camera that closes files cleanly on power loss, and for making sure the power feed is solid in the first place — see wiring a riding system safely for the general principles, and leave any work involving the main harness or a CAN-connected circuit to a technician, following your owner's manual.
Setting loop length and sensitivity for how you actually ride
Two settings do most of the work, and the right values depend on your roads rather than on any universal recommendation.
Segment length. Shorter is better if you pull clips often or ride somewhere with a lot of incidents worth flagging. Longer is better if you mostly want a passive record and dislike sorting files. If you are unsure, three minutes and leave it alone.
Impact sensitivity. This is where motorcycles differ sharply from cars. A bike transmits road shock directly into the camera, so a sensitivity that works in a car will lock a clip at every expansion joint. The symptom is an event folder full of nothing, and the consequence is that the folder fills and stops protecting real events. If you are getting more than the occasional false lock, reduce it. The cost of reducing it too far is that a genuine low-speed impact might not trigger, which is why the manual lock control matters — a button or an app press you can use deliberately.
Parking mode is the third variable and the one with a real trade-off. It records while the bike is unattended, which is the reason many riders fit a camera at all, and it draws power from the battery to do it. Any parking setup needs a low-voltage cutoff so the camera stops before it leaves you unable to start the bike, and the threshold should be set with the bike's own battery condition in mind rather than left at a default. Our overview of whether a motorcycle dash cam is worth it covers where that value shows up, and a weather-sealed motorcycle camera is only as reliable as the circuit feeding it.
What loop recording does not give you
It is not an archive. Anything you want in a year has to be off the card. It is not proof of a negative either — a clip that shows nothing unusual is weak evidence that nothing happened, because the camera has one field of view and a motorcycle incident often develops outside it. And it is not a substitute for a rear channel: front-only footage of a rear-end impact shows the road ahead and nothing that matters, which is the argument set out in our comparison of front and rear motorcycle dash cam setups.
FAQ
Will loop recording overwrite my crash footage?
Only if the clip was never protected, or if the event folder was already full and the camera stopped protecting new clips. Check that the impact sensor actually triggered, and pull the file off the card the same day rather than trusting the protection to hold indefinitely.
What loop length should I use?
Three minutes suits most riders. Choose one minute if you extract clips frequently and want to move small files around, five minutes if you rarely touch the card and prefer fewer of them. The length has no effect on video quality.
Why is my footage stuttering or dropping frames?
Usually the card cannot sustain the write rate, either because its speed class is below what the camera needs or because the card is fragmented from months of overwriting. Reformat in the camera first. If it persists, the card is the wrong specification or is wearing out.
Does loop recording wear out the memory card?
Yes. Constant rewriting is the hardest workload a card sees, and cards in dash cams have a working life measured in months to a couple of years depending on hours recorded. Replacing the card before it fails is cheaper than discovering it failed during the ride that mattered.
Why did I lose the last few minutes before I switched off?
The segment in progress was not closed. Some cameras hold enough reserve power to finish the file when the ignition goes off, and some do not. If it happens on every ride, that is the explanation. If it happens intermittently, look at the power feed and the connector instead.
