Dash Cam Loop Recording: How to Keep Important Footage From Being Overwritten

What is dash cam loop recording?

Rather than writing one enormous video file, a dash cam records in short sequential segments — commonly one, three or five minutes each, depending on the model and its settings. Segmenting keeps files manageable, limits the damage if a single file is corrupted, and makes it possible to reuse storage cleanly.

When the usable space on the card runs out, loop recording is what allows the camera to continue. Instead of stopping, it generally replaces the oldest normal, unlocked segment with the newest one, and keeps going.

VIOFO documents this directly for its cameras: loop recording runs automatically, and when storage is insufficient the camera overwrites the oldest files, while emergency recordings — triggered by a collision or manually by the driver — are locked so the loop does not reclaim them. Nextbase describes comparable behaviour, with older unprotected recordings replaced once the card fills.

Garmin’s guidance approaches the same problem from the preservation side: video you want to keep should be saved or protected from being overwritten, and transferred to a computer or external storage, because the memory card holds a limited amount.

The important caveat throughout this article: exact behaviour varies by manufacturer, model and configuration. Treat your own manual as authoritative for your own camera.

Why dash cam footage gets overwritten

Overwriting is not a malfunction. It is the expected outcome of writing continuous video to fixed storage. How quickly it comes around depends on a handful of variables that interact:

• Card capacity — the total space available for recordings, minus whatever the device reserves.
• Resolution and bitrate — higher-quality video consumes storage faster, and bitrate matters more than resolution alone.
• Number of channels — each simultaneous camera stream writes its own video.
• How much you drive — an hour a day and eight hours a day produce very different histories on the same card.
• Parking recording — if configured and powered, recording continues while the vehicle is off, consuming additional space.
• Locked and event files — protected clips occupy capacity that the loop cannot reclaim, shortening the normal recording window.
• Device and card settings — clip length, compression and any device-specific storage allocation.

Because of that, no honest guide can tell you that a dash cam holds “X hours” of footage. A four-channel system generally consumes storage faster than a single front stream, simply because it is writing more video — but the actual retention window on any given setup depends on bitrate, resolution, compression, card capacity and settings together. If you want to know your number, check your own card: look at the oldest file on it and see what date it carries.

Coverage trade-offs between one, two and four channels are a separate decision, covered in our guide on whether a 4-channel dash cam is worth it.

What does it mean to lock a dash cam clip?

Locking — also called protecting, or saving an event or emergency file — marks a clip so the loop does not reuse its space. There are usually two routes to it.

The first is automatic. A G-sensor measures sudden changes in motion, and when a reading crosses the configured threshold the camera attempts to lock the current clip as an event recording. The second is manual: a dedicated button, a touchscreen control or an app action that locks the current clip on demand.

Locked clips are typically stored differently from ordinary recordings — often in a separate event or emergency folder — and excluded from the normal overwrite cycle. That is genuinely valuable. It is also not the same as archival storage.

• Protected areas can have their own capacity limits, and some devices recycle the oldest protected files once that area is full.
• Locking depends on the device recognising the event, which is a settings-dependent judgement, not a guarantee.
• A memory card is consumable hardware — it can wear, develop errors or fail outright.
• A card can also be removed, lost, damaged or taken with the vehicle.

The durable step is exporting: copying the original file off the camera to storage you control. Locking buys you time. Exporting is what actually preserves the recording.

The evidence retention problem

A camera can record the right moment and still leave you without the file later.

In practice, footage goes missing in four recognisable ways.

The loop reaches it first. Nothing locked the clip, and by the time anyone thinks to look — often days later, when a claim, a letter or a dispute arrives — the segment has already been replaced by ordinary driving footage.

The impact never triggered a lock. Not every relevant event produces the force the G-sensor is configured to notice. A glancing contact, a near miss or a non-contact incident can pass without generating an event file at all.

The locked clip is missing the context. An event file usually brackets the moment of impact. But the useful material is often in the sequence before it — lane positions, signals, relative speeds — or in what happened immediately afterwards. If only the impact segment was locked, the surrounding clips may already be gone.

