| Quick Facts | |
|---|---|
| Typical loop-recording segment length | 1 to 3 minutes per file, model dependent |
| SD Association Video Speed Class minimum write speeds | V6 = 6 MB/s, V10 = 10 MB/s, V30 = 30 MB/s, V60 = 60 MB/s, V90 = 90 MB/s |
| 4K vs 1080p bitrate difference (same codec) | roughly 2 to 4 times more data per minute at 4K than 1080p |
| H.265/HEVC bitrate savings vs H.264/AVC | about 25% to bitrate at comparable quality, per Wikipedia's summary of published test results |
| Event-file (G-sensor) protection | locked into a separate folder immediately on impact detection; not overwritten by loop recording until manually cleared |
How long do dash cam recordings last before they get overwritten?
There's no set number of hours or days; a dash cam keeps recording in a loop until the card runs out of free space, then starts erasing its own oldest footage to keep going.
Shopping for a specific model? See our best dash cams picks — 10 models compared on the specs that decide it.
Almost every dash cam on the market uses loop recording, and it helps to picture it less like a tape running out and more like a conveyor belt. The camera records in fixed-length segments, commonly one to three minutes apiece depending on the model, and writes each one to the card as a separate file. Once the card fills up, the camera doesn't stop. It deletes the single oldest segment and writes the new one in its place, then repeats that process indefinitely for as long as the camera has power.
That design answers a real practical problem: nobody wants to manually clear a memory card every few days just to keep a dash cam running. But it also means the honest answer to how long dash cam recordings last is 'until the card is full, then forever after that, on a rolling basis.' A 32GB card might hold three or four hours of footage before the loop starts turning over; a 256GB card holds proportionally more. Neither number is really a countdown timer, since the camera keeps recording and overwriting in that same loop for as many years as the hardware and card survive.
What actually decides how much footage a card can hold
Card capacity divided by video bitrate is the real math, and bitrate itself swings hard based on resolution, frame rate, and how much motion is in the scene.
Two dash cams with identical memory cards can hold wildly different amounts of footage, because the file size per minute depends on how much data the camera is writing, not just how big the card is. Resolution is the biggest lever. Standard video-compression figures put 4K footage encoded in H.264 at roughly two to four times the bitrate of 1080p footage encoded the same way, which means a card that holds a full day of 1080p driving footage might only hold six to twelve hours of 4K from the same trip.
Codec choice compounds that further. Wikipedia's summary of H.265/HEVC cites study results showing it needs roughly 25 to 66 percent less bitrate than H.264 for comparable visual quality, so two 4K dash cams can fill a card at very different rates depending on which codec is doing the compressing. Scene complexity matters too, in a way that's easy to overlook: a highway drive with wide open sky compresses more efficiently than a busy city street, since modern video codecs spend more bits encoding motion and detail than encoding a static frame. None of this is unique to dash cams. It's the same math behind any continuously-recording camera, just compressed into a card small enough to sit behind a rearview mirror.
Why the memory card itself is doing more work than it looks like
A dash cam writes data nonstop for as long as it has power, which is a harder workload than almost anything else a memory card is normally asked to do, and cards not built for it can drop frames or fail early.
Most memory cards spend their lives holding still photos, written in short bursts with long idle stretches in between. A dash cam inverts that completely: it writes continuously, hour after hour, with no idle time to speak of. The SD Association, the industry body that defines SD card standards, created Video Speed Class ratings specifically because ordinary speed ratings don't guarantee steady write performance during continuous recording, and a card that stutters mid-write can drop frames or corrupt a file right when it matters most.
Under the SD Association's own published ratings, V6, V10, V30, V60, and V90 guarantee minimum sustained write speeds of 6, 10, 30, 60, and 90 megabytes per second respectively. A 1080p dash cam generally sits comfortably within a V10 or V30 card's sustained write speed, while 4K recording is the territory where V30 or V60 starts to matter, since a card writing below the footage's actual bitrate will drop frames rather than simply writing slower. This is also why dash cam manufacturers frequently recommend cards marketed for continuous or 'high-endurance' use rather than a standard card pulled from a phone or camera; the flash memory inside is built to tolerate the nonstop write-erase cycle a dash cam demands, where a card designed for occasional photo storage is not.
Why some footage survives the loop and most doesn't
A built-in G-sensor detects sudden impacts and immediately locks that clip into a separate, protected folder, which is the one exception to the constant overwrite cycle.
Loop recording would be a liability if it erased evidence of the one moment that actually mattered. That's the job of the G-sensor, an accelerometer built into nearly every modern dash cam that watches for sudden deceleration or a physical jolt. The instant it registers something consistent with a collision, the camera flags the current clip as an event file and moves it into a protected folder that ordinary loop recording is not allowed to touch.
That protection is deliberately narrow. It covers the file the G-sensor happened to be writing when the trigger fired, not the whole card, and it doesn't extend to footage recorded before or after that window unless the camera also buffers a few seconds on either side. It's also not unlimited: event files pile up in their own folder, and if that folder itself fills the card, most cameras either stop protecting new events or, on some models, start overwriting the oldest locked files too. Treating a locked event file as permanently safe is the wrong assumption; it's protected from routine loop overwrite, not backed up anywhere else, which is exactly why offloading footage after a real incident is worth doing sooner rather than trusting the card indefinitely.
What to actually do if you need footage saved for good
Pull the footage off the card and onto a phone, computer, or cloud service as soon as possible after anything worth keeping, since the card itself is never a permanent archive.
The loop-recording folder and the protected-event folder are both still just space on the same card, which means neither one is a backup in any real sense. A card that gets knocked loose, corrupted, or simply fills its event folder can still lose footage a driver assumed was safe. The practical fix costs nothing extra: most dash cams pair with a phone app over WiFi specifically so a driver can pull a clip immediately after anything worth keeping, rather than waiting to plug the whole card into a computer later.
Card capacity is worth matching to how you actually plan to use the camera, not just buying the biggest number available. A larger card mostly buys more time before dash cam recordings last long enough to matter and more headroom in the protected-event folder before that fills too; it does nothing to make footage permanent on its own. Anyone shopping for a new setup can compare current models, card sizes, and channel counts across our full dash cam lineup, and our wireless dash cam picks specifically highlight models built around that phone-app hand-off, which matters more once you understand that the card was never meant to hold anything forever.