Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
Loop recording is the feature that lets a dash cam record indefinitely on a finite microSD card by overwriting the oldest unlocked clip rather than stopping when the card fills. That circular-buffer behavior is the default on every current model, from the VIOFO A229 Pro to the Nextbase iQ, but the segment lengths, gap behavior, and file-locking rules are not identical.
Most shoppers encounter loop recording as a yes/no checkbox, then discover the real questions only after an incident: why is a clip missing, why did the card fill with protected files, or why did the loop silently stop. The mechanism is simple, but the reliability details live in segment length, SD card endurance, and how the camera treats locked event files.
This guide explains how loop recording actually behaves across the VIOFO A229 Pro, Vantrue N5, Nextbase iQ, and Nextbase 622GW. It also covers the two items that keep the loop from failing: a high-endurance microSD card and a hardwire kit for buffered parking mode.
It is written for drivers comparing current models and for owners troubleshooting a "card full" warning, a gap between clips, or a missing impact file.
Quick Reference: Loop Recording at a Glance
| Model | Loop segments | Card limit | Parking-mode buffer |
|---|---|---|---|
| VIOFO A229 Pro | 1/2/3/5/10 min | 512GB | 15s before / 30s after event |
| Vantrue N5 | 1/2/3 min, default 1 min | 512GB | 10s before / 30s after event |
| Nextbase iQ | Fixed 30-second clips | 256GB | Radar + AI SmartSense |
| Nextbase 622GW | 1/2/3 min, default 1 min | 128GB U3, 256GB on Elite | G-sensor only, ~30s after bump |
How Dash Cam Loop Recording Works
A dash cam does not record one continuous file. It divides footage into fixed-length segments — usually between 30 seconds and five minutes — and writes them to the memory card in sequence. When the card is full, the camera deletes the oldest unlocked segment and continues recording in its place. In storage terms, that is a first-in, first-out circular buffer.
The practical result is that a 64GB card does not fill up after a week of commuting. At 4K, a 128GB card typically holds five to six hours of front footage before the loop begins overwriting; at 1080p, the same card holds roughly 12 to 16 hours. The VIOFO A229 Pro's 4K front stream is about 1.2GB per five minutes, which works out to roughly 240MB per minute — useful for estimating how long footage survives before being overwritten.
Locked or event files sit outside the loop. When the G-sensor detects an impact or you press the manual protect button, the current segment moves to a separate event or protected folder. The loop cannot overwrite those files, which is the feature that preserves accident footage — and the source of the most common "card full" problem when too many clips get locked.
Loop Segment Lengths and Why They Matter
Segment length is the first setting worth changing on cameras that expose it. Shorter segments reduce how much footage is lost if a file corrupts, while longer segments create fewer files and make scanning a long drive easier.
The choices differ by manufacturer:
- VIOFO A229 Pro: 1, 2, 3, 5, or 10 minutes.
- Vantrue N5: 1, 2, or 3 minutes, with 1 minute as the default.
- Nextbase 622GW: 1, 2, or 3 minutes, with 1 minute as the default.
- Nextbase iQ: fixed at 30 seconds, with no user adjustment.
The N5's shorter range is partly enforced by the FAT32 file-size limit. Individual files are capped at 4GB, which is why no camera records an hour-long single clip onto a FAT32-formatted card. On the Nextbase iQ, the fixed 30-second clips are the smallest of the group: the 4K front camera writes about 143MB per clip, and the cabin or rear 2K cameras write about 86MB per clip, all using H.265 encoding.
For most drivers, a three-minute segment is the best balance. It limits corruption loss to a few minutes while keeping the file count manageable on a daily commute.
The "Seamless" Myth: Clip Gaps and Impact Footage
Loop recording is often marketed as seamless, but community evidence across brands tells a more precise story. Owners have documented seven-to-twelve-second gaps between consecutive clips, and occasional overlaps, meaning there can be brief windows with no saved footage at all. On the VIOFO A329S — which shares the A229 Pro platform and firmware family — DashCamTalk users reported both seven-to-twelve-second overlaps and seven-to-twelve-second gaps between driving clips.
Those boundaries matter most in an accident. If an impact falls at the exact end of a clip, the event file may capture only a few seconds, while the rest of the incident lands in the next normal clip. Vantrue's own guidance tells owners to check both the event folder and the normal folder after an incident. A separate, community-documented A229 Pro case showed the front camera capturing before and after an impact but missing the impact moment itself.
This is why loop recording should not be treated as a frame-perfect safety net. The real protection layers are a correctly tuned G-sensor that locks the event file, buffered parking mode, and — where available — cloud backup. The loop itself is reliable in ordinary driving, but clip boundaries are a known weak point. For a deeper look at how the G-sensor protects event files, see our guide to dash cam G-sensors.
Locked Files and the Event Folder Problem
Locked files are both the point of loop recording and its most common failure mode. Because the loop cannot overwrite protected files, a camera with an overly sensitive G-sensor will gradually fill the event folder with pothole and door-slam clips. Once that folder consumes enough of the card, the loop stalls or the card reports full — even though most of the saved files are useless.
Manufacturers handle this differently:
- Vantrue N5: when the event folder reaches 30% of card capacity, the oldest event videos are recycled.
- VIOFO A229 Pro and Nextbase 622GW: normal clips loop, but protected files remain until you format the card manually.
- Nextbase 622GW manual: format roughly every two weeks so protected files don't fill the card and halt the loop.
The recommendation is consistent across brands: format the card in the camera every two to four weeks. Daily drivers should format monthly; rideshare or 24/7 parking users should format every two weeks. In-camera formatting clears old protected files and gives the loop a clean index. If the driving G-sensor is set too high, lower it to Low or Off and use the manual protect button for real incidents.
Loop Recording on Current Dash Cams
VIOFO A229 Pro
The A229 Pro is VIOFO's flagship 4K platform. Its front camera uses a Sony STARVIS 2 IMX678 sensor at 4K with a 140° field of view; the two-channel setup adds a 2K rear camera on the IMX675, and the three-channel version includes a 1080p interior camera with four infrared LEDs.
- Loop segments: 1, 2, 3, 5, or 10 minutes
- 4K front bitrate: about 1.2GB per five minutes
- Card support: up to 512GB microSD
- Buffered parking: 15 seconds before and 30 seconds after a detected event
- Parking power: requires the VIOFO HK4 hardwire kit
In buffered parking mode, the A229 Pro stores the pre-event buffer only while it is actively recording; if it has not yet triggered into recording, the parking G-sensor cannot catch the impact. That makes the HK4 hardwire kit and a properly configured parking mode the difference between a protected parking event and a missed one.
Vantrue N5
The Vantrue N5 is a four-channel camera with front, front-cabin, rear-cabin, and rear lenses. Maximum resolution is 2.7K front plus three 1080p feeds, with a Novatek dual-core chipset and supercapacitor power.
- Loop segments: 1, 2, or 3 minutes; default is 1 minute
- Event-folder recycling: oldest events recycle once the folder reaches 30% of card capacity
- Buffered motion detection: 10 seconds before and 30 seconds after an event
- Card support: up to 512GB microSD
- Parking power: requires a Vantrue USB-C hardwire kit with ACC switching
The N5's event-folder recycling is a useful safeguard, but it is not a substitute for formatting. Vantrue recommends formatting every two to four weeks and specifically names Samsung PRO Endurance and SanDisk High/MAX Endurance cards for continuous HD loop recording.
Nextbase iQ
The Nextbase iQ is a connected 4G LTE camera available in 1K, 2K, and 4K front resolutions. The 4K model uses an Omnivision OS08A10 8MP sensor, with a cabin camera and an optional 2K rear module.
- Loop segments: fixed at 30 seconds, non-adjustable
- 4K front clip size: about 143MB per 30 seconds
- Cabin/rear 2K clip size: about 86MB per 30 seconds
- Encoding: H.265
- Card support: up to 256GB microSD, U3/V30 required
- Parking: SmartSense Parking uses front and rear radar plus AI motion sensing
The iQ's most distinctive loop trait is its fixed 30-second clip length, which creates a large number of small files. Its headline parking, Live View, and cloud features require a paid subscription. Power comes from OBD-II or hardwiring, not a 12V cigarette-lighter socket, so installation is part of the purchase decision.
Nextbase 622GW
The 622GW is Nextbase's legacy 4K flagship, launched in 2020. It remains useful as a reference point for how loop recording differs from the newer iQ.
- Loop segments: 1, 2, or 3 minutes; default is 1 minute
- Card support: 8GB to 128GB U3 cards; a 256GB U3 card is only listed for the 622GW Elite
- Minimum write speed: about 48MB/s continuous
- Parking: Intelligent Parking Mode wakes the camera on a G-sensor bump and records about 30 seconds
- No buffered parking or time-lapse mode
The 622GW requires a fast U3 card. Standard SanDisk cards that miss the 48MB/s continuous-write minimum are flagged as unsuitable, and many SanDisk warranties exclude dashcam or continuous-recording use. If you are buying used or clearing out an older card, a high-endurance U3/V30 card is the safe choice.
Parking Mode and the Hardwire Requirement
Loop recording during normal driving works from any power source, but parking mode does not. Buffered parking — recording the seconds before and after a detected event — requires constant power, which means a hardwire kit or battery pack, not a cigarette-lighter adapter that shuts off with the ignition.
Two kits cover most of the models in this guide:
- VIOFO HK4 hardwire kit: Type-C, three-wire install with ACC detection, 12V/24V compatible, and four low-voltage cutoff points at 11.8V, 12.0V, 12.2V, and 12.4V for 12V systems. Fuse taps are not included on the base SKU.
- Vantrue USB-C hardwire kit: 11.5 feet, 12V–24V to 5V, dual-stage cutoff at 11.6V for 12V vehicles and 23.2V for 24V vehicles. Newer variants offer five-level adjustable cutoff and an LED voltage display.
The ACC wire must connect to an ignition-switched circuit, or the camera will not switch between driving and parking modes. If the constant-power wire is not truly constant, parking recording ends early. Setting the cutoff higher protects the car battery from draining too far. For the full parking-mode picture, see our guide to dash cam parking mode.
Check Price on Amazon — VIOFO HK4
Check Price on Amazon — Vantrue USB-C hardwire kit
SD Cards: The Real Failure Point
The most common cause of missing footage, card errors, and a stopped loop is not the camera — it is a slow, worn, or wrong-format microSD card. Standard consumer cards are not built for the continuous write cycles and windshield heat of a dash cam, and many warranties explicitly exclude dashcam or surveillance use.
Two cards are the practical standards for loop recording:
- Samsung PRO Endurance 256GB: rated for up to 140,160 hours of Full HD recording at 26Mbps, with read/write speeds up to 100/40 MB/s and a five-year limited warranty. Independent testing measured real-world writes around 78 MB/s, well above the rated figure.
- SanDisk High Endurance 256GB: rated for up to 40,000 hours by SanDisk, U3/V30/C10, with temperature, water, shock, and X-ray resistance. For heavy 24/7 parking use, SanDisk MAX Endurance is the stronger choice, rated for up to 120,000 hours on the 256GB model.
Both cards carry U3/V30, which guarantees at least 30 MB/s sustained write — the floor for reliable 4K loop recording. The card matters as much as the camera, and buying a high-endurance model is the single cheapest reliability upgrade in a dash cam setup. For a full comparison, see our guide to high-endurance microSD cards.
Check Price on Amazon — Samsung PRO Endurance 256GB
Check Price on Amazon — SanDisk High Endurance 256GB
Recommended Loop Settings
For most drivers, these settings deliver the best balance of reliability and usable footage:
- Segment length: 3 minutes on VIOFO and Nextbase 622GW; 3 minutes on Vantrue N5 where available.
- Driving G-sensor: Low or Off on a stiff suspension; use the manual lock button for real events.
- Format cadence: monthly for daily drivers, biweekly for rideshare, fleet, or 24/7 parking use.
- Card: high-endurance U3/V30 microSD from the model's supported capacity range.
- HDR: on where available, especially for night plate legibility.
- Parking mode: Time Lapse or Low Bitrate for overnight parking on VIOFO and Vantrue units; buffered Auto Event Detection only when wired to constant power.
Frequently Asked Questions
Q: Does a dash cam record continuously or only on impact?
It records continuously while powered. The footage is split into short loop segments, and the G-sensor or a manual button locks relevant segments so the loop cannot overwrite them.
Q: Why is footage missing from my dash cam?
The three most common causes are a slow or dying microSD card, a gap at a clip boundary, or an event folder filled with locked files that halted the loop. Format the card in the camera every two to four weeks and use a high-endurance U3/V30 card.
Q: What loop segment length should I use?
Three minutes is the best default for VIOFO, Vantrue, and Nextbase 622GW. The Nextbase iQ is fixed at 30 seconds. Shorter clips limit corruption loss; longer clips reduce file clutter.
Q: Will loop recording overwrite my accident clip?
Only if the clip is not locked. The G-sensor should lock the event file on impact, and the manual protect button is a backup. Locked files are stored separately from normal loop clips, but too many locked files can fill the card.
Q: What size SD card can I use?
The VIOFO A229 Pro and Vantrue N5 support up to 512GB. The Nextbase iQ supports up to 256GB with U3/V30 required. The Nextbase 622GW supports 8GB to 128GB U3, with 256GB only on the 622GW Elite.
Q: Does loop recording work in parking mode?
Yes, but buffered parking requires constant power through a hardwire kit or battery pack. VIOFO buffered parking stores about 15 seconds before and 30 seconds after an event; Vantrue stores about 10 seconds before and 30 seconds after.
Conclusion
Loop recording is not a spec to glance at — it is the behavior that determines whether a four-hour drive survives on a 128GB card and whether a parking-lot hit is saved or silently overwritten. On current flagships, the mechanism works well, but it is not seamless. Clip-boundary gaps exist, locked files can stall the loop, and a cheap SD card remains the most common point of failure.
The most reliable setup pairs a proven camera with two supporting pieces: a high-endurance microSD card and a hardwire kit for parking mode. The VIOFO A229 Pro and Vantrue N5 both offer configurable segments, buffered parking, and up to 512GB of storage, which makes them the two strongest platforms for drivers who want control over how the loop behaves.
For more on the adjacent hardware, read our guide to high-endurance SD cards, our deep dive on parking mode, and our explainer on G-sensors. If you are ready to buy, the VIOFO A229 Pro is the best all-around starting point for reliable loop recording and buffered parking.