The storage itself failed. Continuous video writing is demanding, and VIOFO lists recording failures, gaps and corrupted files among the symptoms associated with unsuitable or worn cards. A card that has quietly degraded can leave you with unreadable files exactly when they matter.

Each of these is preventable, and none of them is prevented by owning a good camera alone.

How to protect dash cam footage before you need it

This is a preparedness list, not a maintenance burden. Most of it is a one-off setup exercise plus an occasional check.

1. 1Confirm the camera actually starts recording when you set off — a file that plays back, not just an indicator light.
2. 2Learn the manual event or lock control before an incident, so you are not reading the manual at the roadside.
3. 3Verify that G-sensor or event recording is enabled and configured at a sensitivity appropriate for your driving.
4. 4Know which folder holds normal clips and which holds protected or event clips on your device.
5. 5Use a compatible high-endurance memory card that meets the camera manufacturer's requirements.
6. 6Periodically confirm that recordings actually play back — on the camera and on another device.
7. 7Understand roughly how much history your configuration retains, rather than assuming the card stores weeks.
8. 8After an important event, export the original files promptly and preserve the surrounding clips too.

One deliberate omission: this guide does not prescribe a card replacement or formatting schedule. Manufacturers publish different guidance for different devices, and the right interval is the one in your documentation — not a number invented by a blog. Whatever you do, back up anything you need before formatting, because formatting erases the card.

A related failure mode — the camera that appears to be working but is not writing usable files at all — is covered in our pre-incident recording checklist.

Does a bigger memory card stop footage from being overwritten?

No. A larger card can extend the recording window — if the camera supports that capacity — but it does not change the loop. It simply takes longer for the cycle to come back around to any given clip.

Two practical limits are worth knowing. First, cameras state a maximum supported capacity, and a card beyond it may not work reliably, or at all. Card type, speed class and endurance rating also have to meet the manufacturer’s requirements — continuous recording is a workload most general-purpose cards are not built for.

Second, capacity is consumed at whatever rate your configuration dictates. Raising resolution or bitrate, or adding camera channels, will absorb the extra space. Doubling capacity while doubling channels leaves the retention window roughly where it started.

Buy the card your manufacturer recommends rather than the largest one available, and treat capacity as a way to buy review time — not as a substitute for locking and exporting.

Does the G-sensor save every accident?

No, and planning around the assumption that it will is one of the more common evidence mistakes.

A G-sensor responds to measured force. Sensitivity is configurable on most devices, and both extremes cause problems: set too low and a real collision may not register; set too high and routine potholes and speed bumps fill the protected folder with useless locked clips, which in turn consumes the space the loop cannot reclaim.

Many incidents that later matter involve little or no impact at all:

• A sideswipe or light contact during a disputed lane change.
• A near miss where the other vehicle never touched yours.
• A brake-check or aggressive-driving encounter.
• A road-rage confrontation or verbal exchange.
• A traffic stop or citation you may later want to document.
• A deliberately staged manoeuvre intended to look like your fault.

On that last point, deliberately staged collisions are a reminder that the moment worth keeping may begin well before any contact.

This is precisely why the manual lock control matters. Automatic protection is a useful default. Knowing how to lock and export a clip yourself is the part you actually control.

What should you save after an important road incident?

Once you are safe and the immediate situation is handled, treat preservation as a short, ordered task — and do it before the loop has time to work through the card.

• The event or impact clip itself.
• The clips immediately before it — approach, lane position, signals, speed.
• The clips immediately after it — reactions, stopping position, what was said or done.
• Every available camera angle, not only the one that seems most obviously relevant.
• Original unedited files, with their timestamps intact — keep edits and trims as separate copies.
• Any GPS, speed or sensor context your device records alongside the video.

The value of an evidence record usually lies in the sequence, not in one dramatic second. A clip that begins at the moment of contact can leave the most contested question — what led up to it — undocumented.

For incidents where the other driver leaves the scene, the preservation and reporting steps are covered in our hit-and-run footage guide. If the incident happened while the vehicle was parked, whether anything was recorded at all depends on the setup described in does a dash cam record when the car is off.

RoadBacked Protection: capture is not enough

Most dash cams are sold on resolution, night vision and app features. Those specifications matter. But retention, preservation and what a driver does next are usually left entirely to the driver.

