Dash Cam Not Recording? 9 Checks to Make Before You Need the Footage

1. Confirm the camera actually starts recording

Power and recording are two different states. A device that lights up, chimes and shows a live preview is not necessarily writing a valid video file to storage. A card fault, a full protected-file area or a settings change can leave a camera looking perfectly healthy while producing nothing you can use.

Start the vehicle and watch what the camera does. Depending on the model this may be a recording indicator, a voice prompt, an on-screen icon or a status shown in the companion app — check your manual for which signal your device uses. Let it run for several minutes of ordinary driving, then stop somewhere safe and open the newest file.

Settings can also work against you without any hardware fault. Garmin’s dash cam settings documentation shows that automatic recording and automatic incident detection are separate options that can be configured independently. Not every model uses the same menu or the same names, so treat that as an example of how settings are structured rather than as a description of your device.

Do not test the light. Test the file.

2. Play back a recent file

The most valuable readiness test takes about a minute: open a real recording and watch it. Confirm that it plays from beginning to end, that the image is not obviously corrupted or frozen, that audio behaves as you expect if you record it, and that the file carries the date and time you expected.

On a multi-channel system, open one file from every channel rather than assuming they all behaved the same way. A file list that looks full can still be missing an entire camera.

When to repeat the test

• After installation, re-installation or any change to how the camera is mounted.
• After a firmware update.
• After replacing or reformatting the memory card.
• After any change to the camera’s power source or wiring.
• After unexplained alerts, beeps, freezes or missing clips.
• Periodically, at an interval that suits how much you drive.

There is no single correct testing interval. Manufacturer recommendations vary, and so does how hard a given driver works the system.

3. Verify every camera angle

If you run a front-and-rear or multi-channel system, each channel needs its own confirmation. A camera can run for months on a healthy front channel while a rear or side camera sits disconnected — quietly removing the exact angle that later turns out to matter.

• Open a recent file from every installed channel, not only the front.
• Check the horizon: a camera aimed too high records sky, too low records your own hood.
• Look for obstructions — wipers at rest, heavy tint bands, mirror housings, trim, stickers or a dirty lens.
• On rear cameras, check whether defroster lines, tint or a loaded boot are blocking the view.
• On side cameras, confirm the orientation is level and the image is not mirrored or rotated in a way you did not intend.

More channels do not guarantee complete evidence. Placement, lens angle and conditions determine what each camera can actually see, which is the subject of our guide on what front-and-rear cameras can miss. The point of this check is narrower: the channels you already paid for should at least be recording.

4. Check the memory card before it fails

Memory cards are the most common single point of failure in a dash cam, because continuous video writing is unusually demanding on flash storage. The card is being overwritten again and again, every day, for as long as the camera runs.

Garmin states that SD cards wear out after being overwritten many times, and that card type, speed and capacity must match the device’s requirements. VIOFO likewise documents that continuous loop recording stresses the card, and lists recording failures, gaps and corrupted files among the symptoms associated with card problems.

• Use a card that meets your camera manufacturer’s exact compatibility requirements for type, speed class and capacity.
• Watch for warning signs: memory errors, repeated beeps, freezes, missing clips or unexplained gaps in the file list.
• Replace a card that is failing or has been in continuous use for a long time — cards are consumables, not permanent parts.
• Back up anything important before formatting, because formatting erases the card.
• Format using the camera manufacturer’s documented procedure, not an arbitrary tool.

Maintenance intervals vary by manufacturer and model. VIOFO recommends formatting at least monthly on its supported devices, while guidance from other manufacturers for their own models differs. Follow the documentation for the camera you own rather than a universal rule from the internet.

5. Make sure loop recording is working

Loop recording is what lets a camera keep going once the card is full. In plain terms: when storage fills, the camera reuses space by replacing older recordings that have not been protected. Nextbase documents this behaviour alongside its file-protect function.

How loop recording fails

• Loop recording has been switched off on a model where that is possible, so the camera stops once storage fills.
• Protected or event files have filled the space reserved for them, leaving nothing available to lock.
• The card is incompatible or corrupted, so the camera cannot manage files reliably.
• The driver misunderstands retention — assuming a week of footage is available when the card holds a few hours.

