Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
A dash cam G-sensor can be the reason a minor pothole fills your event folder with locked clips that show nothing useful — or the reason a hard hit in a parking lot stays protected from overwrite. The difference comes down to how the sensor is set, and on many cameras the default settings do not match the way people actually drive.
Every modern dash cam records continuously while the vehicle is on. The G-sensor is not what starts that recording; it is the small accelerometer that decides which moments are important enough to protect. If that distinction sounds small, it is the source of most confusion around sensitivity settings, false triggers, and why some parked-car impacts never get caught.
This guide explains what a dash cam G-sensor actually measures, how it differs from loop recording and parking mode, and why the same sensitivity setting can behave completely differently on a stiff-suspension sports car than on a smooth highway cruiser. It also covers the practical fixes that experienced owners use: lowering the driving G-sensor, raising the parking G-sensor, disabling the vertical axis, and using buffered parking mode so a fast hit-and-run does not disappear before the camera wakes up.
If you are setting up a first dash cam or trying to stop your event folder from filling with useless locked files, this is the full picture.
At a Glance: G-Sensor Settings That Actually Work
| Situation | Driving G-Sensor | Parking G-Sensor | Additional Move |
|---|---|---|---|
| Rough roads, potholes, speed bumps | Low or Off | High | Disable Z-axis if available |
| Smooth highway commute | Low or Medium | High | Use manual lock for real incidents |
| Urban street parking | Low or Off | High | Use buffered parking mode |
| Scrapes, keying, no impact | Low or Off | High | Use motion detection or low-bitrate recording |
What Is a G-Sensor on a Dash Cam?
A G-sensor is a three-axis accelerometer built into the dash cam. It continuously measures changes in force along three physical directions: forward and backward, side to side, and up and down. When the measured force crosses a preset threshold — a hard brake, a sharp swerve, or an impact — the camera automatically protects the current video segment from being overwritten by loop recording.
That is the entire job of the G-sensor during normal driving: not recording, but locking. A dash cam records onto a memory card in short segments. When the card fills, the oldest segment is overwritten. A G-sensor event simply tells the camera to move the current clip into a protected folder so it survives.
The sensor does this using a MEMS accelerometer, the same type of component used in smartphones, airbag systems, and game controllers. In a dash cam, it is tuned to detect the kinds of sudden movement that accompany collisions, hard braking, and aggressive cornering.
The Physics: How a Three-Axis MEMS Accelerometer Reads an Impact
At rest, a dash cam accelerometer reads close to 1g downward — the constant pull of gravity. As the car accelerates, brakes, or corners, that baseline shifts slightly in one or more axes. Normal braking might produce a small forward deviation; a pothole produces a sharp vertical spike; a side impact produces a strong lateral spike.
A crash is simply a much larger, much faster change in that baseline. The camera firmware compares the live accelerometer data against a threshold. If the reading exceeds the threshold, the camera locks the clip.
Consumer dash cams do not usually expose absolute g-force values. Instead, they offer relative settings such as Low, Medium, and High, or a numeric scale such as 0 to 9. What matters is what those settings mean in practice.
G-Sensor vs Loop Recording vs Parking Mode
These three terms are often blurred together, but they control different things.
| Concept | What It Does |
|---|---|
| Loop recording | Continuously writes video to the memory card, overwriting the oldest files when full. Always active while powered. |
| G-sensor | Detects sudden force and locks the current clip so loop recording cannot overwrite it. |
| Parking mode | A low-power state that keeps the camera ready to record while the vehicle is parked. It uses the G-sensor, motion detection, or both. |
The most common mistake is assuming the G-sensor starts recording while driving. It does not. The camera already records continuously. The G-sensor only protects the segment that contains the event.
Parking mode is a separate layer. In basic parking mode, the camera often sits in standby to save power. On impact, the G-sensor wakes it up to start recording. That wake-up delay is one reason advanced buffered parking modes matter, which is covered later.
Why "High" Feels Backwards: Sensitivity Explained
High sensitivity means the camera locks more clips. It does not mean a higher threshold for bigger crashes. A dash cam set to High requires less force to trigger, so potholes, door slams, and rough pavement are more likely to create protected files. Low sensitivity means only stronger impacts lock a clip.
This is the single most confusing labeling decision in dash cams, and it is worth repeating: High = more sensitive = more stored events. Low = less sensitive = only bigger impacts.
Most cameras ship with a Medium default. For many drivers, especially on imperfect roads, Medium is already too twitchy.
Driving vs Parking Sensitivity: Opposite Settings
The best driving G-sensor setting is usually Low, or off entirely. The reasoning is simple: the camera records continuously while you drive, so if something important happens, the footage is already on the card. A manual lock button can protect it instantly if you want to be certain. A high driving G-sensor mostly fills the protected folder with potholes and expansion joints.
The best parking G-sensor setting is the opposite: High. While parked, the camera is often not recording continuously. A light bump or door ding needs to wake it up, so a sensitive trigger is desirable. If you hardwire the camera, parking G-sensor High is the standard recommendation from manufacturers and owners alike.
The False-Trigger Problem and How to Fix It
The most common complaint on dash cam forums is not "the G-sensor missed an accident." It is "the event folder is full of locked videos, and the camera stopped recording."
That second part matters. Locked files are never automatically overwritten. If enough protected clips accumulate, loop recording has no space left for normal footage, and the camera may stop saving new video. Some models cap the protected folder around 50 files; others simply fill the card until you intervene.
The main culprits are vertical-axis triggers: potholes, speed bumps, road joints, even closing a door. On cameras with per-axis control, disabling the Z-axis removes most of those false locks while preserving horizontal impact detection — the direction that matters for front, rear, and side collisions.
The fix is straightforward:
- Lower the driving G-sensor or turn it off.
- Disable the Z-axis if the camera allows it.
- Delete locked files regularly and format the card in-camera.
- Use the manual lock button for genuine incidents while driving.
Parking Mode and the Wake-Up Latency Gap
Basic auto-event parking mode has a weakness: it sits in standby and only starts recording after an impact wakes it. That wake-up process can take three to five seconds. A fast hit-and-run driver can be out of frame before the camera begins capturing.
Buffered parking mode solves this by keeping a rolling pre-event cache in memory. VIOFO's buffered parking saves roughly 15 seconds before an event and 30 seconds after it. Vantrue keeps a similar rolling cache. Thinkware uses radar to wake the camera within one to two seconds before an impact, enough time to capture a 20-second protected segment that includes pre-impact footage.
There is also an entire category of incidents the G-sensor will never catch: scrapes, keying, and slow vandalism produce no sudden impact force. Motion detection or continuous low-bitrate recording is the only reliable way to record those while parked.
How Popular Dash Cams Handle G-Sensor Tuning
VIOFO A229 Pro
The A229 Pro separates driving and parking G-sensor settings, each with Low, Medium, and High options. Its buffered parking mode captures 15 seconds before and 30 seconds after a detected event. One important detail: in Auto Event Detection parking mode, the parking G-sensor only works while the camera is actively recording. If the camera has not triggered into recording, the impact may not be caught. This makes buffered parking the better choice for parked protection.
A hardwire kit is required for parking mode. The camera supports up to 512GB microSD cards. Check the best high-endurance SD cards to ensure reliable storage for your footage.
Vantrue N4 Pro
The N4 Pro offers per-axis G-sensor control, which is rare and useful. You can adjust X, Y, and Z axes individually or disable one entirely. Disabling the Z-axis is the community-approved way to kill wind and pothole false triggers while keeping front, rear, and side impact detection.
In parking mode, its Quick Start Collision Parking Mode can power on about three seconds after an impact. A full event folder stops loop recording, so locked files still need manual deletion or card formatting.
Nextbase 622GW
The 622GW uses a Low, Medium, High, Off G-sensor scale. Its Intelligent Parking Mode automatically sets the G-sensor to High when parked and enters after five minutes stationary or with the ignition off. On impact, it saves a 45-second protected file on the 622GW, then continues recording for another four and a half minutes before returning to standby.
That parking behavior is limited by the camera's 320mAh internal battery, which provides roughly 15 minutes of standalone recording. Nextbase estimates that catches about five separate parking incidents or up to 15 minutes of sustained attention to the vehicle. For reliable overnight coverage, the camera needs constant power via a hardwire kit.
Thinkware U3000
The U3000 takes a different approach: built-in dual 24GHz radar wakes the camera before an impact occurs. When the radar detects a moving object, the camera starts recording within one to two seconds. Thinkware specifies a detection range of about 7 meters and an 80-degree horizontal angle. On impact, a 20-second protected video covering before and after the event is saved.
Radar detects sedan-or-larger objects, not pedestrians, and Energy Saving Parking Mode 2.0 disables cloud features to reduce power draw.
Check current availability on Amazon
BlackVue DR900X Plus
BlackVue exposes one of the deepest G-sensor menus available. Each of the three axes can be adjusted independently, and an Off setting disables event locking entirely. Its advanced sensitivity settings let you fine-tune the threshold while viewing pre-recorded G-sensor data alongside the video, which is useful if you want to see exactly what the camera sees before it locks a file.
The biggest practical note is storage: locked event files do not overwrite, and on BlackVue models the protected folder can cap around 50 files. That is another reason to keep driving sensitivity low.
Check current availability on Amazon
Recommended G-Sensor Settings by Vehicle and Road Type
The same camera can behave completely differently in two vehicles. Stiff-suspension performance cars and SUVs on rough roads generate constant vertical spikes, while smooth highway cruisers generate almost none. Vehicle and road quality matter more than brand.
| Vehicle / Road Profile | Driving G-Sensor | Parking G-Sensor | Extra Advice |
|---|---|---|---|
| Performance car, stiff suspension | Low or Off | High | Disable Z-axis if available |
| SUV or truck on broken pavement | Low or Off | High | Use buffered parking |
| Smooth highway commuter | Low or Medium | High | Manual lock for real events |
| Urban street parking | Low or Off | High | Motion detection or low-bitrate for keying |
The pattern is consistent: driving protection should be minimal because continuous recording already covers you. Parking protection should be aggressive because the camera is asleep until something happens.
Frequently Asked Questions
Q: What is a G-sensor on a dash cam?
A G-sensor is a three-axis accelerometer that detects sudden changes in force. When an impact, hard brake, or sharp swerve exceeds a set threshold, the dash cam automatically locks the current video clip so loop recording cannot overwrite it.
Q: Should I set my dash cam G-sensor to high or low while driving?
Set it to Low or Off. The camera records continuously while driving, so a high G-sensor mostly creates false triggers from potholes and speed bumps. A manual lock button protects real incidents without filling the event folder.
Q: Does the G-sensor start recording when a crash happens?
No. The dash cam records continuously whenever it is powered. The G-sensor only protects the clip that contains the event. In parking mode, however, the G-sensor can wake a standby camera to start recording, which is why buffered parking modes are valuable.
Q: Why is my dash cam event folder full of locked videos?
Locked event files never get overwritten automatically. A too-sensitive G-sensor, especially on rough roads, can fill the protected folder with pothole and door-slam clips until the camera runs out of space and stops loop recording.
Q: Can I turn off the G-sensor completely?
Yes, most cameras allow it. Turning it off for driving is common because loop recording and the manual lock button cover your needs. For parking, you usually want it on High, because the camera otherwise has no impact trigger.
Q: Do I need a hardwire kit for G-sensor parking mode?
Yes, for reliable parking coverage. Parking mode needs constant power, and most dash cams enter parking mode only when connected through a hardwire kit or an external battery pack. The G-sensor itself does not power the camera.
Conclusion
A dash cam G-sensor is best understood as a protection layer, not a recording button. The camera records continuously on the road; the accelerometer simply decides which moments survive. Once you see that separation, the settings make sense: keep driving sensitivity Low or Off so the event folder stays clean, and keep parking sensitivity High so a parked car catches the light hits that matter.
The second layer is wake-up latency. A basic parking G-sensor can miss a fast hit-and-run because the camera needs a few seconds to power on from standby. Buffered parking mode on the VIOFO A229 Pro, a rolling cache on the Vantrue N4 Pro, or radar wake on the Thinkware U3000 closes that gap. If you care about parked protection, that is the feature to prioritize.
Finally, remember that the G-sensor only catches impact force. Scrapes and keying will not trigger it. For those, motion detection or continuous low-bitrate parking mode is required. Set the driving G-sensor low, the parking G-sensor high, protect important clips manually, and clear locked files before they choke the card.