The camera records. RoadBacked helps with what happens next.

RoadBacked pairs a 4-channel Protection Camera — front, rear, left and right recording, with GPS and speed context — with incident submission, evidence organization and membership support. Everyday driving footage stays local to the camera; members choose what incident materials to upload. Coverage and performance still depend on installation, power, settings, storage, lighting, hardware and the circumstances of the event.

See the Protection Camera · Compare membership options

Already dealing with an incident?

If something has already happened and you have footage, photographs and documents but no clear way to present them, the one-time Incident Evidence Review can help organize the incident record. If footage is already missing, stop using the affected storage and start with our recovery guide.

• It does not determine legal fault.
• It does not guarantee a claim outcome.
• It does not provide legal advice or legal representation.

$149 · Human review · One incident · No membership required

Frequently asked questions

What is loop recording on a dash cam?

Loop recording is the mode that lets a camera keep recording indefinitely on a finite memory card. The camera writes short sequential clips, and when usable storage runs out it generally reuses the space taken by the oldest normal, unlocked file.

Does loop recording delete old footage?

In practice, yes — ordinary unlocked footage is replaced by newer footage once storage fills. Files that the camera has locked as event or protected recordings are normally excluded from that cycle, though the exact behaviour depends on the model and its settings.

How long does dash cam footage stay on the memory card?

There is no universal answer. Retention depends on card capacity, resolution and bitrate, how many channels record at once, compression, how much you drive, whether the camera records while parked, and how much space locked files occupy. Check your own configuration rather than assuming weeks of history.

Does a G-sensor stop footage from being overwritten?

It can, when it triggers. A G-sensor attempts to lock a clip when it detects a sufficient impact, and locked clips are normally protected from the loop. But sensitivity and trigger behaviour vary, and many important events — a near miss, a disputed lane change, a road-rage encounter, a traffic stop — may never generate an impact strong enough to trigger anything.

Can locked dash cam footage still be lost?

Yes. Locking is protection from the loop, not permanent archival storage. Protected folders can have capacity limits, some devices eventually recycle protected files, cards wear out and fail, and a card can be lost or damaged. Exporting the original file is the durable step.

Does a larger SD card keep footage longer?

A larger card supported by your camera can extend how much history fits before the loop comes around, but it does not change the loop itself. Higher resolution, higher bitrate and more camera channels consume that extra capacity faster. Use a card that meets the manufacturer's stated compatibility and endurance requirements.

What footage should I save after an accident?

Save the event clip, the clips immediately before and after it, every available camera angle, and the original unedited files with their timestamps and any GPS or speed data the device records. Context and sequence are often more useful than a single dramatic second.

Sources and editorial basis

Device-behaviour claims on this page are sourced to official manufacturer documentation. Loop behaviour, locking rules, folder structure and retention vary by brand and model — always follow the documentation for the camera you own.

• Garmin — Saving and transferring dash cam recordings

  Manufacturer documentation describing saved recordings, protecting video from being overwritten, and the recommendation to transfer video you want to keep to a computer or external storage because the memory card has limited capacity.

• VIOFO — Loop recording and emergency (locked) files

  Manufacturer documentation of automatic loop recording, oldest-file overwrite when storage is insufficient, and collision-triggered or manually triggered emergency recordings that are locked against the loop.

• VIOFO — Recommended memory cards

  Manufacturer guidance on card requirements and on the recording failures, gaps and corruption associated with unsuitable or worn cards.

• VIOFO — Why you should format the card, and how

  Manufacturer guidance that continuous loop recording places sustained write load on the card, with model-specific maintenance recommendations. Other manufacturers publish different intervals.

• Nextbase — Loop recording feature

  Manufacturer description of loop recording replacing older unprotected recordings when storage fills, alongside G-sensor and manual file protection.

This article provides general educational information. Insurance procedures, evidentiary rules, traffic laws and recording laws vary by policy, insurer, state and circumstances. RoadBacked is not an insurance carrier or law firm and does not provide legal advice or representation, negotiate claims, act as a public adjuster, perform accident reconstruction, or guarantee outcomes. See our editorial standards.