Work out roughly how long your system retains footage at its current resolution, channel count and card size. That number tells you how quickly you need to act after something happens. A protected or event file is not automatically permanent; exact retention behaviour depends on the device.

If an incident already happened, use the preservation workflow instead: what to do with dash cam footage after an accident.

6. Verify date, time, GPS and speed context

An accurate clock is quietly one of the most useful settings on the device. The timestamp is what lets a recording be lined up against a police report, a claim file, a call log, scene photographs or a repair record. A camera running on the wrong date produces footage that is harder to place in a sequence of events.

Check the date and time now, and check again after any power loss, firmware update or time-zone change. If your device supports location or speed data, Garmin’s settings documentation shows that some dash cams offer a data overlay containing date, time, location and speed. Not all dash cams do, and the options differ by model — confirm what your own camera supports and that the features you want are actually enabled and functioning.

Evidence readiness is not a feature. It is a system check.

One honest caveat: GPS and speed data do not prove innocence or fault. They add context — and that context can document facts that are unfavourable to you just as easily as favourable ones. Enable them because you want an accurate record, not because you expect them to settle an argument.

7. Test the G-sensor and manual protect function

Event protection is designed to stop an important file from being overwritten by the loop. Nextbase documents both G-sensor protection and manual file protection; other manufacturers implement event locking differently. What no manufacturer can promise is perfect detection — whether a sensor triggers depends on its sensitivity setting and on the nature of the event.

Before you need it, find out:

• What indicator confirms that a clip has been protected.
• Where protected files are stored, and how to find them.
• Whether the camera has a manual protect control — a button, a voice command or an app action.
• How much protected storage is available, and what happens when it fills.
• Whether protected files are eventually subject to device-specific retention limits.

Test the manual protection control, not the sensor. Do not deliberately create a hard impact to see whether the G-sensor fires; follow your manufacturer’s instructions for sensitivity configuration and any supported test procedure.

Automatic protection is useful. Knowing how to preserve a clip manually is the backup plan.

8. Test parking mode separately

Driving recording and parking recording are different power and configuration states. A camera that records flawlessly on ignition power may do nothing at all once the vehicle is switched off, unless the system has been specifically configured and powered for parking monitoring.

• Confirm whether your camera supports a parking mode at all, and which variant — motion detection, impact detection, time-lapse or continuous.
• Confirm how it is powered when the ignition is off, and what installation that requires.
• Confirm any voltage cut-off or timer setting that stops recording to protect the vehicle battery.
• Park, leave the car for a while, then check whether parking-mode files were actually created.

RoadBacked’s camera supports parking monitoring, which may require additional installation or hardwiring depending on the vehicle. Whether anything records while the engine is off is a question worth settling in advance — covered in does a dash cam record when the car is off and, for the scenario that usually prompts the question, a parked car hit by another driver.

9. Practice retrieving a clip before you need one

This is the check almost nobody performs, and the one most likely to cause trouble. Record a harmless test drive, then retrieve one clip using whichever method your system documents: Wi-Fi or app transfer, a memory card reader, a USB connection, or another supported route.

• Copy the file off the camera without editing or trimming the original.
• Keep a working copy separately from the original if you want to rename or share it.
• Back the copy up somewhere that is not the camera and not only the phone in your pocket.
• Play it on a second device to confirm the format is readable outside the manufacturer’s app.
• Note how long the whole process took — that is how long it will take under pressure.

Recording is only half of the evidence workflow. After an incident the driver still has to preserve the right clips before the loop reaches them, retrieve them intact, organize them alongside photographs and documents, and submit the relevant material to whoever is asking.

A camera you cannot retrieve footage from is not ready for an incident.

A simple periodic readiness routine

You do not need a maintenance schedule from a spreadsheet. You need a two-minute routine you will actually repeat — monthly is a reasonable default for most drivers, more often if you drive for a living.

• Confirm the recording indicator or app status when the vehicle starts.
• Open one recent file and watch part of it.
• Inspect one file from each installed channel.
• Check for storage or error warnings on the device.
• Confirm date, time and — where supported — GPS context are correct.
• Wipe the lenses and check that nothing is obstructing any view.
• Follow your manufacturer’s guidance for SD-card maintenance and firmware updates.

The exact cadence should follow your camera manual and how intensively you drive. A card in a vehicle used ten hours a day is under a very different load from one in a weekend car.

Protection starts before the incident

Most dash cams are evaluated on resolution, Wi-Fi, night vision and storage. Those specifications matter. But when an incident becomes disputed, the useful question is a different one: did the system capture the relevant context, and can the driver preserve and retrieve it?

RoadBacked combines a 4-channel Protection Camera — front, rear, left and right recording, with GPS and speed context — with incident submission, evidence organization and membership support for what happens next. Coverage and performance still depend on installation, power, settings, storage, lighting, hardware and the circumstances of the event.

Everyday driving footage stays local to the camera. Members choose what incident materials to upload.

See the Protection Camera · Compare membership options

Already had an incident?

If the incident already happened and the recording is missing, stop using the affected storage until you understand what happened, and start with RoadBacked’s recovery guide. If you have the footage but the incident is disputed, the one-time Incident Evidence Review can help organize the footage and supporting materials you submit.

• 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

How do I know if my dash cam is actually recording?

Do not rely on an indicator light. Let the camera run for a few minutes, then open the newest file and play it back from start to finish. A file that exists, plays and carries the date you expect is the only reliable confirmation.

Why does my dash cam turn on but not record?

Power and recording are separate states. Common causes include an incompatible, full or worn memory card, loop recording switched off on models where it can be disabled, protected files occupying the available storage, a card formatted outside the camera, or a firmware or power fault. Check the card first, then the recording settings in the manual.

Can an SD card cause a dash cam to stop recording?

Yes. Continuous video writing is demanding on flash storage. Garmin states cards wear out after being overwritten many times, and VIOFO documents recording failures, gaps and corruption among the symptoms associated with card problems. Use a card that meets the camera manufacturer's stated requirements and replace one that shows errors.

Should loop recording be on?

On most consumer dash cams, yes — loop recording is what allows the camera to keep recording once storage fills, by reusing space taken by older unprotected files. If it is disabled on a model where it can be, the camera may simply stop once the card is full.

How often should I format my dash cam SD card?

There is no universal interval. Follow the camera and card manufacturer. VIOFO recommends formatting at least monthly on its supported devices; other manufacturers publish different maintenance guidance for their models. Back up anything you need before formatting, because formatting erases the card.

Does a dash cam automatically save footage after a crash?

Many cameras have a G-sensor that attempts to lock a file when it detects an impact, and many also offer manual protection. Neither is guaranteed: detection depends on sensitivity settings and the nature of the event, and protected files may still be subject to device-specific retention limits. Learn how to protect a clip manually as well.

How do I know if my rear or side camera is recording?

Check each channel individually. Open one recent file from every camera and confirm it plays and is framed the way you expect. A system can run normally on the front channel while a disconnected rear or side camera silently removes the angle that later matters.

Should GPS and speed be enabled on a dash cam?

If your device supports it and you want that context recorded, enable it and confirm it is working. Be aware that this data adds context in both directions — it can document facts that are unfavourable to you as well as favourable. It does not prove fault or innocence.

How can I test my dash cam before an accident?

Record a short ordinary drive, then run the nine checks in this guide: confirm recording starts, play back a file, check every channel, inspect the card for errors, confirm loop recording, verify date, time and GPS settings, test manual file protection, confirm parking mode separately if you rely on it, and copy one clip off the camera to another device.

Sources and editorial basis

Device-behaviour claims on this page are sourced to official manufacturer documentation. Menus, retention behaviour and maintenance requirements vary by brand and model — always follow the documentation for the camera you own.

• Garmin — Dash cam settings documentation

  Official manufacturer documentation showing that dash cam settings can separately control automatic recording, incident detection and the data overlay containing date, time, location and speed. Menus and available options vary by model.

• Garmin — Memory card compatibility and support

  Manufacturer support material on memory cards, including that cards wear out after being overwritten many times and that card type, speed and capacity must meet the device's requirements.

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

  Manufacturer guidance that continuous loop recording stresses the card, and a recommendation to format at least monthly on its supported devices. Other manufacturers publish different intervals.

• VIOFO — Recommended memory cards

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

• Nextbase — Loop recording feature

  Manufacturer documentation describing loop recording behaviour — replacing older unprotected recordings when storage fills — together with G-sensor and manual file protection. Retention behaviour differs by device.

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.